Skip to content
Tiger MCP

Tiger MCP

by Timescale
Released
v0.22.0
Apache-2.0
Repository Docs
Databases & Data

Summary

Timescale's official MCP server, bundled with the Tiger CLI — manage Tiger Cloud Postgres services, inspect schemas and hypertables, and search the docs from an AI assistant.

Features

  • Bundled with the Tiger CLI and reuses its `tiger auth login` credentials
  • Service lifecycle: list, create, fork, start, stop, resize, delete, logs, password rotation
  • Schema inspection covering tables, views, indexes, functions and TimescaleDB hypertables
  • Connection strings and connectivity testing for Tiger Cloud databases
  • One-command install for Claude Code, Codex, Cursor, Gemini CLI, VS Code and Windsurf; OCI image on ghcr.io

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Tiger MCP" tools will be available.
{
  "mcpServers": {
    "tiger-mcp": {
      "command": "tiger",
      "args": [
        "mcp",
        "start"
      ]
    }
  }
}

Description

Tiger MCP ships inside the Tiger CLI, Timescale's command-line tool for Tiger Cloud, rather than as a separate package. That matters in practice: the MCP server reuses the CLI's authentication and configuration, so once you have run tiger auth login, the agent is authenticated too, and the same ~/.config/tiger state backs both.

Through it an agent gets programmatic access to Tiger Cloud services and the databases behind them. On the service side that is listing, creating, forking, starting, stopping, resizing and deleting services, plus reading service logs and rotating the master password. On the database side it can fetch connection strings, test connectivity, and — the useful one for an agent writing queries — display schema information including tables, views, indexes, functions and TimescaleDB hypertables, so a generated query respects the time-partitioning layout instead of treating a hypertable as an ordinary table. A documentation surface is exposed alongside, so the assistant can look up current Tiger Cloud and TimescaleDB guidance rather than improvise.

Installation is one command per client: tiger mcp install claude-code, or codex, cursor, gemini, vscode, windsurf; tiger mcp install on its own prompts for the client. For anything not on that list, point the client at tiger mcp start as a stdio command, and tiger mcp list / tiger mcp get enumerate and describe the available tools, prompts and resources before you wire it in. A container image is published to ghcr.io/timescale/tiger-cli, authenticated with TIGER_PUBLIC_KEY and TIGER_SECRET_KEY and needing the config directory and .pgpass bind-mounted in.

Apache-2.0 licensed and versioned with the CLI itself, so tiger upgrade brings the MCP server along with it.

Covered in the Weekly

Related MCP Servers

MCP: Supabase

by Supabase

Manage your Supabase project from an agent — run SQL, inspect tables, manage branches, and generate types.

DatabaseDeployment
Browse all MCP servers →