Connect Microsoft Excel to Claude Code

Have Claude write values and update formulas inside your Microsoft Excel workbooks. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Microsoft Excel to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Microsoft Excel, you add a Microsoft Excel MCP server: a small hosted service that exposes Microsoft Excel's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Microsoft Excel account. No API keys pasted into config files.

claude mcp add --transport http microsoft-excel https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Microsoft Excel once connected?

Full read-write Excel access lets Claude write values into ranges, add or update formulas, create and rename worksheets, apply formatting, and append rows to tables, all in the workbook you already use. The manual cell-by-cell entry that followed every analysis happens directly in the file.

Write calculated values into a named range or specific cells
Add or update formulas across a column
Create a new worksheet and populate it from your instructions
Append rows to an existing Excel table
Apply number formatting or basic styling to a range
Rename or reorder worksheets within a workbook

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Microsoft Excel access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Microsoft Excel API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Microsoft Excel changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Microsoft Excel connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Microsoft Excel connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Microsoft Excel account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Microsoft Excel's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Microsoft Excel?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Microsoft Excel account it signs in with. Revoking access is one click in Microsoft Excel.

More on the Microsoft Excel connector

Microsoft Excel connector for claude.ai Google Sheets + Claude Code Airtable + Claude Code Smartsheet + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us