Schema | Framedash Game Telemetry MCP Server

Framedash Game Telemetry MCP Server

Describes the environment variables required to run the server.

Name	Required	Description
`FRAMEDASH_API_KEY`	Yes	API key with analytics:read for aggregate tools; the raw query tool additionally requires data:admin
`FRAMEDASH_BASE_URL`	No	API base URL (default: https://app.framedash.dev)
`FRAMEDASH_PROJECT_ID`	No	Default project UUID for project-scoped tools

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }
`resources`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
queryA	Execute a read-only SQL query against the ClickHouse events table. Returns up to `limit` rows (default 100, max 1000).
get_dashboardB	Get project dashboard metrics (KPIs, daily active users, top events).
get_retentionC	Get player retention cohort analysis.
get_funnelC	Analyze event funnels. Requires 2-8 event names as steps.
get_insightsC	Get aggregated insights for a metric grouped by a dimension.
get_heatmapA	Get heatmap grid data for a map. Returns performance metrics per cell.
list_projectsA	Show the project bound to the current API key.
get_project_statusB	Get the status of a project (event counts, last event time, etc.).
list_mapsB	List all maps in the project.
list_contentA	List content registry entries (event names, display labels, etc.).
list_alertsB	List all alert rules in the project.
get_alert_historyA	Get alert event history (trigger/resolve events).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
`projects`	Project bound to the current API key

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/crane-valley/framedash-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server