Spanly vs Langfuse MCP
Spanly is an MCP server published by spanly.com. Marketplaces we read that list it: 1 (Official MCP Registry). Langfuse MCP is an MCP server published by avivsinai. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-25. 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 |  Spanly |  Langfuse MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.14.0 Downloads/month (PyPI): 8 895 Downloads/week (PyPI): 2 824 Forks (GitHub): 29 Stars (GitHub): 112 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.14.0 Downloads/month (PyPI): 8 895 Downloads/week (PyPI): 2 824 Forks (GitHub): 29 Stars (GitHub): 112 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 | Spanly | Langfuse MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 112 |
| Forks (GitHub) (differs) | No figure on GitHub | 29 |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | Remote server (mcp.spanly.com) | On your machine (langfuse-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/avivsinai/langfuse-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 19 h ago | 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
Spanly
MCP observability. Query live traffic, errors, duration, and alerts from your AI agent.
Langfuse MCP
Langfuse MCP server for accessing and analyzing telemetry data via natural language
How to run each
Spanly As a remote MCP server
claude mcp add --transport http spanly https://mcp.spanly.com/Langfuse MCP As a local MCP server: PyPI package
claude mcp add --env "LANGFUSE_PUBLIC_KEY=<YOUR_LANGFUSE_PUBLIC_KEY>" --env "LANGFUSE_SECRET_KEY=<YOUR_LANGFUSE_SECRET_KEY>" --transport stdio langfuse-mcp -- uvx langfuse-mcpRequires: LANGFUSE_PUBLIC_KEY (secret), LANGFUSE_SECRET_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Spanly 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 Spanly publish no settings it asks for, so we do not compare settings.
What it can do: Spanly · What it can do: Langfuse MCP · 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.