MCP server for Framedash game telemetry: query analytics, heatmaps, perf regressions, and alerts
MCP (Model Context Protocol) server for the Framedash game telemetry platform. Provides 12 read-only tools and 4 resources for querying analytics data from LLM-powered tools.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"framedash": {
"command": "npx",
"args": ["@framedash/mcp-server"],
"env": {
"FRAMEDASH_API_KEY": "fd_xxx",
"FRAMEDASH_PROJECT_ID": "your-project-uuid"
}
}
}
}
Add to your VS Code settings:
{
"claude.mcpServers": {
"framedash": {
"command": "npx",
"args": ["@framedash/mcp-server"],
"env": {
"FRAMEDASH_API_KEY": "fd_xxx",
"FRAMEDASH_PROJECT_ID": "your-project-uuid"
}
}
}
}
| Variable | Required | Description |
|---|---|---|
FRAMEDASH_API_KEY | Yes | API key with analytics:read for the aggregate tools; the raw query tool additionally requires data:admin |
FRAMEDASH_PROJECT_ID | No | Default project UUID for project-scoped tools |
FRAMEDASH_BASE_URL | No | API base URL (default: https://app.framedash.dev) |
If FRAMEDASH_PROJECT_ID is omitted, project-scoped tools still work but
require an explicit project_id argument per call.
| Tool | Description |
|---|---|
query | Execute SQL analytics query (SELECT only, limit default 100) |
get_dashboard | Project KPI summary (DAU, MAU, sessions, events) |
get_retention | Cohort retention data |
get_funnel | Funnel analysis for event steps |
get_insights | Event insights with grouping |
get_heatmap | Heatmap grid data for a map |
list_projects | Show the project bound to the API key |
get_project_status | Project health overview |
list_maps | List maps in a project |
list_content | List content registry entries |
list_alerts | List alert rules |
get_alert_history | Alert trigger history |
| URI | Description |
|---|---|
framedash://projects | Project bound to the API key |
framedash://projects/{projectId}/maps | Map list with bounds |
framedash://projects/{projectId}/content | Content registry |
framedash://projects/{projectId}/status | Project health status |
Run from the repository root:
pnpm install
pnpm --filter @framedash/mcp-server... build
pnpm --filter @framedash/mcp-server test
With pnpm 9, the trailing ... selects the MCP package plus its workspace
dependencies, including @framedash/api-client, before compiling from a clean
checkout.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @framedash/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-crane-valley-framedash-mcp-server": {
"command": "npx",
"args": [
"-y",
"@framedash/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@framedash/mcp-servernpmio.github.crane-valley/framedash-mcp-server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.