Tiger CLI is the command-line interface for Tiger Cloud. It provides commands for managing and querying database services, as well as an integrated
If you already use Tiger Cli, the tiger cli mcp server is the piece that lets your assistant work with it directly. Tiger CLI is the command-line interface for Tiger Cloud. It provides commands for managing and querying database services, as well as an integrated Model Context Protocol (MCP) server for use with AI assistants.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
login — Log in to your Tiger accountlogout — Log out from your Tiger accountstatus — Show current authentication status and project IDlist — List all servicescreate — Create a new serviceget — Show detailed service information (aliases: describe, show)fork — Fork an existing servicestart — Start a stopped servicestop — Stop a running serviceresize — Resize service CPU and memory allocationdelete — Delete a serviceupdate-password — Update service master passwordSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Configuration is passed through the environment: TIGER_PUBLIC_KEY, TIGER_SECRET_KEY, TIGER_SERVICE_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tiger Cli's toolset — login, logout, status and 11 more — is a fair guide to whether it matches your workflow. It is maintained by timescale; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| login | Log in to your Tiger account |
| logout | Log out from your Tiger account |
| status | Show current authentication status and project ID |
| list | List all services |
| create | Create a new service |
| get | Show detailed service information (aliases: describe, show) |
| fork | Fork an existing service |
| start | Start a stopped service |
| stop | Stop a running service |
| resize | Resize service CPU and memory allocation |
| delete | Delete a service |
| update-password | Update service master password |
| logs | View service logs |
| connect | Connect to a database with psql (in an interactive terminal, if the service has read replicas, offers to connect to one of them; use --no-replica-prompt to skip) |
| Variable | Description | Required |
|---|---|---|
| TIGER_PUBLIC_KEY | Credential the server authenticates with. | Yes |
| TIGER_SECRET_KEY | Credential the server authenticates with. | Yes |
| TIGER_SERVICE_ID | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.