Office Addin Mcp

io.github.dsbissettPublished by GitHub account dsbissettv0.8.0Updated Nov 3, 2026

MCP server for Office add-ins via WebView2/CDP. Provides excel.*, page.*, and addin.* tools.

Overview

AI-generated overview

Local MCP server that attaches to Office WebView2 add-ins over CDP, letting an assistant read and edit Excel, Word, Outlook, PowerPoint and OneNote content.

What you can do
  • Summarize, tabulate, query and batch-patch Excel workbooks, including a server-side filter/groupBy/aggregate DSL
  • Discover document structure and apply batched find/replace edits in Word
  • Query mailboxes and active items, and set subject or body on Outlook compose items
  • Query decks and rewrite slide titles or body bullets in PowerPoint; query notebooks and append HTML or bullets to OneNote pages
  • Read an Excel range and embed it on a PowerPoint slide, record tool sequences as replayable macros, and manage add-in lifecycle
  • Automate pages as a fallback: screenshots, snapshots, clicks, typing, navigation, console and network logs
When to use it
Useful when an assistant should work directly inside open Office documents and mail on Windows — summarizing a workbook, pivoting a sheet, drafting a reply, or rebuilding slides — instead of the user copying data back and forth. Also usable for headless Chrome page automation on macOS and Linux.
Requirements
Runs as a local stdio process, typically via npx (Node.js 14+) or a prebuilt binary; building from source needs Go 1.22+. Office tools require Office on Windows 10/11 with the WebView2 debug port enabled (WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS set to a remote debugging port), or the --launch-addin flag to sideload an add-in project. The server probes a local debug endpoint by default.
Before you install
Tools write to real documents, mail drafts, slides and notebooks, and runScript tools execute arbitrary Office.js callbacks, so changes can be destructive. The --allow-dangerous-cdp flag (env OAMCP_ALLOW_DANGEROUS_CDP) enables crash/terminate CDP methods. Document structure snapshots are cached to a local doccache file. The server can relaunch Office and start a dev server when it owns the launch.

Installation

In SourceWeft

  1. Open Office Addin Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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/<doc>/bookmark/<name>, office://outlook/inbox, office://pp/<deck>/slide<N>, office://onenote/<notebook>/<section>/<page> — and subscribe to notifications/resources/updated when contents change.
  • Macro record & replay. macro.record_start → run any sequence of tools → macro.record_stop writes a JSON macro to disk. On next launch the server registers each macro as a callable macro.<name> 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 available_sheets, nearest_name_suggestions, parsed_address, slide_count, item_mode, 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 <Host>.run callbacks when the workflow surface isn't enough.

Requirements

RequirementNotes
Office on Windows 10/11Required for all *.runScript / *.query / *.discover / *.applyDiff / addin.* tools — Office only uses WebView2 on Windows
Node.js 14+For the npx install path
Go 1.22+Only needed to build from source
macOS / LinuxSupported for page.* / pages.* against headless Chrome (no Office)

Install

npm (recommended)

bash
npm install -g @dsbissett/office-addin-mcp

Or run on demand without installing:

bash
npx @dsbissett/office-addin-mcp@latest --help

Pre-built binaries for Windows x64, macOS (Intel + Apple Silicon), and Linux (x64 + ARM64) ship via optional npm dependencies — the correct binary is fetched automatically.

Build from source

bash
go install github.com/dsbissett/office-addin-mcp/cmd/office-addin-mcp@latest

Use it in Claude Code

One command registers the server globally:

bash
claude mcp add office-addin-mcp -- npx -y @dsbissett/office-addin-mcp@latest

Or add it manually. Project scope (.claude/mcp.json in the repo) or user scope (~/.claude.json → mcpServers) both work:

json
{  "mcpServers": {    "office-addin-mcp": {      "command": "npx",      "args": ["-y", "@dsbissett/office-addin-mcp@latest"]    }  }}

Then, in any Claude Code session:

  1. Open the Office host (see Office host setup below) so the WebView2 debug port is listening.
  2. Ask Claude to do something — e.g. "Summarize the workbook, then pivot the Sales sheet by region." It will pick excel.summarizeWorkbook and excel.query automatically.
  3. Run /mcp in Claude Code to inspect the tool list, or claude mcp list from a shell.

Tip: pass --launch-addin and Claude can sideload the add-in project under the current working directory automatically. No manual env var needed.

Use it in other MCP clients

VS Code (GitHub Copilot)

Workspace config at .vscode/mcp.json:

json
{  "servers": {    "office-addin-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@dsbissett/office-addin-mcp@latest"]    }  }}

Or: Command Palette → MCP: Add Server → paste the command.

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

json
{  "mcpServers": {    "office-addin-mcp": {      "command": "npx",      "args": ["-y", "@dsbissett/office-addin-mcp@latest"]    }  }}
Codex (OpenAI)

~/.codex/config.toml:

toml
[mcp_servers.office-addin-mcp]command = "npx"args = ["-y", "@dsbissett/office-addin-mcp@latest"]
Windsurf

~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "office-addin-mcp": {      "command": "npx",      "args": ["-y", "@dsbissett/office-addin-mcp@latest"]    }  }}
Any MCP-compatible client
  • command: npx
  • args: ["-y", "@dsbissett/office-addin-mcp@latest"]
  • transport: stdio

Office host setup

Office hosts only expose their WebView2 runtime to CDP when started with a debug-port env var. The variable is shared across every Office app, so the same setup works for all five:

PowerShell

powershell
$env:WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = "--remote-debugging-port=9222"Start-Process excel.exe my-workbook.xlsx# or:  Start-Process winword.exe my-document.docx# or:  Start-Process outlook.exe# or:  Start-Process powerpnt.exe my-deck.pptx# or:  Start-Process onenote.exe

Command Prompt

cmd
set WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=9222excel.exe my-workbook.xlsx

The server probes http://127.0.0.1:9222 by default. Override with --browser-url or --ws-endpoint. Or skip the setup entirely with --launch-addin — the server will detect the Office add-in project under cwd and sideload it through office-addin-debugging.

Tool surface

Phase 0 of PLAN-workflow-surface.md deleted the raw cdp.* surface; everything below is the workflow-shaped replacement. Each workflow tool is one MCP call → one Office.js batch → one CDP round-trip.

Excel

ToolPurpose
excel.summarizeWorkbookSheets, tables, named ranges, used-range bounds — single call
excel.tabulateRegionLoad a range, return rows-as-objects + per-column type tags
excel.queryServer-side filter / project / groupBy / agg / limit DSL
excel.discoverPersistent workbook fingerprint snapshot (doccache)
excel.applyDiffBatch cell/range patches in one Excel.run
excel.runScriptRun an arbitrary Excel.run callback

Word

ToolPurpose
word.discoverDocument structure snapshot
word.applyEditsBatch find/replace edits in one Word.run
word.runScriptRun an arbitrary Word.run callback

Outlook

ToolPurpose
outlook.queryQuery the mailbox / current item
outlook.discoverMailbox + active-item snapshot
outlook.draftReplySet subject and/or body on a compose-mode item
outlook.runScriptRun an arbitrary callback against Office.context.mailbox

PowerPoint

ToolPurpose
powerpoint.querySlide-level query DSL
powerpoint.discoverDeck structure snapshot
powerpoint.rebuildSlideFromOutlineRewrite a slide's title and/or body bullets
powerpoint.runScriptRun an arbitrary PowerPoint.run callback

OneNote

ToolPurpose
onenote.queryNotebook / section / page query DSL
onenote.discoverNotebook structure snapshot
onenote.appendToPageAppend HTML and/or bullets to a page
onenote.runScriptRun an arbitrary OneNote.run callback

Cross-host & macros

ToolPurpose
office.embedRead an Excel range and insert it on a PowerPoint slide
macro.record_startBegin capturing subsequent tool calls into a named macro
macro.record_stopFinalize and persist the macro to disk
macro.<name>Replay a persisted macro (auto-registered on next startup)

Add-in lifecycle & generic page automation

Tool groupPurpose
addin.*ensureRunning (start here — probes then launches if needed), launch, stop, detect, status, contextInfo, cfRuntimeInfo, openDialog, dialogSubscribe, dialogClose, listTargets
page.*screenshot, snapshot, click, fill, typeText, hover, navigate, evaluate, pressKey, waitFor, consoleLog, networkLog, networkBody
pages.*list, select, close, handleDialog
inspect.* / interact.*DOM / accessibility inspection and higher-level interaction primitives

MCP Resources

LLM clients can reference Office state by URI instead of re-fetching it every turn. Five resource templates are registered on startup:

URI templateBacked by
office://excel/<workbook>/<sheet>!<range>excel.tabulateRegion
office://word/<doc>/bookmark/<name>word.runScript (inline script)
office://outlook/<folder>outlook.query
office://pp/<deck>/slide<N>powerpoint.query
office://onenote/<notebook>/<section>/<page>onenote.query

Resources support resources/subscribe. The server polls fingerprints every 30s and emits notifications/resources/updated when content changes; resources/unsubscribe (or client disconnect) tears down the polling goroutine.

Performance notes

  • urlPattern selects the WebView2 page by substring match against the target URL. After the first call against a session, the selector cache drops diagnostics.cdpRoundTrips from ~3 to 1 on subsequent calls.
  • The session pool allows 3 reconnects per 60-second window. Exhaustion surfaces as connection/session_acquire_failed. If the server owns the launch, it attempts one automatic stop+relaunch cycle before surfacing that error, so transient Excel restarts are transparent to the agent.
  • DocCache snapshots are atomic-rename writes, mode 0600. Disable with --no-doccache.

Flags & environment variables

FlagEnvDefaultDescription
--browser-url—http://127.0.0.1:9222WebView2 / Chrome debug endpoint
--ws-endpoint——Direct browser WebSocket URL (overrides --browser-url)
--log-file—stderrAppend diagnostics to a file instead of stderr
--log-level—infoslog level: debug, info, warn, error
--launch-addin—offAuto-detect and sideload the Office add-in project under cwd at startup, only if no CDP endpoint is reachable
--launch-excel—offDeprecated alias for --launch-addin
--no-doccache—offDisable the persistent document discovery cache (*.discover still runs; reads/writes to doccache.json are skipped)
--allow-dangerous-cdpOAMCP_ALLOW_DANGEROUS_CDPoffEnable crash/terminate CDP methods
--version——Print binary version and exit

The binary takes no positional subcommands — it speaks MCP over stdio. The legacy call / daemon / serve --stdio subcommands have been removed.

Layout

cmd/office-addin-mcp/   main entryinternal/tools/         registry, dispatcher, envelope, diagnosticsinternal/cdp/           hand-rolled CDP WebSocket clientinternal/webview2/      endpoint discoveryinternal/session/       session pool + reconnect budgetinternal/officejs/      Office.js executor + payloadsinternal/js/            embedded Office.js scriptsinternal/doccache/      persistent document discovery cacheinternal/resources/     office:// URI parsing + provider + polling watcherinternal/recorder/      macro recorder storeinternal/tools/macrotool/  macro.record_start / record_stop / replayinternal/mcp/           SDK server wiring + resource registration

License

MIT

Source: README.md at commit fc2ee47

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.8.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.