Mcp

Point Claude Code, Cursor, or any MCP client at your Morse AI data. POST /api/v1/mcp is a stateless, hosted MCP server — no local process to install or run.

A local, npx-installed stdio MCP server is planned but not built yet (deferred to AGE-221). The only way to use Morse over MCP today is the hosted HTTP endpoint on this page.

How it works

Endpoint


POST https://api.morsehq.dev/api/v1/mcp

GET and DELETE are not supported — this is a stateless request/response endpoint, not a long-lived SSE session.

Auth

Same bearer API key as the SDK and OTLP ingest.

Protocol

Stateless JSON-RPC 2.0. Supported methods: initialize, ping, tools/list, tools/call, and notifications/* (acknowledged, no-op). There’s no session ID and no SSE stream.

Tools

Every tool call is routed through the same registry that powers Copilot — tool results reflect your org’s actual data, scoped server-side so an MCP caller can’t pass a different org or user than the API key resolves to.

All 15 exposed tools are read-only:

search_traces, get_trace_detail, get_span_detail, get_trace_correlation
get_agent_stats, explain_agent_dag, analyze_critical_path
analyze_costs
search_logs
list_alerts
get_org_risks, get_investigations, get_cpso, get_operating_summary
search_docs

How to use it

Configure your MCP client (Claude Code, Cursor, etc.) with the endpoint above and your Morse API key as the bearer token.
Ask it questions that need real data — “what agents failed most this week”, “what’s driving cost on the checkout agent” — and it calls the matching tool.
Every result is scoped to your org automatically; there’s no way to query another org’s data through this endpoint.

Copilot — the same tool registry, used conversationally inside the app.
OTLP integration — the other direction: getting data in, without the SDK.

Mcp