Quick start
Stdio (Claude Desktop, Cursor, Zed)
Add Tell to your MCP client configuration:HTTP/SSE
If your Tell server has MCP enabled, connect via HTTP:What you can do
Once connected, ask your AI assistant things like:- “Show me daily active users for the last 30 days”
- “Which events are tracked most frequently?”
- “Find users most likely to churn”
- “Create a dashboard with DAU, WAU, and top events”
- “Are there any anomalies in the logs?”
Tools
Workspace discovery
Data discovery and querying
Boards
Sharing
Data exploration
ML enrichment
User segments
Authentication
Tools authenticate using an API key. You can provide it in three ways:- Environment variable — set
TELL_API_KEYin your MCP client config - Per-tool parameter — pass
api_keyto any tool call - Environment reference — use
env:MY_VAR_NAMEto read from an environment variable
Permissions
Most tools work with any authenticated user. Two tools require Admin or higher:
Board updates and deletions require board ownership or Admin role.
Recommended workflow
The MCP server includes instructions that guide AI assistants through the best workflow:list_workspaces— find your workspace IDworkspace_info— learn the data model before queryingrun_board— use existing dashboards for standard metrics (DAU, MAU, events)list_events— discover what’s being trackedquery— write SQL for ad-hoc analysisexplore_data— drill down into raw dataenrichment_status,churn_risk/anomaly_summary— check ML insights
SQL query security
Thequery tool enforces multiple layers of protection:
- SELECT only — no INSERT, UPDATE, DELETE, DROP, or ALTER
- Workspace scoping — queries are automatically scoped to your workspace
- Function blocking — 40+ dangerous functions are blocked (file access, remote connections, system info)
- No cross-workspace access — queries can’t reference other workspace databases
What’s next
- Blocks — the streaming block format that MCP tools use for generative UI
- CLI Commands —
tell mcpand other CLI tools - Ask — query your data with AI from the command line