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
| Tool | What it does |
|---|---|
list_workspaces | List workspaces you have access to with your role in each |
Data discovery and querying
| Tool | What it does |
|---|---|
workspace_info | Get the complete data model — tables, columns, relationships, query patterns. Call this first before writing SQL. |
list_columns | List column names and types for a specific table (Admin+) |
query | Execute a read-only SQL query against your analytics data (Admin+) |
Boards
| Tool | What it does |
|---|---|
list_boards | List dashboards in a workspace |
get_board | Get a board’s full configuration — blocks, series, visualizations |
create_board | Create a new dashboard with metric blocks |
update_board | Update a board’s title, description, or blocks |
delete_board | Permanently delete a board |
run_board | Execute all metric series in a board and return the results |
Sharing
| Tool | What it does |
|---|---|
share_board | Create a public share link for a board |
get_share_link | Check if a board has an existing share link |
Data exploration
| Tool | What it does |
|---|---|
list_events | Discover top events by count and percentage |
explore_data | Browse raw rows from events, sessions, users, or logs with filters |
ML enrichment
| Tool | What it does |
|---|---|
enrichment_status | Check if ML predictions are active and how many events are enriched |
churn_risk | Find users most likely to churn, sorted by risk score |
anomaly_summary | Summarize anomalous log patterns by source |
segment_overview | Show user distribution across ML-assigned segments |
User segments
| Tool | What it does |
|---|---|
list_segments | List available segment definitions (lifecycle and engagement) |
segment_counts | Count users per segment with percentages |
segment_users | List users in a specific segment with stats |
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:| Tool | Required role |
|---|---|
query | Admin+ (raw SQL access) |
list_columns | Admin+ (schema inspection) |
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