ioffice-mcp: Instructions file for Claude Code

CLAUDE.md

ioffice-mcp CLAUDE.md is an instructions file for Claude Code from chrischall/ioffice-mcp. It costs 2,145 tokens per session, scanned A, original, MIT.

Project instructions for ioffice-mcp, an MCP server that connects Claude to iOffice workplace and facility-management APIs. It exposes tools for buildings, floors, spaces, reservations, and visitor check-ins.

In plain words
What is it for?
Use them when building, testing, running, or extending the server and its workplace-management tools.
Why use it?
They explain how the server is built, how its tools are named, and which environment settings are needed to run it.

Instructions file for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is chrischall/ioffice-mcp's own configuration. It tells Claude Code how to work on ioffice-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ioffice-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to chrischall/ioffice-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/chrischall/ioffice-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/chrischall/ioffice-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ioffice-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/chrischall/ioffice-mcp/claude-md.svg)](https://agentmods.dev/instructions/chrischall/ioffice-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/chrischall/ioffice-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/ioffice-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,145 This file is loaded in full into every session.
When invoked 2,145 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.02145 $0.02145
Opus 5 $0.01073 $0.01073
Sonnet 5 $0.00429 $0.00429
Haiku 4.5 $0.00215 $0.00215

Measured 7d ago against content hash 6c72a923edf4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

ioffice-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ioffice-mcp

MCP server exposing iOffice workspace/facility management APIs to Claude. Uses stdio transport.

Commands

npm run build            # tsc + esbuild bundle → dist/index.js + dist/bundle.js
npm test                 # Run tests (vitest)
npm run test:watch       # Watch mode
npm run test:coverage    # Coverage report (100% thresholds enforced)
npm run dev              # node --env-file=.env dist/index.js (requires built dist)

Run locally (requires built dist):

IOFFICE_HOST=tenant.ioffice.com IOFFICE_TOKEN=xxx node dist/index.js

Tool naming

All tools are prefixed io_ (e.g. io_list_buildings, io_create_reservation, io_checkin_visitor).

Architecture

src/
  index.ts          # MCP server entry — runMcp() from @chrischall/mcp-utils, registers all tool modules, stdio transport
  client.ts         # IOfficeClient (thin wrapper over createApiClient from @chrischall/mcp-utils) + re-exported buildQueryString/buildOptionalBody + local optionalBody helper
  tools/
    buildings.ts    # io_{list,get,create,update,delete}_building
    floors.ts       # io_{list,get,create,update,delete}_floor
    spaces.ts       # io_{list,get,create,update,delete}_space
    users.ts        # io_{list,get,create,update,delete}_user
    reservations.ts # io_{list,get,create,update,delete,checkin,checkout}_reservation
    visitors.ts     # io_{list,get,create,update,checkin,checkout}_visitor
    maintenance.ts  # io_{list,get,create,update,accept,start,complete,archive}_maintenance_request
    mail.ts         # io_{list,get,create,deliver,return}_mail
    moves.ts        # io_{list,get,create,update,approve,cancel}_move

Each tool module exports a register<Domain>Tools(server, client) function that calls server.registerTool(...) with a zod input schema and a handler. index.ts constructs one IOfficeClient and hands it to runMcp({ deps: client, tools: [...] }), which passes it to every register call. Add new domains by mirroring this pattern (and add them to the tools array in index.ts).

Read the full file on GitHub · 136 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 136 lines · 2,145 tokens per session scan A 6c72a923edf4

Subscribe to this mod's changes

ioffice-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/ioffice-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 2,145 tokens to every session, about $0.0107 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

vibe-coding-prompt-template backend.instructions.md

Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.

KhazP/vibe-coding-prompt-template · 139 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens