Iwork Mcp
MCP server for Apple iWork automation — 117 tools for Numbers, Pages, and Keynote. Template discovery, Creator Studio AI tools, compound batch operations. One l…
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.
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
From the project's README.