Tinybird Data Platform MCP. Audit your real-time data infrastructure via chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Tinybird Data Platform MCP Server connects your AI agent to a real-time analytics engine. You can manage data sources, inspect pipeline logic (Pipes), and execute direct SQL queries against live data—all through natural conversation.
This tool lets you audit complex analytical infrastructure without opening the dashboard.
What your AI agents can do
Execute sql query
Runs an arbitrary SQL query directly against your Tinybird data workspace.
Get datasource details
Fetches detailed information, including schema and metadata, for a specific data source.
Get datasource stats
Retrieves metrics like row counts and total storage size used by a selected data source.
The agent runs custom SQL against your Tinybird workspace, retrieving immediate data results.
You can retrieve a list of all available data sources or get specific details (like schema) for one source.
The system fetches usage metrics, such as row counts and storage sizes, for any given data source.
You can list all defined Pipes or get the detailed SQL logic and nodes of a specific Pipe to understand its flow.
The agent executes a full, published Pipe definition and returns the resulting data set as JSON.
You can list all authentication tokens in the workspace to audit who has access to your data.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Tinybird Data Platform: 10 Tools for Data Ops
These tools let you read the schema, list assets, check stats, run queries, and manage your entire data pipeline stack through natural conversation.
019d848eexecute sql query
Runs an arbitrary SQL query directly against your Tinybird data workspace.
019d848eget datasource details
Fetches detailed information, including schema and metadata, for a specific data source.
019d848eget datasource stats
Retrieves metrics like row counts and total storage size used by a selected data source.
019d848eget pipe details
Gets detailed information about a specific transformation pipe, including its history and configuration.
019d848elist auth tokens
Outputs a list of all authentication tokens currently defined in the workspace.
019d848elist datasources
Retrieves a complete listing of every data source present in your current workspace.
019d848elist pipe nodes
Lists all the individual SQL nodes that make up a specific transformation pipe.
019d848elist pipes
Retrieves a list of every defined data pipeline (Pipe) in your workspace.
019d848elist workspaces
Lists all available workspaces that the admin token has access to.
019d848equery pipe data
Executes a named Pipe and returns the full results as structured JSON data.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Tinybird Data Platform, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Tinybird Data Platform MCP Server connects your agent directly to a real-time analytics engine in Tinybird. You're getting admin-level access, letting you manage everything from raw data ingestion right through complex transformations and ad-hoc queries—all without ever having to open the dashboard yourself.
This isn't just another wrapper; it lets you audit your whole analytical infrastructure using nothing but natural conversation. You can inspect every layer of data processing, check usage metrics on a whim, and run full workflows instantly. It’s like having an expert teammate who knows where all the switches are.
Listing and Inspecting Your Data Sources
You need to know what data you're working with? You can start by running list_workspaces to see every workspace the admin token has access to. From there, use list_datasources to pull a complete list of every single source in your current workspace. If you wanna dig deeper into one specific source, the agent uses get_datasource_details to fetch all the schema and metadata for that data set.
It’s how you verify what columns exist and what type of data they hold.
To check usage stats on a data source—things like row counts or total storage size—you just call get_datasource_stats. You get immediate metrics showing exactly how much data's sitting there. You can also list all the authentication tokens defined in the workspace using list_auth_tokens, which lets you audit who has access to your critical data.
Mapping Out Your Data Pipelines (Pipes)
The core of any analytics stack is its pipes, and this tool gives you full visibility. You can call list_pipes to get a list of every defined transformation pipeline in the workspace. If you need to understand how one specific pipe works—its history, configuration, or logic flow—you use get_pipe_details. This reveals the inner workings of that data process.
Want to see exactly which steps make up a complex pipe? The agent uses list_pipe_nodes to list all the individual SQL nodes that compose any given transformation pipe. It lets you trace the flow from start to finish, making debugging way faster than clicking through menus. You can run predefined data workflows by executing a full Pipe definition using query_pipe_data, and it returns the resulting dataset as structured JSON, ready for your agent to use.
Running Queries and Auditing Security
Need some immediate answers? The agent doesn't rely on pre-built pipes; you can run arbitrary SQL queries directly against your Tinybird data workspace using execute_sql_query. You just type the query, and it gets instant results. If your task is to audit your security setup, listing all authentication tokens via list_auth_tokens gives you a clear rundown of every key available.
Basically, you can list all workspaces (list_workspaces), then list all data sources (list_datasources) and get the schema details for any one source (get_datasource_details). You'll also check usage metrics like row counts or storage size using get_datasource_stats. For transformations, you can list all defined pipes (list_pipes), get a deep dive into a pipe’s configuration via get_pipe_details, and even see every individual node in the process with list_pipe_nodes.
When you're done inspecting, you can run a whole pipeline using query_pipe_data or fire off an immediate, custom query with execute_sql_query. It’s everything your data stack needs, right here.
How Tinybird Data Platform MCP Works
- 1 First, subscribe to this server and provide your Tinybird Admin Token. This grants your AI client necessary administrative permissions.
- 2 Next, prompt the agent with a specific task—for example, 'List all data sources' or 'Get stats for X'.
- 3 The agent calls the appropriate tool (like
list_datasources), receives structured metadata and results, and presents them to you in plain language.
The bottom line is: it turns complex backend API calls into simple chat commands.
Who Is Tinybird Data Platform MCP For?
This is for the data professional who spends too much time clicking through dashboards just to check a number. If you're an engineer who needs to debug pipeline logic at 2 AM, or an analyst who wants quick answers without opening the full UI, this server saves clicks and minutes.
You use list_pipe_nodes and get_pipe_details to quickly audit pipe logic or check data source states during development. You don't want to open the dashboard just to look at a node.
You run quick, ad-hoc queries using execute_sql_query to test hypotheses or confirm numbers without waiting for a data team member to write and execute a report.
You monitor ingestion performance by calling get_datasource_stats and review token scopes using list_auth_tokens, ensuring the platform is running smoothly.
What Changes When You Connect
- Check performance metrics instantly. Instead of navigating to a dashboard tab, ask the agent for
get_datasource_statsand get row counts or storage usage in seconds. - Debug complex pipelines fast. Use
list_pipe_nodesto pull the exact SQL logic from any Pipe without needing admin console access—it shows you exactly how data moves. - Run live tests instantly. Instead of building a report, just tell your agent to run an arbitrary query using
execute_sql_queryand see the results immediately. - Understand everything available. Call
list_datasourcesorlist_pipesto get a clear inventory of every asset in your workspace—you'll know exactly what data exists. - Audit security easily. Run
list_auth_tokensanytime you need to verify which credentials are active and who has access.
Real-World Use Cases
Troubleshooting a missing metric
A product manager notices the 'weekly signups' number is wrong. Instead of filing a ticket, they ask their agent to run get_datasource_stats on the raw signup table and compare that count against the expected value. The stats show an ingestion failure last night, solving the problem before the data team wakes up.
Understanding a flaky report
A data engineer finds a pipe called 'monthly_summary' is giving inconsistent results. They use get_pipe_details and then list_pipe_nodes to see the exact SQL logic for the join. This immediately shows they are joining on an outdated key, fixing the bug in minutes.
Ad-hoc exploratory analysis
An analyst needs to check how many users signed up from a specific region last quarter. They don't want to wait for a dedicated query. They use execute_sql_query directly, running their own custom SQL and getting the count right away.
Inventory check before migration
A DevOps lead is migrating services. Before starting, they call list_datasources to get a comprehensive list of every source in the workspace and then list_workspaces to see if there are any forgotten environments.
The Tradeoffs
Assuming data is clean
Just running execute_sql_query with a complex join, assuming the data sources are up-to-date and correct.
→
Always check first. Use list_datasources to verify the source exists, then use get_datasource_stats to confirm it has recent activity before running any queries.
Overlooking pipeline dependencies
Running a query against a Pipe that depends on a data source that hasn't been updated in days.
→
First, use get_pipe_details to understand the full flow. Then, check the dependency health with list_datasources and get_datasource_stats before executing.
Manually checking schemas
Opening up the UI for every single data source just to verify column names or types.
→
Skip the clicks. Use list_datasources to see what's there, and then run get_datasource_details on any specific one to pull its schema directly into your chat.
When It Fits, When It Doesn't
Use this server if you need administrative control over data assets and want to test hypotheses against real-time data without opening the Tinybird UI. If your goal is simple reporting, stick to a BI tool like Tableau or Looker. Don't use it just because you can run SQL; use it because you need to audit infrastructure. Specifically, if you need to debug how data flows from source -> pipe -> result, then get_datasource_stats and list_pipe_nodes are non-negotiable tools. If your only task is running one single, known query, you might just use execute_sql_query, but for anything involving setup, auditing, or debugging a pipeline, this full suite of tools is necessary.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Tinybird. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Checking data health usually means opening four different tabs and clicking through five menus.
Today, to see if your core `users_data` source is healthy—meaning it actually ingested new records overnight—you gotta jump into the dashboard. You check the data sources tab, then click on the source name, then find the stats panel, and finally scroll down until you see the row count. It's a multi-step pain that wastes time.
With this MCP server, you just ask: "Give me the stats for `users_data`.". The agent handles all those clicks behind the scenes. You get an immediate, clean answer with the current row count and storage size—no dashboard navigation required.
Tinybird Data Platform MCP Server gives you granular control over data pipelines.
Before this server, if a report was wrong, you were stuck. You could run the query (`execute_sql_query`), but if it failed, figuring out *why* meant diving deep into the Pipe's logic flow. Was the join wrong? Did a node fail to load? This required tribal knowledge and manual checks.
Now, you ask the agent for `get_pipe_details`. It pulls up the entire definition, showing you every step and even listing all the nodes via `list_pipe_nodes`. You see the whole process flow in text. That's a massive difference—you debug logic, not just results.
Common Questions About Tinybird Data Platform MCP
How do I see what data sources exist using list_datasources? +
Run list_datasources. This tool immediately returns an inventory of every source in your workspace. It's a quick way to get names and basic metadata without browsing the UI.
Is execute_sql_query safe for production data? +
It runs arbitrary SQL, so treat it like running directly against the database. Always confirm your query logic first by checking source details with get_datasource_details before executing.
What is the difference between list_pipes and query_pipe_data? +
list_pipes only gives you the names of defined pipelines. You must use query_pipe_data to actually execute a pipe and get results.
How do I check authentication tokens using list_auth_tokens? +
Simply call list_auth_tokens. This gives you an audit trail, listing every token ID. It's critical for knowing who or what has access to your data.
What specific metrics does `get_datasource_stats` return? +
It returns usage statistics, including row counts and total storage sizes. You use this tool to track data growth rates or spot sources where ingestion is suddenly dropping off.
How do I examine the transformation logic inside a pipe using `list_pipe_nodes`? +
This tool retrieves all SQL nodes within a specific Pipe ID. It shows the exact sequence of SELECT statements and data transformations, letting you audit the pipeline's internal logic before running it.
If my project uses multiple environments, how do I find them using `list_workspaces`? +
This tool lists all accessible workspaces attached to your account. Remember that any subsequent command—like listing sources or executing queries—must target the correct workspace ID.
What is the difference between `get_datasource_details` and running a query? +
get_datasource_details provides static metadata, like schema structure and connection identifiers. Running an actual query executes code against the live data to return current records.
Where do I find my Tinybird Admin Token? +
Log in to your Tinybird Dashboard, select a workspace, and go to the 'Auth Tokens' section. You can use the Admin Token or create a custom one with the necessary scopes.
Which SQL dialect does Tinybird use? +
Tinybird is powered by ClickHouse, so it uses the ClickHouse SQL dialect, which includes powerful functions for high-performance analytical processing.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Checkly
Manage application monitoring and E2E testing via Checkly — track API uptime, trigger checks, and monitor performance directly from any AI agent.
Grafana
Manage observability via Grafana — search and inspect dashboards, monitor alerts, and handle data sources directly from any AI agent.
pgvector (Vector Database)
Run vector similarity searches, manage embedding tables, and build AI-powered retrieval pipelines — all directly inside your existing PostgreSQL database.
You might also like
RentCast
Automate real estate data and valuation tracking via RentCast — manage properties, rental yields, and market trends directly from any AI agent.
X (Twitter)
Automate social intelligence workflows via X (Twitter) — search recent tweets, retrieve user profiles, and analyze tweet engagement directly from any AI agent.
Zippopotam.us
Global postal code intelligence — lookup city, state, and coordinates by zip code via AI.