Zespan MCP server

Zespan provides a hosted MCP (Model Context Protocol) server that lets you query your observability data directly from AI coding tools. Ask questions like “what were the slowest traces in the last hour?” or “run root cause analysis on trace abc123” — without leaving your editor.

Endpoint

https://api.zespan.com/v1/mcp

The server is hosted by Zespan. No local process to run.

Authentication

The MCP server uses personal API keys with the lqtp_ prefix. These are separate from project SDK keys (zsp_) and are scoped to your user account.

Generate a personal API key

Go to Settings → MCP in the Zespan dashboard. Click Generate key, give it a name, and copy the key — it is shown only once.

Client configuration

Claude Desktop
Cursor
Claude Code
Other clients

Open your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the zespan server entry:

{
  "mcpServers": {
    "zespan": {
      "url": "https://api.zespan.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer lqtp_YOUR_PERSONAL_API_KEY"
      }
    }
  }
}

Restart Claude Desktop. You should see Zespan tools listed when you start a new conversation.

Open ~/.cursor/mcp.json (create it if it doesn’t exist) and add:

{
  "mcpServers": {
    "zespan": {
      "url": "https://api.zespan.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer lqtp_YOUR_PERSONAL_API_KEY"
      }
    }
  }
}

Reload Cursor. Zespan tools will be available in Cursor’s agent mode.

Add the server to your Claude Code MCP config (~/.claude/mcp.json):

{
  "mcpServers": {
    "zespan": {
      "url": "https://api.zespan.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer lqtp_YOUR_PERSONAL_API_KEY"
      }
    }
  }
}

Any MCP-compatible client that supports HTTP with custom headers can connect. Use:

URL: https://api.zespan.com/v1/mcp
Header: Authorization: Bearer lqtp_YOUR_PERSONAL_API_KEY

Available tools

The Zespan MCP server exposes 9 tools:

Tool	Description
`list_projects`	List all projects your account has access to
`get_project_overview`	Summary of recent activity — event count, error count, avg latency
`query_traces`	Query traces with filters: model, status, time range, limit
`get_trace`	Full detail of a single trace by trace ID
`get_slow_traces`	Find the slowest traces in a given time window
`get_metrics`	Aggregated cost, latency, and token usage grouped by model, hour, or day
`get_errors`	Error breakdown grouped by error code, message, and model
`natural_language_query`	Submit a natural language question about your observability data
`root_cause_analysis`	Run root cause analysis on a failed trace

Example prompts

Once connected, you can ask your AI assistant:

What were the 5 slowest traces in my production project in the last 24 hours?

Run root cause analysis on trace abc123 — why did it fail?

Show me the cost breakdown by model for the last 7 days.

Are there any error spikes in the last hour?

Next steps

API keys — manage personal and project API keys
Traces — explore traces in the dashboard
ZespanPilot — AI copilot built into the Zespan dashboard

​Endpoint

​Authentication

​Generate a personal API key

​Client configuration

​Available tools

​Example prompts

​Next steps