Tinybird Quickstarts

website·Indexed 38 days ago

https://www.tinybird.co/clickhouse/knowledge-base

Guides for building on managed ClickHouse with Tinybird, including an overview of what Tinybird adds to ClickHouse.

Tokens
613
Snippets
1
Records
5
Agent score
45%

What's inside Tinybird

  1. Overview of Tinybird's managed ClickHouse capabilities

    Tinybird provides a managed ClickHouse environment optimized for modern development and agentic coding. It extends ClickHouse with the following capabilities:

    • Data Ingestion: Streaming and batch data via the Events API and managed Connections for Kafka, Amazon S3, and Google Cloud Storage.
    • Resources as Code: Define Data Sources, Connections, Pipes, API Endpoints, and Materialized Views using TypeScript, Python, or datafiles.
    • Development Workflow: Support for Tinybird Local, isolated Cloud Branches, and CI/CD deployment pipelines.
    • Data Access: Query data via API Endpoints, the Query API, the ClickHouse interface, or the Model Context Protocol (MCP).
  2. Integrate Tinybird with AI agents

    Tinybird provides two primary ways to enable AI coding agents to interact with your project:

    1. Agent Skills: Provides instructions to compatible coding agents for creating and reviewing project files, SQL, tests, and deployments.
    2. MCP Server: The Tinybird Model Context Protocol (MCP) server gives agents Token-scoped access to a live Workspace to inspect data, run queries, and call published Endpoints.

    For full capability (project guidance + live data access), use both Agent Skills and the MCP server together.

    npx skills add tinybirdco/tinybird-agent-skills
  3. Choose a Tinybird development workflow

    Depending on your preferred language and workflow, you can build with Tinybird using one of three primary methods:

    • Tinybird CLI: Best for those who prefer SQL-first workflows and using datafiles and cloud branches.
    • TypeScript SDK: Best for developers wanting typed resources and a TypeScript-native workflow to define Data Sources and Endpoints.
    • Python SDK: Best for developers wanting Python-native resource definitions and runtime usage, deploying via the Tinybird CLI.
  4. Ingest data into Tinybird

    Tinybird supports multiple ingestion methods:

    • Events API: Used for HTTP streaming.
    • Managed Connections: Used for integrating with Kafka, Amazon S3, and Google Cloud Storage. Connections store credentials and integration settings and are deployed as part of the project code.
    • Local Files: Direct upload of local files.
  5. Manage schema iterations with Cloud Branches

    Tinybird supports data branching via Cloud Branches. These are isolated environments where you can modify schemas, queries, APIs, and connector ingestion without affecting the production environment. A Branch can attach to the latest production partition without copying the underlying data, allowing for validation before deploying to the main Workspace.