Local OpenRouter cost analytics, reports, experiments and routing presets over MCP stdio.
Connect Runs on your machine
claude mcp add openrouter-analytics-mcp -e OPENROUTER_MANAGEMENT_KEY=<OPENROUTER_MANAGEMENT_KEY> -e OPENROUTER_WORKBENCH_DATA_DIR=<OPENROUTER_WORKBENCH_DATA_DIR> -- npx -y @cyuanxv/[email protected]{
"mcpServers": {
"openrouter-analytics-mcp": {
"command": "npx",
"args": [
"-y",
"@cyuanxv/[email protected]"
],
"env": {
"OPENROUTER_MANAGEMENT_KEY": "<OPENROUTER_MANAGEMENT_KEY>",
"OPENROUTER_WORKBENCH_DATA_DIR": "<OPENROUTER_WORKBENCH_DATA_DIR>"
}
}
}
}{
"mcpServers": {
"openrouter-analytics-mcp": {
"command": "npx",
"args": [
"-y",
"@cyuanxv/[email protected]"
],
"env": {
"OPENROUTER_MANAGEMENT_KEY": "<OPENROUTER_MANAGEMENT_KEY>",
"OPENROUTER_WORKBENCH_DATA_DIR": "<OPENROUTER_WORKBENCH_DATA_DIR>"
}
}
}
}{
"servers": {
"openrouter-analytics-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cyuanxv/[email protected]"
],
"env": {
"OPENROUTER_MANAGEMENT_KEY": "<OPENROUTER_MANAGEMENT_KEY>",
"OPENROUTER_WORKBENCH_DATA_DIR": "<OPENROUTER_WORKBENCH_DATA_DIR>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
OPENROUTER_MANAGEMENT_KEYRequired, secret | Your own OpenRouter Management Key; keep it in the MCP client secret environment. |
OPENROUTER_WORKBENCH_DATA_DIRRequired | Absolute dedicated private data directory for the local SQLite database. |
Details
| Package | @cyuanxv/[email protected] (NPM, stdio) |
| First published | 22 Oct 2026 |
| Last updated | 22 Oct 2026 |
| Registry name | io.github.cyuanxv/openrouter-analytics-mcp |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.