Tinybird MCP server

Features

• Query Tinybird Data Sources using the Tinybird Query API
• Get the result of existing Tinybird API Endpoints with HTTP requests
• Push Datafiles

Usage examples

• Bluesky metrics (Claude transcript)
• Web analytics starter kit metrics (video]

Setup

Installation

Using MCP package managers

npx @smithery/cli install @tinybirdco/mcp-tinybird --client claude

npx @michaellatman/mcp-get@latest install mcp-tinybird

Prerequisites

• Tinybird Account & Workspace
• Claude Desktop
• uv

Configuration

1. Configure Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json

%APPDATA%/Claude/claude_desktop_config.json

<TINYBIRD_API_URL>

<TINYBIRD_ADMIN_TOKEN>

{
    "mcpServers": {
        "mcp-tinybird": {
            "command": "uvx",
            "args": [
                "mcp-tinybird",
                "stdio"
            ],
            "env": {
                "TB_API_URL": "<TINYBIRD_API_URL>",
                "TB_ADMIN_TOKEN": "<TINYBIRD_ADMIN_TOKEN>"
            }
        }
    }
}

2. Restart Claude Desktop

SSE mode

uvx mcp-tinybird sse

Prompts

• tinybird-default: Assumes you have loaded some data in Tinybird and want help exploring it.
  • Requires a "topic" argument which defines the topic of the data you want to explore, for example, "Bluesky data" or "retail sales".

• Create a prompts Data Source in your workspace with this schema and append your prompts. The MCP loads

  prompts

  on initialization so you can configure it to your needs:

SCHEMA >
    `name` String `json:$.name`,
    `description` String `json:$.description`,
    `timestamp` DateTime `json:$.timestamp`,
    `arguments` Array(String) `json:$.arguments[:]`,
    `prompt` String `json:$.prompt`

Tools

• list-data-sources

  : Lists all Data Sources in the Tinybird Workspace

• list-pipes

  : Lists all Pipe Endpoints in the Tinybird Workspace

• get-data-source

  : Gets the information of a Data Source given its name, including the schema.

• get-pipe

  : Gets the information of a Pipe Endpoint given its name, including its nodes and SQL transformation to understand what insights it provides.

• request-pipe-data

  : Requests data from a Pipe Endpoints via an HTTP request. Pipe endpoints can have parameters to filter the analytical data.

• run-select-query

  : Allows to run a select query over a Data Source to extract insights.

• append-insight

  : Adds a new business insight to the memo resource

• llms-tinybird-docs

  : Contains the whole Tinybird product documentation, so you can use it to get context about what Tinybird is, what it does, API reference and more.

• save-event

  : This allows to send an event to a Tinybird Data Source. Use it to save a user generated prompt to the prompts Data Source. The MCP server feeds from the prompts Data Source on initialization so the user can instruct the LLM the workflow to follow.

• analyze-pipe

  : Uses the Tinybird analyze API to run a ClickHouse explain on the Pipe Endpoint query and check if indexes, sorting key, and partition key are being used and propose optimizations suggestions

• push-datafile

  : Creates a remote Data Source or Pipe in the Tinybird Workspace from a local datafile. Use the Filesystem MCP to save files generated by this MCP server.

Development

Config

.env

TB_API_URL=
TB_ADMIN_TOKEN=

{
  "mcpServers": {
    "mcp-tinybird_local": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/your/mcp-tinybird",
        "run",
        "mcp-tinybird",
        "stdio"
      ]
    }
  }
}

"mcpServers": {
  "mcp-tinybird": {
    "command": "uvx",
    "args": [
      "mcp-tinybird"
    ]
  }
}

Building and Publishing

1. Sync dependencies and update lockfile:

uv sync

1. Build package distributions:

uv build

dist/

1. Publish to PyPI:

uv publish

• Token:

  --token

  or

  UV_PUBLISH_TOKEN

• Or username/password:

  --username

  /

  UV_PUBLISH_USERNAME

  and

  --password

  /

  UV_PUBLISH_PASSWORD

Debugging

npm

npx @modelcontextprotocol/inspector uv --directory /Users/alrocar/gr/mcp-tinybird run mcp-tinybird

Monitoring