How do I install Ioffice?

Ioffice is a local plugin. Install it using npm package: ioffice-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Ioffice safe to use?

Yes. Ioffice passed MCP Marketplace's automated security scan with a score of 9.2/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Ioffice need?

Ioffice requires the following credentials or environment variables: IOFFICE_HOST, IOFFICE_TOKEN, IOFFICE_USERNAME, IOFFICE_PASSWORD. You can find setup instructions on the server detail page.

What AI apps work with Ioffice?

Ioffice uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Ioffice MCP Server

by Chris Hall

Developer ToolsLow Risk9.2Local

Free

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

About

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

Security Report

9.2

Low Risk9.2Low Risk

Valid MCP server (2 strong, 1 medium validity signals). 1 code issue detected. 2 known CVEs in dependencies (0 critical, 1 high severity) Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (98/99 approved); 3 highly-trusted packages. 1 finding(s) downgraded by scanner intelligence.

7 files analyzed · 4 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Your iOffice tenant hostname (e.g. yourcompany.ioffice.com)Optional

Environment variable: IOFFICE_HOST

Your iOffice API token (preferred over username/password)Required

Environment variable: IOFFICE_TOKEN

Your iOffice username (used if no API token)Optional

Environment variable: IOFFICE_USERNAME

Your iOffice password (used if no API token)Required

Environment variable: IOFFICE_PASSWORD

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-chrischall-ioffice-mcp": {
      "env": {
        "IOFFICE_HOST": "your-ioffice-host-here",
        "IOFFICE_TOKEN": "your-ioffice-token-here",
        "IOFFICE_PASSWORD": "your-ioffice-password-here",
        "IOFFICE_USERNAME": "your-ioffice-username-here"
      },
      "args": [
        "-y",
        "ioffice-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

ioffice-mcp

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.

variable	default
`MCP_CONFIRM_MODE`	`ask-user`	What 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_ELICITATION`	`on`	`off` 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_SECONDS`	`600`	How long a token stays valid.
`MCP_CONFIRM_SECRET`	random per process	Signing key; set it only if tokens must survive a server restart.