Overview - Tembo Docs

Base URLs

Tembo API and self-hosted deployments use the same API operations and schemas.

Tembo API: https://api.tembo.io
Self-hosted: https://{deployment-origin}/api/public-api

Self-hosted deployments use their own deployment origin and currently require the additional /api/public-api path prefix.

Authentication

For the Tembo API, create an API key from Settings > API Keys in the hosted Tembo dashboard. For self-hosted, create an API key in your deployment’s own dashboard. When you create a key, choose when it expires: 7, 30, 60, or 90 days, 1 year, or no expiration. The dashboard defaults to 90 days. Expired keys stop authenticating requests. When creating a key through the API, set expiresAt to a future timestamp, or omit it for a key that never expires.

curl -H "Authorization: Bearer YOUR_API_KEY" \
  https://api.tembo.io/v1/sessions

curl -H "Authorization: Bearer YOUR_API_KEY" \
  https://tembo.example.com/api/public-api/v1/sessions

TypeScript SDK

npm install @tembo-io/sdk

Set the TEMBO_API_KEY environment variable to your API key. Keep it on your server, not in browser code or source control.

import Tembo from '@tembo-io/sdk';

const client = new Tembo();

const sessions = await client.sessions.list({ limit: '5' });
console.log(sessions);

Rust SDK

The Rust SDK is asynchronous. These examples use the Tokio runtime.

cargo add tembo-rs
cargo add tokio --features rt-multi-thread,macros

Tembo::from_env() reads your API key from the TEMBO_API_KEY environment variable.

use tembo_rs::Tembo;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let client = Tembo::from_env()?;

    let sessions = client.sessions().list().limit(5).send().await?;
    println!("{sessions:?}");

    Ok(())
}

Each endpoint page in this API reference shows TypeScript and Rust examples.

MCP server

The Tembo MCP server lets AI clients use the public Tembo API. Its tools are generated from the same OpenAPI schema as the API reference and SDKs.

Connect

Use this remote HTTP MCP endpoint:

https://mcp.tembo.io/mcp

Connect using either OAuth or an API key:

OAuth: Add only the MCP URL. Your client opens Tembo sign-in and asks you to select and authorize an organization.
API key: Send your organization API key as Authorization: Bearer YOUR_API_KEY.

For clients that support static HTTP headers, use:

{
  "mcpServers": {
    "tembo": {
      "type": "http",
      "url": "https://mcp.tembo.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

The server can perform the same API operations available to the authenticated user or API key. Review write operations before approving them in your MCP client.

Self-hosted

Self-hosted deployments expose the MCP server at https://{deployment-origin}/mcp. Connect with an API key created in your deployment. Self-hosted MCP does not require Clerk.

Rate limits

100 requests per minute per API key. 1,000 requests per hour per organization.

​Base URLs

​Authentication

​TypeScript SDK

​Rust SDK

​MCP server

​Connect

​Self-hosted

​Rate limits