pixl.directory
Tinybird logo

Tinybird

Model Context Protocol (MCP) server for Tinybird, enabling LLMs to interact with real-time analytics and data processing capabilities.

Installation Instructions →

How to Use Model Context Protocol (MCP) in Cursor

What is MCP?

Model Context Protocol (MCP) is an open protocol that allows you to provide custom tools to agentic LLMs (Large Language Models) in Cursor's Composer feature.

Installation Steps

  1. Open Cursor Settings
    • Navigate to Cursor Settings > Features > MCP
    • Click the "+ Add New MCP Server" button
  2. Configure the Server
    • Name: Give your server a nickname
    • Type: Select the transport type (stdio or sse)
    • Command/URL: Enter either:
      • For SSE servers: The URL of the SSE endpoint
      • For stdio servers: A valid shell command to run the server

Example Configurations

For stdio Server (Tinybird Example):

Command: node ~/mcp-quickstart/tinybird-server/build/index.js --token $TINYBIRD_TOKEN --datasource $TINYBIRD_DATASOURCE

For SSE Server:

URL: https://api.tinybird.co/v0/sse

Using MCP Tools

Tool Availability

  • • After adding a server, it will appear in your MCP servers list
  • • You may need to click the refresh button to populate the tool list

Using Tools in Composer

  • • The Composer Agent automatically uses MCP tools when relevant
  • • You can explicitly prompt tool usage by:
    • Referring to the tool by name
    • Describing the tool's function

Tool Execution Process

  • • Displays a message in chat requesting approval
  • • Shows tool call arguments (expandable)
  • • Executes the tool upon user approval
  • • Displays the tool's response in the chat

Important Notes

  • • MCP tools may not work with all models
  • • MCP tools are only available to the Agent in Composer
  • • For Tinybird integration, you need to set up TINYBIRD_TOKEN and TINYBIRD_DATASOURCE environment variables
  • • Generate an API token from your Tinybird workspace settings
  • • Create and specify your datasource name in the Tinybird UI
  • • For security, use a wrapper script that sets the environment variables before running the server
  • • Consider using read-only tokens for query-only operations
  • • Be mindful of query complexity and data ingestion limits
  • • Use appropriate token scopes based on your data access needs
← Back to Home