Office Addin Mcp
Control Excel cells, add-in lifecycle, and hosted page behavior from your agent via namespaced excel.*, page.*, and addin.* MCP tools over WebView2/CDP.
Overview
Office Add-in MCP is a Model Context Protocol server for the Build phase that provides excel.*, page.*, and addin.* tools for Office add-ins via WebView2/CDP.
What is this MCP server?
- Namespaced MCP tools: excel.*, page.*, and addin.* for Office add-in projects
- WebView2 and CDP bridge for Office-hosted web UI automation
- @dsbissett/office-addin-mcp v0.8.0 stdio npm package
- Broader than Excel-only servers—Office add-in patterns with structured tool surface
- GitHub reference for agent-driven add-in testing alongside human sideload workflows
- Registry version 0.8.0
- 3 documented tool namespaces: excel.*, page.*, addin.*
- npm package @dsbissett/office-addin-mcp with stdio transport
Community signal: 2 GitHub stars.
What problem does it solve?
Building Office add-ins forces you to manually drive Excel, the task pane, and DevTools while the agent cannot call consistent high-level add-in operations.
Who is it for?
Small teams building Excel or Office task-pane add-ins who want agent-callable, namespaced tools instead of ad-hoc scripting only.
Skip if: Web-only SaaS with no Office host, or organizations that block desktop Office automation and MCP CDP access.
What do I get? / Deliverables
Your agent invokes structured excel, page, and addin MCP tools to test and automate your Office JavaScript integration from the IDE.
- Agent-callable excel.*, page.*, and addin.* tool operations
- Integrated WebView2/CDP debugging path for Office-hosted UI
- Faster regression checks on Office JavaScript features from the agent
Recommended MCP Servers
Journey fit
Office add-ins are cross-surface integrations; agents need structured tools beyond raw CDP when shipping spreadsheet or task-pane products. Unified excel.*, page.*, and addin.* tool families map directly to wiring Office JavaScript hosts into your Build workflow.
How it compares
Structured Office add-in MCP with excel./page./addin. tools, richer than Excel-only WebView2 MCP for multi-surface add-in work.
Common Questions / FAQ
Who is Office Add-in MCP for?
Developers shipping Office JavaScript add-ins who want MCP agents to exercise Excel, page, and add-in behaviors through a defined tool API.
When should I use Office Add-in MCP?
Use it during Build and integration testing when your product lives inside Excel or Office and you need repeatable agent-driven control via WebView2/CDP.
How do I add Office Add-in MCP to my agent?
Add @dsbissett/office-addin-mcp as a stdio MCP server in your client config, ensure Excel/Office and your sideloaded add-in are running, then call excel.*, page.*, or addin.* tools from the agent.