Excel WebView2 MCP
Debug and automate Excel Office add-ins running in WebView2 by giving your agent Chrome DevTools Protocol access to the embedded web surface.
Overview
Excel WebView2 MCP is a Model Context Protocol server for the Build phase that connects agents to Excel add-in UIs through WebView2 Chrome DevTools Protocol.
What is this MCP server?
- MCP server specialized for Excel add-ins via WebView2 CDP
- stdio npm package @dsbissett/excel-webview2-mcp v0.0.9
- Targets developers automating or inspecting add-in UI inside Excel
- Narrower scope than full Office-addin-mcp—Excel WebView2 focus
- GitHub-hosted reference implementation for Office JavaScript + WebView2 workflows
- Registry version 0.0.9
- npm package @dsbissett/excel-webview2-mcp with stdio transport
- Single-package MCP server schema entry
Community signal: 2 GitHub stars.
What problem does it solve?
Your Excel add-in UI runs inside WebView2 and normal browser automation cannot see or debug it from the agent.
Who is it for?
Windows-focused developers building Excel task-pane or function add-ins who already use WebView2 debugging workflows.
Skip if: Mac-only Office add-in shops, pure Google Sheets integrations, or builders with no Excel add-in project.
What do I get? / Deliverables
Your agent can drive CDP-backed inspection and automation against the add-in’s web surface while you develop inside Excel.
- Agent-driven CDP access to Excel add-in WebView2 surfaces
- Faster iteration on Office JavaScript UI without manual DevTools-only workflows
- Repeatable MCP tool calls for add-in inspection tasks
Recommended MCP Servers
Journey fit
Excel add-in development is a Build-phase integration problem where the UI runs inside Office’s WebView2 host, not a normal browser tab. WebView2 CDP bridging is an integration layer between your add-in web stack and desktop Excel, not generic frontend polish.
How it compares
Excel-specific WebView2 CDP MCP, not the broader office-addin-mcp tool suite with excel.*, page.*, and addin.* namespaces.
Common Questions / FAQ
Who is Excel WebView2 MCP for?
Developers creating Excel Office add-ins who need agent-assisted debugging of the WebView2-hosted UI on supported Windows setups.
When should I use Excel WebView2 MCP?
Use it during Build when you are integrating Office JavaScript with Excel and need CDP-level visibility into the embedded webview from an MCP client.
How do I add Excel WebView2 MCP to my agent?
Install @dsbissett/excel-webview2-mcp, register the stdio MCP server in Claude Code or Cursor, and run Excel with your sideloaded add-in per the GitHub README.