mcpField
I
ioffice-mcp

ioffice-mcp

Local
github.com/chrischallBusiness & Marketing1Updated 4d ago
Repository

About ioffice-mcp

ioffice-mcp connects Claude to iOffice workspace management. It supports booking rooms and managing visitors and maintenance tickets, with confirmation safeguards for state-changing operations.

Key features

  1. 01Book rooms
  2. 02Manage visitors
  3. 03Handle maintenance tickets
  4. 04Confirm changes before writing
  5. 05Preview targeted record changes

Use cases

  1. 01Book a workspace meeting room
  2. 02Manage visitor records
  3. 03Submit or track maintenance tickets
  4. 04Review a proposed update or deletion

MCP support

Exposes iOffice workspace-management operations to Claude through an MCP server. Write and state-changing tools require confirmation or provide a preview and single-use token, depending on client capabilities.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "chrischall-ioffice": {
      "command": "npx",
      "args": [
        "-y",
        "ioffice-mcp"
      ],
      "env": {
        "IOFFICE_HOST": "<IOFFICE_HOST>",
        "IOFFICE_TOKEN": "<IOFFICE_TOKEN>",
        "IOFFICE_USERNAME": "<IOFFICE_USERNAME>",
        "IOFFICE_PASSWORD": "<IOFFICE_PASSWORD>"
      }
    }
  }
}
Run commandnpx -y ioffice-mcp
Environment variables to set
IOFFICE_HOSTYour iOffice tenant hostname (e.g. yourcompany.ioffice.com)
IOFFICE_TOKENSecretYour iOffice API token (preferred over username/password)
IOFFICE_USERNAMEYour iOffice username (used if no API token)
IOFFICE_PASSWORDSecretYour iOffice password (used if no API token)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmioffice-mcp3.2.6

Tools

53

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
viewenumNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns iOffice's payload untouched. No field projection: this server has no verified record of which iOffice fields matter, and inventing one would risk dropping a field a caller needs.compact | full
limitintegerNoMax results (default 50, max 100)
searchstringNoFilter by name or description
orderBystringNoProperty to sort by (default: id)
startAtintegerNoPagination offset (default 0)
orderByTypeenumNoSort direction (default: asc)asc | desc

Details

From the project README

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.