InvokePort vs Excel MCP Server
InvokePort is an MCP server published by gerefull. Marketplaces we read that list it: 1 (Official MCP Registry). Excel MCP Server is an MCP server published by haris-musa. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-30. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Excel MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 No figure published Not marked · First seen |
Listed Version: 2.2.3 Downloads/month (PyPI): 135 901 Downloads/week (PyPI): 91 342 Forks (GitHub): 478 Stars (GitHub): 4 268 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 2.2.3 Downloads/month (PyPI): 135 901 Downloads/week (PyPI): 91 342 Forks (GitHub): 478 Stars (GitHub): 4 268 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | InvokePort | Excel MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 4 268 |
| Forks (GitHub) (differs) | No figure on GitHub | 478 |
| Last release (differs) | 2026-10-20 (worse) | 2026-10-29 (better) |
| Where it runs (differs) | Remote server (invokeport.com/api/mcp) | On your machine (excel-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/haris-musa/excel-mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-28 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
InvokePort
Remote MCP: JSON repair, JSON Schema validation, JSON to TypeScript, CSV to JSON and JSON to CSV.
Excel MCP Server
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
How to run each
InvokePort As a remote MCP server
claude mcp add --transport http invokeport https://invokeport.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: INVOKEPORT_API_KEY (secret), INVOKEPORT_ORIGIN, Authorization header
Excel MCP Server As a local MCP server: PyPI package
claude mcp add --transport stdio excel-mcp-server -- uvx excel-mcp-server stdioCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only InvokePort has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Excel MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: InvokePort · What it can do: Excel MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.