Office Addin MCP server
io.github.dsbissett/office-addin-mcp·v0.8.0·3 starsMCP server for Office add-ins via WebView2/CDP. Provides excel.*, page.*, and addin.* tools.
3 stars52 downloads/wk
Reviews
Write oneNobody has reviewed Office Addin yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Office Addin tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 110 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Office Addin compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,273 servers
- GitHub stars
- 3
- more than 80% of 28,534 servers
- Downloads a week
- 52
- more than 45% of 11,915 servers with a package
Install Office Addin in Claude Code, Cursor or VS Code
Runs npx -y @dsbissett/office-addin-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add office-addin-mcp -- npx -y @dsbissett/office-addin-mcp
What the publisher says
From the Office Addin repository's README, as published. We do not edit it. Read it on GitHub
office-addin-mcp
Drive Excel, Word, Outlook, PowerPoint, and OneNote add-ins from any MCP client — through one Go binary that speaks the Model Context Protocol over stdio.
office-addin-mcp attaches to the WebView2 runtime that Office uses to host Office.js add-ins, then exposes a high-level tool surface to LLM clients. Instead of teaching the model how to chain 15 raw Office.js primitives, the server ships one tool call per workflow.
See the latest release · CHANGELOG.md · PLAN-workflow-surface.md.
Highlights
- Workflow tools, not primitives. excel.tabulateRegion, word.applyEdits, outlook.draftReply, powerpoint.rebuildSlideFromOutline, onenote.appendToPage, and excel.summarizeWorkbook each compress what used to be 5–20 calls into one Office.js batch (one CDP round-trip).
- Server-side query DSL. excel.query / outlook.query / powerpoint.query / onenote.query run filter / project / groupBy / agg / limit inside the host so a 100k-row workbook returns a 5-row answer.
- Persistent document context cache. *.discover tools snapshot workbook / document / mailbox / deck / notebook structure to %LOCALAPPDATA%\office-addin-mcp\doccache.json so repeat discovery calls cost zero CDP round-trips.
- MCP Resources with live subscriptions. Reference Office state by URI — office://excel/Book1/Sheet1!A1:D20, office://word//bookmark/, office://outlook/inbox, office://pp//slide, office://onenote/// — and subscribe to notifications/resources/updated when contents change.
- Macro record & replay. macro.recordstart → run any sequence of tools → macro.recordstop writes a JSON macro to disk. On next launch the server registers each macro as a callable macro. tool.
- Auto-diagnostics on Office.js errors. ItemNotFound, address parse failures, slide-index errors, and compose-vs-read mismatches are enriched in the failure envelope with availablesheets, nearestnamesuggestions, parsedaddress, slidecount, itemmode, and a recoveryHint — so the model can self-correct without a second round-trip.
- Self-healing CDP connection. If Excel closes unexpectedly, the server detects the dead connection on the next tool call, stops the stale sideload registration, relaunches Excel (including the dev server if needed), resets the session pool, and retries the original operation — no agent intervention required. Only activates when the server owns the launch (via --launch-addin or a prior addin.launch call); attaching to an external --browser-url endpoint is never disturbed.
- Progress notifications on long operations. addin.launch, addin.ensureRunning, and macro replay stream MCP $/progress notifications at each phase boundary (dev-server start, sideload, CDP-ready wait, step execution) so clients can show a live status bar instead of a silent spinner.
- Cross-host orchestration. office.embed reads a range from Excel and inserts it onto a PowerPoint slide in one call.
- Page automation fallback. page. / pages. / inspect. / interact. cover screenshot, snapshot, click, fill, type, hover, navigate, evaluate, wait, console log, network log — same primitives against headless Chrome on macOS/Linux.
- Per-host runScript escape hatch. excel.runScript, word.runScript, outlook.runScript, powerpoint.runScript, onenote.runScript run arbitrary .run callbacks when the workflow surface isn't enough.
Requirements
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Office Addin: common questions
- Is Office Addin MCP server safe?
- Mostly: it is graded B (82/100). Read the Office Addin safety report
- How do I install Office Addin?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Office Addin need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Office Addin maintained?
- The last commit was 146 days ago (2026-06-09). The latest release is v0.8.0.
- How does Office Addin compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,273 servers); github stars 3 (more than 80% of 28,534 servers); downloads a week 52 (more than 45% of 11,915 servers with a package). Full comparison.