Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldSalesforce Hosted MCPMCP100 SelectedExcel MCP ServerMCP100 Selected
Task fit
Best for
  • Connect compatible AI clients to Salesforce's documented MCP capabilities.
  • Reading, creating, formatting, charting, and updating XLSX workbooks and worksheets, including formulas and pivot tables
Not ideal for
  • Users who need a fully reviewed MCP100 recommendation today
  • Workbooks that depend on full desktop Excel behavior, macros, or manual visual review
Avoid when
  • Permissions, credentials, and connected data cannot be tested with least privilege
  • You cannot restrict file access or are using a version affected by CVE-2026-40576
Provenance
Provenance details

First-party MCP

Salesforce · Publisher source ↗

Community implementation

Haris Musa · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Apr 12, 2026

Package: Apr 12, 2026

Popularity evidence
GitHub starsNot documented

4,108

GitHub stars · checked 2026-08-14T18:46:26.000Z

External adoption evidenceNot documented
  • github: repository stars: 4,108Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude CodeStreamable HTTP
Claude DesktopStreamable HTTP
CodexStreamable HTTP
VS CodeStreamable HTTP
CursorStreamable HTTP
OpenCodeStreamable HTTP
Claude CodeLocal stdio
Claude DesktopLocal stdio
CodexLocal stdio
VS CodeLocal stdio
CursorLocal stdio
OpenCodeLocal stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationFollow only the publisher source; credential storage, scopes, and revocation remain under review.Local stdio has no separate service authentication. Remote MCP authentication is not documented, so remote listeners must remain network-restricted.
CostPublisher plans, API usage, infrastructure, or per-action charges may apply; MCP100 has not published a cost conclusion.The MIT-licensed local server lists no usage fee; normal hosting, client, model, and network costs may apply.
PermissionsExact permissions and read/write boundaries have not completed MCP100 review.The server can read, create, modify, format, chart, and delete workbook content. Remote modes confine relative paths to EXCEL_FILES_PATH in the patched release.
Data handlingCandidate-specific retention, subprocess, telemetry, and model-data behavior remain review items.Workbook paths and spreadsheet content are processed by the server and returned to the connected client as required by tool calls; publisher telemetry and retention are not documented.
Limitations
Tradeoffs
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
  • It provides deep spreadsheet manipulation without desktop Excel, but write tools can overwrite data and remote transports add network and filesystem exposure.
Risk contextUse a test account, least privilege, read-only controls where available, and explicit approval for mutations.Versions through 0.1.7 have a critical path-traversal vulnerability. Use 0.1.8 or later, prefer stdio, restrict workbook paths, avoid public remote listeners, and keep recoverable backups.
Evidence date
Editorial review2026-07-242026-08-13
Candidate evidence2026-07-30T19:00:00.000Z2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →