Tinybird MCP Server

Connect AI agents directly to Tinybird real-time analytics workspaces to query data, run SQL, and call published API endpoints as tools.

Analytics by Tinybird API Key active

Connect (Remote Server) Docs

Overview

Tinybird's official MCP server is a provider-hosted remote server at https://mcp.tinybird.co that exposes a Tinybird workspace to MCP clients. It lets agents explore data sources, generate SQL from natural language, run queries against the Tinybird SQL API, and invoke every published API endpoint in the workspace as an individual tool with its documented parameters.

Authentication is handled with Tinybird tokens passed as a token query string parameter. Admin tokens unlock all tools and the full workspace, while resource-scoped tokens or JWTs let you restrict an agent to specific endpoints, enable multi-tenancy, and control concurrency. For non-default Tinybird regions, a host parameter targets the right API region.

The server speaks Streamable HTTP. Clients that support it can connect directly to the URL; older clients can use the mcp-remote bridge. An earlier open-source implementation at tinybirdco/mcp-tinybird was archived in September 2025 and replaced by this hosted server.

Tools

Tool	Description
`explore_data`	Answer natural language questions about workspace data by orchestrating SQL generation and execution.
`text_to_sql`	Convert a natural language question into a SQL query compatible with the Tinybird SQL API.
`execute_query`	Execute a SQL query against the Tinybird SQL API and return the results.
`list_datasources`	List all data sources in the connected Tinybird workspace.
`list_service_datasources`	List organization and service-level data sources available to the workspace.
`list_endpoints`	List all published API endpoints in the workspace.
`<endpoint_name>`	Every published Tinybird API endpoint is exposed as its own tool, accepting the same parameters defined for that endpoint. JWT tokens scope which endpoints are callable.

Setup Guide

Prerequisites

An active Tinybird account and workspace
A Tinybird Auth Token (admin, resource-scoped, or JWT) from the token dashboard
An MCP client. Streamable HTTP is required, or use the mcp-remote bridge for clients that only support stdio.

Direct URL (Streamable HTTP clients)

Point your MCP client at:

https://mcp.tinybird.co?token=TINYBIRD_TOKEN

Bridge config (stdio-only clients like Claude Desktop)

Add this to your MCP client config (for example, claude_desktop_config.json):

{
  "mcpServers": {
    "tinybird": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.tinybird.co?token=TINYBIRD_TOKEN"
      ]
    }
  }
}

JWT with non-default regions

When using JWT tokens, include the host parameter so the server routes to the correct region:

https://mcp.tinybird.co?token=JWT_TOKEN&host=https://api.REGION.PROVIDER.tinybird.co

Omitting host with a JWT will produce a "Workspace not found" error.

Monitoring usage

Track MCP traffic from inside Tinybird with:

SELECT * FROM tinybird.pipe_stats_rt WHERE url LIKE '%from=mcp%'

Use Cases

Let an agent answer ad-hoc product analytics questions like sessions, retention, or funnel metrics by querying Tinybird data sources in natural language.
Expose a curated set of published Tinybird endpoints to an agent using a scoped JWT, so the agent can only call approved metrics with safe parameters.
Power a customer-facing analytics chatbot with multi-tenant JWTs that restrict each end user to their own data partition.
Generate SQL from natural language for an analyst, validate it with text_to_sql, then execute via execute_query for fast iteration.
Build internal copilots that combine workspace endpoint tools with list_endpoints and list_datasources for self-discovery.

Example Prompts

"List all data sources in the workspace and show me a sample of the events table."
"How many unique users visited the pricing page in the last 7 days, broken down by country?"
"Convert this question into SQL: top 10 referrers by sessions yesterday."
"Call the signups_by_day endpoint for the last 30 days and chart the result."
"Show me which published endpoints are available and describe what each one returns."

Pros

Officially hosted by Tinybird, no self-hosting or container management required.
Fine-grained access control via resource-scoped tokens and JWTs, including multi-tenancy and concurrency limits.
Every published API endpoint is automatically exposed as a typed tool, so workspace changes flow through without server updates.
Built-in observability: MCP traffic shows up in tinybird.pipe_stats_rt for monitoring and debugging.

Limitations

Requires a Tinybird account and workspace, not useful outside the Tinybird ecosystem.
Clients without Streamable HTTP support need the extra mcp-remote bridge step.
JWT users must remember to pass the correct host parameter for non-default regions or requests will fail with "Workspace not found".

Alternatives

ClickHouse MCP server for querying ClickHouse directly (Tinybird is built on ClickHouse).
Motherduck MCP server for serverless DuckDB analytics.
Provider-hosted analytics MCP servers from data warehouses like Snowflake or BigQuery for similar SQL-over-MCP workflows.