M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
M

MCP Server for Excel

Community
AI-driven Excel automation on Windows, powered by the real Excel COM engine.
How to install ↓ Compare GitHub source repository ↗
Category
Other #71 of 230
Stars
★ 828 Very popular
Transport
stdio (local process)
Runtime
Prebuilt binary · .NET 10
Credentials
No credential needed
License
MIT
Last commit
Tools
2
60FMRS · C

A feature-rich, community-maintained MCP server for Windows-only Excel automation that drives the real Excel COM engine to cover Power Query, DAX, VBA, PivotTables, and charts, but it needs a local Excel install and exclusive workbook access, ruling out cross-platform or server-side use.

Strongest · Documentation 15/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
9/20
Maintenance
15/20
Documentation
15/20
Setup experience
13/20
Why each score
Reliability 8/20
Only the README and manifest are available; there is no visible CI workflow content or committed test files to verify that MCP initialization and tool-list handshake actually work as described. The tool/operation counts are inconsistent between the repo description ("23 tools, 214 operations") and the README body ("26 tools with 234 operations"), suggesting documentation may lag behind the actual implementation and undermining confidence in the accuracy of declared behavior. The server depends on exclusive local COM access to a running Excel process, and failure modes (Excel not installed, file locked by another process) are not concretely documented. Per the static calibration rule, reliability cannot exceed 12 without verifiable execution evidence (real CI + committed tests), and the thin evidence here pushes the score further down.
Security and permissions 9/20
The server runs locally via COM against a real Excel instance and does not appear to transmit credentials over a network, so classic secret-leakage risk is low. However, it can execute arbitrary VBA macros ("Run the UpdatePrices macro"), modify or delete worksheets, and overwrite workbook content, and none of the provided material describes confirmation prompts, scoping, or least-privilege controls before such destructive/dangerous operations. IRM/AIP-protected file handling is mentioned but its data-boundary implications are not explained. Arbitrary VBA execution is a real code-execution risk vector with no described mitigation, which is a meaningful deduction — though it does not meet the red-line bar (no evidence of malware, covert exfiltration, or fabricated test/maintainer claims).
Maintenance 15/20
The project shows healthy signals: 423 stars, only 5 open issues, not archived, a clear MIT license, CI badges, a formal versioned release (v1.0.0), a release process, plus CONTRIBUTING.md and PRIVACY.md files, indicating active, single-owner maintenance (the author also maintains several sibling MCP projects). No explicit security-response channel or SECURITY.md is evident in the supplied material, and dependency-update policy is not described, so it falls short of full marks.
Documentation 15/20
Documentation is layered and fairly extensive: a detailed README, a separate FEATURES.md reference, split CLI/MCP installation guides, example prompts, benchmark data, and an architecture diagram. However, the mismatch between the repo description and README on tool/operation counts signals possible documentation drift from the actual codebase, and troubleshooting/cost/limitation coverage (beyond the Windows/Excel requirement) is comparatively shallow. Overall usable but with hidden assumptions and minor inconsistencies, warranting a deduction.
Setup experience 13/20
Multiple installation paths are documented (one-click VS Code extension, Claude Desktop .mcpb, standalone executable, dotnet tool install, npx add-mcp auto-configuration) with per-client guidance. Still, the full path involves several manual steps (installing/using Excel as a prerequisite, installing the executable or dotnet tool, then running a separate npx step to configure the MCP client, with Node.js as an added dependency for that step), and the tool is restricted to Windows with Excel installed. This is a workable but still manual, multi-step, platform-constrained setup. Per the static calibration rule, setup cannot exceed 15 without verifiable execution evidence.

Static review · not runListed 2026-08-26

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or code

Best for

  • Data analysts automating repetitive Excel workflows
  • Developers building Excel-based data solutions
  • Business users managing complex Excel workbooks
  • Teams maintaining Power Query/VBA/DAX code in Git

Not for

  • Server-side data processing (use libraries like ClosedXML or EPPlus instead)
  • Linux or macOS users (Windows plus a local Excel install is required)
  • High-volume batch processing workloads

Required permissions

  • Controls the local Excel.Application process via Windows COM automation
  • Requires exclusive access to the Excel workbook files it operates on
  • Creates and modifies workbook files (e.g. .xlsx) on disk during automation

Risks and side effects

  • Drives a real local Excel process and edits real workbooks, so files should be backed up or version-controlled before automation
  • Supports running VBA macros, which can execute arbitrary code if the macro source is untrusted
  • Not an official Microsoft product — maintained by an independent community developer, not Excel or MCP's upstream owner
  • Requires exclusive workbook access, which can conflict with other processes that have the file open

Setup

Before you start

Runtime：Prebuilt binary · .NET 10

1) VS Code users: install the extension from the marketplace (one-click, recommended). 2) Claude Desktop users: download the .mcpb file from the latest GitHub release and install it. 3) Any other MCP client: download mcp-excel.exe from the latest release and add it to PATH. 4) Alternatively install via dotnet tool install --global Sbroenne.ExcelMcp.McpServer (requires the .NET 10 runtime), then auto-configure your agent with npx add-mcp "mcp-excel" --name excel-mcp. 5) Before use, close all open Excel files and make sure Excel 2016 or later is installed locally.

Check that it works

Check that tools like range and range_format appear in your MCP client's tool list; then ask it to write data to A1:B2 in a new workbook and confirm the change is visible in the opened Excel window.

Troubleshooting

  1. Confirm you're on Windows with Excel 2016 or later installed
  2. Close all open Excel workbook files before running the server to avoid exclusive-access conflicts
  3. If installed via dotnet tool, verify the .NET 10 runtime is present
  4. If the npx add-mcp auto-configuration step fails, verify Node.js is installed
  5. For high token usage, consider switching to the CLI (excelcli) instead of the full MCP tool set

Things to try

Once connected, you can ask your AI assistant things like:

  • Put this data in A1:C4 - Name, Age, City / Alice, 30, Seattle / Bob, 25, Portland
  • Format the Price column as currency
  • Make the headers in A1:G1 bold and auto-fit the column widths
  • Add a formula column that calculates Quantity times Unit Price in A1:C4

Tools 2

range writes
Reads and writes cell values, formulas, number display formats, and data validation for a range.
range_format writes
Applies visual styling — fonts, fills, borders — and column auto-fit to a range.

Use cases

Creating new Excel workbooks and populating them with sample data or tables
Importing data with Power Query, loading it to the Data Model, and creating DAX measures
Building PivotTables, charts, and interactive slicers from existing data
Formatting ranges (number formats, conditional formatting, styling) and converting them to Excel Tables
Running or managing VBA macros, and exporting Power Query M code for version control

Supported clients

Claude Desktop
VS Code
GitHub Copilot

Listed from the project's documentation, not tested by this site.

Overview

MCP Server for Excel (repo mcp-server-excel) is an open-source (MIT-licensed) Model Context Protocol server written in .NET that drives the actual Excel application through its Windows COM API, rather than just parsing .xlsx files. It lets conversational AI assistants such as GitHub Copilot and Claude automate worksheets, Power Query, DAX measures, VBA macros, PivotTables, charts, conditional formatting, slicers, named ranges and data connections through natural language. The project also ships a feature-parity CLI (excelcli) for coding agents, sharing the same core commands as the MCP server. It requires Windows with Excel 2016 or later installed, and all Excel files must be closed before use since the server needs exclusive access to workbooks.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →
Compare with other MCP servers

Source revision 70c4ded99c8a Data synced 2026-10-19 Read the FMRS scoring method