Spanly MCP
Overview
The Spanly MCP server gives an agent read access to your telemetry – requests, errors, dashboards, and alerts.
The Spanly MCP server is an MCP server we run, not one you instrument. Point any MCP-compatible agent (Claude Desktop, Cursor, custom) at it and the agent can:
- Search and aggregate requests across your projects.
- Pull out errors and group by code.
- Read dashboards: top servers, top tools, slowest operations.
- Manage alert rules and channels.
- Share links to specific dashboards or requests.
This is how you ask "what changed in the last hour?" or "which tool is slowest on the new server version?" without leaving your chat / IDE.
Endpoint
The Spanly MCP server is hosted at:
https://mcp.spanly.comIt speaks HTTP MCP with bearer-token auth. Use your project's API key as the bearer token – the same key the SDK and CLI use.
Authentication & scope
- Authentication:
Authorization: Bearer spanly_us_…(orspanly_eu_…). - Scope: the API key is bound to a single project. All MCP tool calls resolve against that project's data only.
- Region: encoded in the key prefix and auto-routed.
- Read vs write: most tools are read-only. Tools that change state (alert rules, channels, shared links) require the same project-admin permissions a human user would need in the dashboard.
What's the difference between Spanly MCP and instrumenting?
| Instrumenting (SDK / CLI) | Spanly MCP | |
|---|---|---|
| You run | Your MCP server, wrapped | Just an MCP client |
| Direction | You send data to Spanly | An agent reads data from Spanly |
| Use case | "Capture what my MCP server does" | "Let an agent inspect what Spanly captured" |
The two work together – instrument your MCP server so Spanly has data, then connect an agent via Spanly MCP so it can query that data.
See also
- Connecting – config snippets for Claude Desktop, Cursor, Windsurf, and curl.
- Tools – the full surface of MCP tools the server exposes.