Developer · Local MCP server
Tiger MCP
Provides programmatic access to Tiger Cloud services, databases, and documentation.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.timescale/tiger-cli- Version
- 0.26.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- timescale (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/timescale) · how
- Repository
- github.com/timescale/tiger-cli
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/timescale/tiger-cli:0.26.0 | - | stdio |
How to connect Tiger MCP
Tiger MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/timescale/tiger-cli:0.26.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e TIGER_PUBLIC_KEY -e TIGER_SECRET_KEY ghcr.io/timescale/tiger-cli:0.26.0. It reads these environment variables: TIGER_PUBLIC_KEY (required) and TIGER_SECRET_KEY (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"tiger-cli": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TIGER_PUBLIC_KEY",
"-e",
"TIGER_SECRET_KEY",
"ghcr.io/timescale/tiger-cli:0.26.0"
],
"env": {
"TIGER_PUBLIC_KEY": "<value>",
"TIGER_SECRET_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from timescale (GitHub)
| Server | Runs |
|---|---|
| Pg AiguideComprehensive PostgreSQL documentation and best practices, including ecosystem tools. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Tiger SkillsProvider agnostic skills implementation, with skills sourced from local paths or GitHub repositories. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| TidyportsSee and kill the dev servers your coding agents leave running, and get collision-free ports. | Local · stdio |
| tielineStatic FE-BE contract-drift checker: finds frontend calls the backend does not expose. CLI + MCP. | Local · stdio |
| Tier1 IT AssessmentRead-only IT Health Check, domain security, recommendations, pricing, and draft enquiries. | Remote · HTTPLive check: ✓ handshake |
| tierproxyMulti-provider proxy infrastructure for AI/ML. Geo, sessions, cost-aware routing, usage tools. | Local · stdio |
| Time ManagementRead your Pyunto Time Management schedule and log time from an AI assistant. E2EE project planning. | Local · stdio |
| TimebookTrack time on usetimebook.com - start/stop timers, log entries, list projects/clients. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Timeweaver MCPSynthetic time-series test data with trend, seasonality, noise, and anomalies, for any MCP client. | Local · stdio |