Log inSubmit server
Ioffice MCP logo

Ioffice MCP

Connects Claude to iOffice for booking rooms, managing visitors, and handling maintenance tickets.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Ioffice MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ioffice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ioffice-mcp"
      ],
      "env": {
        "MCP_CONFIRM_MODE": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_TTL_SECONDS": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 53 tools correctly (1d ago).

Overview

The ioffice-mcp MCP server connects Claude with iOffice workspace management for booking rooms, managing visitors, and handling maintenance tickets. Write and state-changing operations use confirmation controls, covering 34 tools. On clients without confirmation prompts, it returns a preview and single-use token before performing a write. Use it when Claude needs to interact with iOffice while keeping changes reviewable.

Use cases

  • Book workplace rooms through Claude
  • Manage visitor records in iOffice
  • Handle maintenance ticket workflows
  • Review write previews before sending changes

Key features

  • iOffice workspace management
  • Room booking
  • Visitor management
  • Maintenance ticket handling
  • Confirmation for 34 write and state-changing tools
  • Single-use, argument-bound confirmation tokens

Tools53

What Ioffice MCP lets your agent do. Expand a tool for its parameters.

Verified live~17.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

6/6 checks healthy over the last 54d

What it can do

From the 53 tools this server returned when we ran it; 53 declare their own safety hints.

Can delete or modify data · 34Handles credentials · 35Makes network requests · 53Read-only tools · 19
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age223 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · ioffice-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.6kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed53Callable tools this server registers over MCP.

How Ioffice MCP works

What ioffice-mcp MCP server does

The ioffice-mcp MCP server gives Claude access to iOffice workspace management tasks. Its documented use cases include booking rooms, managing visitors, and handling maintenance tickets. These operations let an agent work with workplace requests through the MCP interface rather than treating them as text-only tasks.

Each of those operations requires confirmation before it is carried out.

How it works

The ioffice-mcp MCP server applies a confirmation flow to every write and state-changing tool. When the connected client can display a confirmation prompt, the user receives the actual prompt. Claude Code is identified as a client with this capability.

Clients that cannot show a confirmation prompt, including Claude Desktop and claude.ai, use a two-call process. The first call does not send the change to iOffice. Instead, it returns a preview containing the HTTP method, request path, and exact body, along with a single-use confirmToken. A later call must provide that token to perform the write.

Tokens are tied to the arguments used for the preview. If any argument changes before the second call, the token is rejected. This prevents approval of one request from being reused for a different request.

Setup and configuration

Consult the project documentation for those connection details.

Confirmation behavior can be configured with environment variables:

  • MCP_CONFIRM_MODE defaults to ask-user. On clients without prompt support, this returns a preview and token, then requires approval before the model repeats the call. auto permits the model to reuse the token after reviewing the preview. refuse rejects writes on those clients. Unknown values are treated as refuse.
  • MCP_CONFIRM_TTL_SECONDS defaults to 600, controlling how long a confirmation token remains valid.
  • MCP_CONFIRM_SECRET defaults to a random value generated for each process. Set it when confirmation tokens need to remain valid across a server restart.

Clients that can show confirmation prompts always use the real prompt, regardless of MCP_CONFIRM_MODE.

Limitations and notes

The documented client behavior differs between Claude Code and clients without confirmation-prompt support. In the latter group, a write is intentionally split into preview and execution calls, so an integration must preserve the returned token and repeat the request without changing its arguments.

Those items should not be assumed when evaluating deployment requirements.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ioffice MCP

ioffice-mcp is an MCP server that connects Claude to iOffice workspace management. Its main documented tools cover booking rooms, managing visitors, and handling maintenance tickets. It also protects 34 write and state-changing tools with confirmations, previews, and single-use tokens on clients without prompt support.

It identifies ioffice-mcp as an npm package, so use the repository or npm package documentation for the exact installation and client configuration steps.

Yes, the confirmation flow explicitly supports Claude Desktop. Because Claude Desktop cannot show the real confirmation prompt, the first write call returns a preview and single-use token; a repeated call with that token performs the change.

Yes, Claude Code is identified as a client that can show confirmation prompts. Write and state-changing operations therefore use the actual confirmation prompt rather than the preview-and-token flow.

Set MCP_CONFIRM_MODE, MCP_CONFIRM_TTL_SECONDS, or MCP_CONFIRM_SECRET. The mode defaults to ask-user, token lifetime defaults to 600 seconds, and a custom secret can preserve tokens across server restarts.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIoffice MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ioffice-mcp?style=directory)](https://allmcps.com/mcp/ioffice-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/ioffice-mcp"><img src="https://allmcps.com/api/badge/ioffice-mcp?style=directory" alt="Ioffice MCP on AllMCPs" /></a>