Netra exposes a remote MCP server so you can pull observability context directly into your editor or agent workspace.
Choose the MCP endpoint that matches your Netra data region, then replace the
API key placeholder with your own project API key.
Server Details
- Region-specific MCP endpoints:
- Auth header:
x-api-key
NETRA_MCP_ENDPOINT="https://api.getnetra.ai/mcp"
NETRA_API_KEY="<your-api-key-here>"
Client Setup
Cursor
Claude Code
Windsurf
Antigravity
Codex
Add this netra entry to your MCP server configuration in mcp.json:If you’re in the EU region, then use the url https://api.eu.getnetra.ai/mcp.
"netra": {
"url": "https://api.getnetra.ai/mcp",
"headers": {
"x-api-key": "<your-netra-api-key>"
}
}
Add the Netra MCP server directly from the command line:If you’re in the EU region, then use the url https://api.eu.getnetra.ai/mcp.
claude mcp add netra --transport http https://api.getnetra.ai/mcp --header "x-api-key: <your-netra-api-key>"
claude mcp add-json netra '{"type": "http", "url": "https://api.getnetra.ai/mcp", "headers": {"x-api-key": "<your-netra-api-key>"}}'
Add this netra entry to your MCP server configuration in mcp_config.json:If you’re in the EU region, then use the url https://api.eu.getnetra.ai/mcp.
"netra": {
"url": "https://api.getnetra.ai/mcp",
"headers": {
"x-api-key": "<your-netra-api-key>"
}
}
Add this netra server definition to your MCP configuration in mcp.json:If you’re in the EU region, then use the url https://api.eu.getnetra.ai/mcp.
"netra": {
"serverUrl": "https://api.getnetra.ai/mcp",
"headers": {
"x-api-key": "<your-netra-api-key>"
}
}
Add this block to ~/.codex/config.toml:If you’re in the EU region, then use the url https://api.eu.getnetra.ai/mcp.
[mcp_servers.netra]
enabled = true
url = "https://api.getnetra.ai/mcp"
[mcp_servers.netra.http_headers]
x-api-key = "<your-netra-api-key>"
x-api-key should be set in the config file. Why Netra MCP
Integrate Netra’s observability context directly into your development workflow. The Netra MCP server enables your AI coding assistant to query traces, filter performance data, and gain deep system insights without leaving the IDE. By bridging the gap between telemetry and your code, it helps you identify and resolve complex LLM performance issues as they happen.
| Tool | Description |
|---|
netra_get_trace_by_id | Retrieve all spans for a given trace ID |
netra_query_traces | Get traces using trace filters (like the filter field in the dashboard) |
Troubleshooting
- Ensure your JSON/TOML configs are properly formatted
- Confirm the MCP server is reachable at your region-specific MCP endpoint
- Verify your API key is correct and has not expired
- Restart the client after making config changes
Next Step
After saving your config, restart the client and confirm the netra MCP server shows up in the available tools or MCP server list. 