LabscoMCP early access ↗
timescaleMCP SERVER · OFFICIAL PROJECT

Tiger MCP

Manage Tiger Cloud services and query them from an assistant — and in read-only mode the write tools are never registered at all.

by timescale ↗Relational SQL Databases✓ Official

LABSCO SUMMARY

Read-only here means the write tools are not on the list.

Plenty of servers offer a safe mode that still advertises destructive tools and refuses at call time. This one unregisters them, so the assistant never sees the create, fork, resize or stop tools when it enumerates what is available, and its queries run on a connection the server rejects writes on. Paired with the row cap on query results, that is what makes pointing it at a real project reasonable.

What it is

The MCP server built into Tiger CLI, the command-line interface for Tiger Cloud. tiger mcp install writes the configuration for a client and tiger mcp start runs the server; it exposes service lifecycle and database tools, and proxies a remote documentation server for PostgreSQL, TimescaleDB and Tiger Cloud material. It reuses whatever authentication and configuration the CLI already holds.

What you get

  • Service lifecycle from the client — service_list, service_get, service_create, service_fork, service_start, service_stop, service_resize, service_update_password, service_logs
  • SQL execution against a service with parameterized queries, custom timeouts and connection pooling — db_execute_query
  • The schema as readable text for a model: tables, views, materialized views, enums, functions, procedures, indexes, triggers, and TimescaleDB hypertable and continuous aggregate metadata — db_schema
  • Documentation tools proxied from pg-aiguide and enabled by default: natural-language search of PostgreSQL and TimescaleDB docs, and guides for features and best practices — search_docs, view_skill; turn the proxy off with tiger config set docs_mcp false
  • A cap on how much a query can pour into the model's context — mcp_max_rows, default 100, applied to the query tool only and not to CLI commands
  • A read-only mode that removes rather than refuses: with read_only set, the create, fork, start, stop, resize and update-password tools are not registered, so they never appear in tools/list, and the query tool opens the session in Tiger Cloud's immutable read-only mode where the server itself rejects writes and DDL. The schema tool always opens a read-only session regardless of the setting
  • One-command install for Claude Code, Codex, Cursor, Gemini CLI, VS Code and Windsurf — tiger mcp install prompts for the client, or takes it as an argument
  • Stdio by default, or Streamable HTTP with tiger mcp start http --port 8080 and http://localhost:8080 as the client's URL
  • A way to see the surface before wiring it up — tiger mcp lists the available tools, prompts and resources, and describes any one of them in detail

Requirements

A Tiger Cloud account, authenticated once with tiger auth login; after that the MCP server picks up the CLI's credentials and configuration and needs no separate setup. TIGER_PUBLIC_KEY and TIGER_SECRET_KEY take priority over stored credentials if you would rather pass them through the environment, and TIGER_READ_ONLY mirrors the read-only setting. Install the CLI with curl -fsSL https://cli.tigerdata.com | sh, Homebrew (brew install --cask timescale/tap/tiger-cli), the Debian or Red Hat package repositories, or go install github.com/timescale/tiger-cli/cmd/tiger@latest. Configuration lives at ~/.config/tiger/config.yaml by default, overridable per-variable with the TIGER_ prefix. Apache 2.0 licensed.

Setup effort

One command — curl -fsSL https://cli.tigerdata.com | sh

See installation options