excel-mcp-server

Provides an MCP server (stdio by default; optional SSE HTTP transport) for reading and writing Microsoft Excel spreadsheets (xlsx/xlsm/xltx/xltm), including reading/writing cell text and formulas, and (on Windows) capturing sheet ranges as images.

Evaluated Apr 04, 2026 (17d ago)

Repo ↗ Ai Ml mcp excel spreadsheet file-io stdio-transport sse windows nodejs

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

TLS/auth are not documented for the SSE endpoints; if exposed, it may be vulnerable to unauthorized access. Tooling accepts absolute file paths, so the primary risk is over-permission to the filesystem. No secret-handling details are provided; since configuration uses environment variables for server behavior, avoid logging those env vars.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You need local/agent-driven Excel range I/O through MCP tools and can supply absolute file paths accessible to the server process.

Avoid When

You cannot control or sandbox file access, or you require fine-grained auth, auditing, and tenant isolation.

Use Cases

• Extracting and paging through data from Excel worksheets via an agent
• Programmatically updating specific ranges in an Excel workbook (values and formulas)
• Reading formulas from Excel for downstream analysis or transformation
• Capturing worksheet images on Windows for visual QA/workflows

Not For

• Running with untrusted files from unknown sources in a high-security environment (Excel parsing/writing can be risky)
• Complex spreadsheet operations beyond simple range reads/writes (e.g., full recalculation/sophisticated Excel semantics)
• Use as a multi-tenant hosted API requiring built-in authentication/authorization

Interface

REST API

Yes

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: None described (local MCP tool process).

OAuth: No Scopes: No

No authentication mechanism is described for MCP tool usage. For SSE transport, the server exposes HTTP endpoints (e.g., /command, /status, /sse) but no auth is documented.

Pricing

Model: n/a (open-source package; NPM distribution referen

Free tier: No

Requires CC: No

No pricing information for a hosted service; appears to be a self-run tool distributed via NPM.

Agent Metadata

Pagination

range-based pagination via read tools (range + knownPagingRanges)

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Server requires absolute file paths accessible to the process environment.
⚠ SSE transport opens HTTP endpoints; ensure network exposure is controlled if used.
⚠ Windows-only image capture may fail on non-Windows hosts.
⚠ Write operations may overwrite cell ranges; agents should carefully choose ranges to avoid unintended changes.

Alternatives

Using Microsoft Graph / Excel APIs (hosted, with auth and auditing) Using document-processing libraries in-process (e.g., Excel parsing libraries) without MCP Building a REST service around an Excel processing library with explicit auth/rate limits

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for excel-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.