Skip to content

ExcelMcp 1.10.0

Choose a tag to compare

@github-actions github-actions released this 23 Jul 05:25
8988f67

ExcelMcp 1.10.0

What's New

Minor Changes

  • #734 8988f67 Thanks @sbroenne! - Read existing conditional formatting rules (#730): the conditionalformat tool now supports list-rules (per range) and list-worksheet-rules (entire sheet). Both return each rule's type, operator, formulas, applies-to range, priority, and formatting (interior/font/borders) with colors as #RRGGBB hex strings, in priority order — enabling round-trip safety, debugging, migration, and audit workflows before modifying or clearing rules.

Patch Changes

  • #713 25473ac Thanks @github-actions! - Release automation: auto-merge the changelog PR. The post-release step that opens the chore/changelog-vX PR now also merges it (queued auto-merge, falling back to an immediate squash merge). Previously the PR was only created and left open until a maintainer merged it by hand, which caused several releases to sit with a stale/missing CHANGELOG on main.

  • #714 7cad2f4 Thanks @sbroenne! - Faster commits for docs-only changes. The pre-commit hook now treats the gh-pages/ documentation website as docs and skips the Release build, smoke tests and all release-packaging gates when a commit touches only documentation (Markdown, docs/, gh-pages/, changesets). Code commits still run the full validation suite, so nothing that ships is left unchecked — documentation edits just no longer wait minutes for binary/packaging gates that cannot be affected by them.

  • #729 6f74c60 Thanks @sbroenne! - Further reduced Log Analytics ingestion cost for MCP Server telemetry. Application Insights heartbeat (HeartbeatState) and performance counter telemetry (Requests/Sec, Private Bytes, % Processor Time, etc.) are no longer ingested, despite the Application Insights SDK providing no in-process way to disable them in this version — they accounted for roughly a third of remaining telemetry ingestion volume. A Log Analytics ingestion-time transform (Data Collection Rule) now drops these rows server-side, plus the previously-missed http.client.request.duration HTTP-client metric. This Data Collection Rule is now defined in infrastructure/azure/appinsights-resources.bicep (previously only configured manually in Azure, at risk of being lost on redeployment).

  • #727 163d9b2 Thanks @sbroenne! - Automated Excel integration testing. A cost-optimized self-hosted Windows runner now executes the real Excel integration suite for ready pull requests, including VBA and session tests. Targeted manual runs support surgical feature validation during development, while only the full-suite check satisfies the merge gate. The runner starts on demand and is deallocated after testing. Formula reads now report correct worksheet coordinates and actionable suggestions for cell errors, and locked or invalid workbook paths are rejected before Excel starts.

  • #722 8e6d9f1 Thanks @sbroenne! - More reliable Python in Excel results. pythoninexcel get-result now detects when the Microsoft-hosted Python backend has finished computing by reading Excel's calculation state and the cell's #BUSY! placeholder directly, instead of guessing based on whether the value looked "stable" across repeated reads. The old heuristic could lock onto a stale placeholder and return the wrong value, which is why it needed retry loops to be dependable. A single get-result call now converges deterministically, and the default wait was raised from 15s to 30s to comfortably cover cold-start round-trips.

  • #725 2b2b5df Thanks @sbroenne! - Reduced MCP Server telemetry noise and cost. The MCP Server no longer reports the .NET runtime's built-in HTTP-client connection-pool metrics (http.client.open_connections, http.client.active_requests, http.client.connection.duration, http.client.request.time_in_queue, http.client.request.duration) to Application Insights. These were emitted automatically by the telemetry SDK regardless of actual traffic and accounted for the large majority of telemetry ingestion volume, without providing any useful signal for this tool.

Installation Options

VS Code Extension (Recommended)

  • Search "ExcelMcp" in VS Code Marketplace and click Install
  • Or download excelmcp-1.10.0.vsix below
  • Self-contained: no .NET runtime or SDK required
  • Includes both MCP Server and CLI (excelcli)
  • Agent skills (excel-mcp + excel-cli) registered automatically via chatSkills

Claude Desktop (MCPB)

  • Download excel-mcp-1.10.0.mcpb and double-click to install

Standalone Executables (Primary — no .NET runtime required)

  • MCP Server: Download ExcelMcp-MCP-Server-1.10.0-windows.zip, extract mcp-excel.exe
  • CLI: Download ExcelMcp-CLI-1.10.0-windows.zip, extract excelcli.exe
  • Add the exe(s) to your PATH, then configure your MCP client with command mcp-excel

NuGet (.NET Tool) (Secondary — requires .NET 10 runtime)

dotnet tool install --global Sbroenne.ExcelMcp.McpServer
dotnet tool install --global Sbroenne.ExcelMcp.CLI

Agent Skills (for AI coding assistants)

  • VS Code Extension includes both skills automatically (excel-mcp + excel-cli)
  • Install via Skills CLI: npx skills add sbroenne/mcp-server-excel --skill excel-cli or --skill excel-mcp
  • Or download excel-skills-v1.10.0.zip

Requirements

  • Windows OS
  • Microsoft Excel 2016+
  • No .NET runtime required for VS Code Extension, MCPB, or standalone executables
  • .NET 10 Runtime required for NuGet (.NET tool) installation only

Documentation