iwork_mcp
MCP server for Apple iWork automation — 125 tools for Numbers, Pages, and Keynote. Template discovery, Creator Studio AI tools, compound batch operations. One line to install.
Install / Use
claude mcp add reichenbach -- npx -y github:reichenbach/iwork_mcpIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of iwork_mcp
iwork_mcp scores 86/100 on our quality scale, 1747th of 2,790 Automation skills we index.
Its MCP Server is 7.7 KB long, well organised into 14 sections with 12 code examples: a thorough specification that gives an agent plenty to work with.
It has 45 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated 11 days ago, so iwork_mcp is actively maintained.
- Our last check on 2026-11-13 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 85/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-12. Automated pattern scan on 2026-11-12. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
iwork_mcp compared with similar skills
All 4 of these similar skills score higher than iwork_mcp; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| iwork_mcp (this skill)by reichenbach | 86 | 45 | 11d ago | MCP Server |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install iwork_mcp?
- Run
claude mcp add reichenbach -- npx -y github:reichenbach/iwork_mcp. The install tabs above show the steps for each supported agent. - Which AI agents does iwork_mcp work with?
- It is written for Claude Code, Claude Desktop and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
- Is iwork_mcp safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 85/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is iwork_mcp still maintained?
- The repository was last updated 11 days ago, so iwork_mcp is actively maintained.
Skill content
View source on GitHubiwork-mcp
An agent-neutral MCP server for automating Numbers, Pages, and Keynote on macOS. It exposes 125 tools over local stdio or authenticated Streamable HTTP.

Capabilities
- Numbers: create spreadsheets, read and write cells and ranges, use formulas, format tables, add charts, and export to PDF, spreadsheet, or CSV formats.
- Pages: create and format documents, edit paragraphs, insert images and tables, and export to PDF, document, EPUB, or text formats.
- Keynote: create and edit presentations, add and edit text boxes and charts, lay out slide items, add presenter notes and transitions, preview single slides, and export to PDF, presentation, HTML, or image formats.
Requirements: macOS 13 or newer, current iWork applications, and Node.js 18 or newer. macOS asks for Automation permission on first use.
Local stdio setup
stdio is the default transport. Each client starts its own server process.
Grok Bot
Add an MCP command server named iwork with command npx and arguments -y, iwork-mcp.
Cursor
Use the included plugin listing, or add this to the client's MCP configuration:
{
"mcpServers": {
"iwork": {
"command": "npx",
"args": ["-y", "iwork-mcp"]
}
}
}
Claude
For Claude Desktop:
npx iwork-mcp install
For Claude Code:
claude mcp add iwork -- npx -y iwork-mcp
Codex
codex mcp add iwork -- npx -y iwork-mcp
Remote HTTP setup
Runs on your own Mac. iWork (Pages, Numbers, Keynote) is macOS-only, so this server must run on the Mac that has iWork installed. The Cloudflare Tunnel only exposes that Mac's server to remote clients; it cannot run in the cloud.
First configure an owner passphrase and start the server. It binds only to loopback by default:
iwork-mcp --setup-passphrase
IWORK_MCP_PUBLIC_URL=https://YOUR-TUNNEL-HOST iwork-mcp --http --port 8787
The endpoint is https://YOUR-TUNNEL-HOST/mcp. It uses OAuth 2.1 dynamic client registration, authorization code with required PKCE S256, rotating refresh tokens, and short-lived opaque access tokens. Every MCP request requires a bearer token.
Optionally set IWORK_MCP_REDIRECT_HOST_ALLOWLIST to a comma-separated list of permitted OAuth callback hosts, host:port pairs, or origins.
For a free named Cloudflare Tunnel and the optional launch-at-login template, follow Remote connector setup.
Grok Bot, Cursor, Claude, and Codex
For any client that accepts a remote MCP URL, add:
{
"mcpServers": {
"iwork": {
"url": "https://YOUR-TUNNEL-HOST/mcp"
}
}
}
The client discovers the OAuth metadata, registers itself, opens the local consent page, and obtains tokens. If a client uses a different configuration shape, enter the same URL in its remote connector UI.
Example requests
Build a monthly budget in Numbers with planned and actual income, categorized expenses, variance formulas, and a net savings row.
Create a concise Keynote review deck with six slides, a consistent layout, and presenter notes.
Draft a formatted Pages project brief with objectives, milestones, risks, and next steps.
How it works
For local use, an MCP client communicates with the server over stdio. For remote use, the official SDK's Streamable HTTP transport serves /mcp behind OAuth. Tool registration is shared, so both transports expose the same tool set. Tool calls run JavaScript for Automation through the system scripting process and control the installed iWork applications.
Each scripting call is killed if it runs too long. Ordinary calls time out after 30 seconds and saves after 120 seconds. To change these limits for large documents, set IWORK_MCP_TIMEOUT_MS and IWORK_MCP_SAVE_TIMEOUT_MS (in milliseconds).
Development
npm install
npm run build
npm test
npm test runs unit and remote OAuth/HTTP tests without opening iWork applications. The HTTP suite skips with a clear reason when a sandbox prohibits socket binding. Integration tests require the applications and skip when they are unavailable:
npm run test:integration
npm run test:all
Reviewer HTTP and OAuth test
Use temporary per-user directories or remove them after testing. Start the server:
IWORK_MCP_PASSPHRASE='YOUR-LONG-TEST-PASSPHRASE' \
IWORK_MCP_PUBLIC_URL=http://127.0.0.1:8787 \
iwork-mcp --http --host 127.0.0.1 --port 8787
In a second terminal, inspect metadata and register a loopback client:
curl http://127.0.0.1:8787/.well-known/oauth-protected-resource
curl http://127.0.0.1:8787/.well-known/oauth-authorization-server
curl -sS -X POST http://127.0.0.1:8787/register \
-H 'content-type: application/json' \
-d '{"redirect_uris":["http://127.0.0.1/callback"],"client_name":"Review Client","token_endpoint_auth_method":"none"}'
Create a PKCE verifier and challenge, replacing YOUR-CLIENT-ID with the registration result:
VERIFIER='review-verifier-0123456789012345678901234567890123456789'
CHALLENGE=$(printf %s "$VERIFIER" | openssl dgst -sha256 -binary | openssl base64 -A | tr '+/' '-_' | tr -d '=')
open "http://127.0.0.1:8787/authorize?response_type=code&client_id=YOUR-CLIENT-ID&redirect_uri=http%3A%2F%2F127.0.0.1%2Fcallback&code_challenge=$CHALLENGE&code_challenge_method=S256&state=review"
Enter the owner passphrase. The browser redirects to the loopback callback; copy the code query value from its address. Exchange it and then initialize MCP:
curl -sS -X POST http://127.0.0.1:8787/token \
-d grant_type=authorization_code \
-d client_id=YOUR-CLIENT-ID \
-d redirect_uri=http://127.0.0.1/callback \
-d code=YOUR-AUTHORIZATION-CODE \
-d code_verifier="$VERIFIER"
curl -i -X POST http://127.0.0.1:8787/mcp \
-H 'authorization: Bearer YOUR-ACCESS-TOKEN' \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"review","version":"1"}}}'
Copy the mcp-session-id response header, send an notifications/initialized notification, then call tools/list with the same bearer token and session header. The automated test performs this complete sequence and verifies that HTTP returns the same 125 tools as stdio.
Security and limitations
/registerallows 20 attempts per client per minute, with a global cap of 200 attempts per minute. Requests rejected by the per-client limit do not consume the global budget. IPv6 clients share a bucket for their /64 prefix, and IPv4-mapped IPv6 addresses use the corresponding IPv4 address. Client buckets are capped at 1,000 entries, evicting expired or oldest entries as needed.- When the socket peer is loopback, the limiter uses the first
CF-Connecting-IPvalue if it is a valid IP address; otherwise it uses the socket address. Trust this header only when usingcloudflared, because Cloudflare overwrites it. With other loopback tunnels (ngrok,ssh -R, Tailscale Funnel), the header is client-controlled, so only the global cap is meaningful. A distributed attacker can still exhaust the global cap, even withcloudflared, temporarily blocking new client setup (existing tokens are unaffected).
The HTTP server defaults to 127.0.0.1. Keep it on loopback behind an HTTPS tunnel, set IWORK_MCP_PUBLIC_URL to the exact external origin, use a strong owner passphrase, and never store secrets in the repository. OAuth state is stored in the current user's data directory with mode 0600; the passphrase hash is stored separately in the current user's configuration directory.
iWork's scripting dictionaries determine what can be automated. Some application features are unavailable or require macOS Accessibility permission.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
