Listed from the MCP registry; nobody on Odel publishes it.

MCP server: One MCP server.

iOffice

@chrischallMCP server · External

iOffice workspace management for Claude — book rooms, manage visitors, maintenance tickets

v3.3.0MITTypeScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: moves money, runs code or commands, deletes data, or sends messages for you.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npmioffice-mcpv3.3.0

Run

npx -y ioffice-mcp

MCP client config

{
  "mcpServers": {
    "ioffice": {
      "command": "npx",
      "args": [
        "-y",
        "ioffice-mcp"
      ]
    }
  }
}
README2 min read

ioffice-mcp

CI npm license

iOffice MCP server for Claude — developed and maintained by AI (Claude Code)

Confirmations

Every write and state-changing tool (34 of them) asks the user to confirm first. A client that can show a confirmation prompt (Claude Code) gets the real prompt unless MCP_CONFIRM_ELICITATION=off. On one that cannot (claude.ai, Claude Desktop), the first call writes nothing and returns a preview — the method, path and exact body that would be sent — plus a single-use confirmToken; only a repeat call with that token performs the write, and a token is refused if any argument changed in between.

An update, delete, io_cancel_move or io_return_mail first reads the record it targets, so its preview (and prompt) names what will change — Delete iOffice user 42 (Alice Smith) with her email, not just the id — and a token is also refused if that record was modified after the preview. An id that does not exist fails at that read, before anything is previewed.

variabledefault
MCP_CONFIRM_MODEask-userWhat a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call writes nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse.
MCP_CONFIRM_ELICITATIONonoff never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE behaviour. Set it for a client that says it can show prompts but never does (the write hangs — opencode 2.0.x). Any other value is treated as on, with a warning on stderr.
MCP_CONFIRM_TTL_SECONDS600How long a token stays valid.
MCP_CONFIRM_SECRETrandom per processSigning key; set it only if tokens must survive a server restart.

Similar modules