Skip to content
Back to search

tiger-cli

Tiger CLI is the command-line interface for Tiger Cloud. It includes an MCP server for helping coding agents write production-level Postgres code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/timescale/tiger-cli with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/timescale/tiger-cli'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/timescale--tiger-cli/badge.svg)](/listings/timescale--tiger-cli)

HTML

<a href="/listings/timescale--tiger-cli"><img src="/api/listings/timescale--tiger-cli/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

Multiple installation methods are provided. Choose your preferred method from the options below. If you aren't sure, use the first one!

Install Script (macOS/Linux/WSL)

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

Install Script (Windows)

irm https://cli.tigerdata.com/install.ps1 | iex

Homebrew (macOS/Linux)

brew install --cask timescale/tap/tiger-cli

Debian/Ubuntu

# Add repository
curl -s https://packagecloud.io/install/repositories/timescale/tiger-cli/script.deb.sh | sudo os=any dist=any bash

# Install tiger-cli
sudo apt-get install tiger-cli

For manual repository installation instructions, see [here](https://packagecloud.io/timescale/tiger-cli/install#manual-deb).

Red Hat/Fedora

# Add repository
curl -s https://packagecloud.io/install/repositories/timescale/tiger-cli/script.rpm.sh | sudo os=rpm_any dist=rpm_any bash

# Install tiger-cli
sudo yum install tiger-cli

For manual repository installation instructions, see [here](https://packagecloud.io/timescale/tiger-cli/install#manual-rpm).

Go Install

go install github.com/timescale/tiger-cli/cmd/tiger@latest

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 375 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Tiger CLI
  2. 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.
  3. ## Installation
  4. Multiple installation methods are provided. Choose your preferred method from the options below. If you aren't sure, use the first one!
  5. ### Install Script (macOS/Linux/WSL)
  6. ```bash
  7. curl -fsSL https://cli.tigerdata.com | sh
  8. ```
  9. ### Install Script (Windows)
  10. ```powershell
  11. irm https://cli.tigerdata.com/install.ps1 | iex
  12. ```
  13. ### Homebrew (macOS/Linux)
  14. ```bash
  15. brew install --cask timescale/tap/tiger-cli
  16. ```
  17. ### Debian/Ubuntu
  18. ```bash
  19. # Add repository
  20. curl -s https://packagecloud.io/install/repositories/timescale/tiger-cli/script.deb.sh | sudo os=any dist=any bash
  21. # Install tiger-cli
  22. sudo apt-get install tiger-cli
  23. ```
  24. For manual repository installation instructions, see [here](https://packagecloud.io/timescale/tiger-cli/install#manual-deb).
  25. ### Red Hat/Fedora
  26. ```bash
  27. # Add repository
  28. curl -s https://packagecloud.io/install/repositories/timescale/tiger-cli/script.rpm.sh | sudo os=rpm_any dist=rpm_any bash
  29. # Install tiger-cli
  30. sudo yum install tiger-cli
  31. ```
  32. For manual repository installation instructions, see [here](https://packagecloud.io/timescale/tiger-cli/install#manual-rpm).
  33. ### Go Install
  34. ```bash
  35. go install github.com/timescale/tiger-cli/cmd/tiger@latest
  36. ```
  37. ## Updating
  38. To upgrade an existing installation to the latest release:
  39. ```bash
  40. tiger upgrade
  41. ```
  42. This downloads the latest published binary, verifies its checksum, and replaces the currently running binary in place. If Tiger CLI was installed via a package manager (Homebrew, apt, yum/dnf), `tiger upgrade` will instead point you at the matching package-manager command.
  43. ## Quick Start
  44. After installing Tiger CLI, authenticate with your Tiger Cloud account:
  45. ```bash
  46. # Login to your Tiger account
  47. tiger auth login
  48. # View available commands
  49. tiger --help
  50. # List your database services
  51. tiger service list
  52. # Create a new database service
  53. tiger service create --name my-database
  54. # Get connection string
  55. tiger db uri
  56. # Connect to your database
  57. tiger db psql
  58. # Run a query without psql
  59. tiger db query -c "SELECT now()"
  60. # Install the MCP server
  61. tiger mcp install
  62. # Install agent skills for your coding agent
  63. tiger skills install
  64. ```
  65. ## Usage
  66. Tiger CLI provides the following commands:
  67. - `tiger auth` - Authentication management
  68. - `login` - Log in to your Tiger account (use `--headless` to authorize with a short code in a browser on any machine)
  69. - `logout` - Log out from your Tiger account
  70. - `status` - Show current authentication status and project ID (alias: `whoami`)
  71. - `tiger project` - Project management
  72. - `list` - List all projects you have access to, marking the active one (alias: `ls`)
  73. - `use` - Switch the active project (requires an OAuth login; clears the default `service_id`, since it belonged to the previous project) (alias: `switch`)
  74. - `tiger service` - Service lifecycle management (aliases: `services`, `svc`)
  75. - `list` - List all services (alias: `ls`)
  76. - `create` - Create a new service
  77. - `get` - Show detailed service information (aliases: `describe`, `show`)
  78. - `fork` - Fork an existing service
  79. - `start` - Start a stopped service (alias: `resume`)
  80. - `stop` - Stop a running service (alias: `pause`)
  81. - `rename` - Rename a service
  82. - `resize` - Resize service CPU and memory allocation
  83. - `delete` - Delete a service (alias: `rm`)
  84. - `update-password` - Update service master password
  85. - `logs` - View service logs (alias: `log`)
  86. - `metrics available` - List the metric names available for a service
  87. - `metrics details` - Show a metric's description, type, default aggregation and labels
  88. - `metrics series` - Fetch a metric's time series, with label filters, an aggregation function, group by and bucket size
  89. - `tiger db` - Database operations
  90. - `psql` - 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) (alias: `connect`)
  91. - `query` - Execute a SQL query against a database and display the results, without needing psql (alias: `sql`)
  92. - `uri` - Get connection URI for a service (alias: `connection-string`)
  93. - `ping` - Test database connectivity (aliases: `test`, `test-connection`)
  94. - `schema` - Display database schema information (tables, views, indexes, functions, TimescaleDB hypertables, and more)
  95. - `extensions list` - List the PostgreSQL extensions installed in a database, with their versions and schemas (aliases: `ext ls`)
  96. - `save-password` - Save a database password to configured password storage (keyring, pgpass, or none)
  97. - `create role` - Create a new database role, with optional read-only enforcement, inherited grants (`--from`), and statement timeout (alias: `create user`)
  98. - `tiger config` - Configuration management (alias: `cfg`)
  99. - `list` - List current configuration (aliases: `ls`, `show`)
  100. - `set` - Set configuration value
  101. - `unset` - Remove configuration value (aliases: `rm`, `delete`)
  102. - `reset` - Reset configuration to defaults (alias: `clear`)
  103. - `tiger mcp` - MCP server setup and management
  104. - `install` - Install and configure MCP server for an AI assistant (alias: `add`)
  105. - `start` - Start the MCP server
  106. - `list` - List available MCP tools, prompts, and resources (alias: `ls`)
  107. - `get` - Get detailed information about a specific MCP capability (aliases: `describe`, `show`)
  108. - `tiger skills` - Agent skills for AI coding agents
  109. - `install` - Install PostgreSQL and TimescaleDB skills for AI coding agents (alias: `add`)
  110. - `tiger feedback` - Submit feedback or a bug report to the Tiger Data team (pass the message as an argument or on stdin)
  111. - `tiger version` - Show version information
  112. - `tiger upgrade` - Upgrade the Tiger CLI to the latest version (alias: `update`)
  113. Use `tiger <command> --help` for detailed information about each command, or browse the generated [CLI reference](docs/cli/tiger.md).
  114. ### Naming a Service
  115. Anywhere a command takes a service as an argument, it takes either its ID (or a read replica set ID) or its name:
  116. ```bash
  117. tiger db psql my-api-db
  118. tiger service stop my-api-db
  119. ```
  120. Names are matched exactly. A name that matches more than one service is refused; run `tiger service list` to find the ID you want. A default service (`tiger config set service_id`, `--service-id`, or `TIGER_SERVICE_ID`) must be an ID, and destructive commands still ask you to type the ID to confirm. The MCP tools take IDs only.
  121. ## MCP Server
  122. Tiger CLI includes a Model Context Protocol (MCP) server that enables AI assistants like Claude Code to interact with your Tiger Cloud infrastructure. The MCP server provides programmatic access to database services and operations.
  123. ### Installation
  124. Configure the MCP server for your AI assistant:
  125. ```bash
  126. # Interactive installation (prompts for client selection)
  127. tiger mcp install
  128. # Or specify your client directly
  129. tiger mcp install claude-code # Claude Code
  130. tiger mcp install codex # Codex
  131. tiger mcp install copilot # GitHub Copilot CLI
  132. tiger mcp install cursor # Cursor IDE
  133. tiger mcp install devin # Devin
  134. tiger mcp install gemini # Gemini CLI
  135. tiger mcp install pi # Pi 0.99.0 or later
  136. tiger mcp install vscode # VS Code
  137. ```
  138. After installation, restart your AI assistant to activate the Tiger MCP server.
  139. #### Manual Installation
  140. If your MCP client is not supported by `tiger mcp install`, follow the client's
  141. instructions for installing MCP servers. Use `tiger mcp start` as the command to
  142. start the MCP server. For example, many clients use a JSON file like the
  143. following:
  144. ```json
  145. {
  146. "mcpServers": {
  147. "tiger": {
  148. "command": "tiger",
  149. "args": [
  150. "mcp",
  151. "start"
  152. ]
  153. }
  154. }
  155. }
  156. ```
  157. #### Streamable HTTP Protocol
  158. The above instructions install the MCP server using the stdio transport. If you
  159. need to use the Streamable HTTP transport instead, you can start the server with
  160. `tiger mcp start http --port 8080` and install it into your client using
  161. `http://localhost:8080` as the URL. Over HTTP the client may be on a different
  162. machine, so `db_query` doesn't accept a SQL file path, only inline SQL.
  163. ### Available MCP Tools
  164. The MCP server exposes the following tools to AI assistants:
  165. **Service Management:**
  166. - `service_list` - List all database services in your project
  167. - `service_get` - Get detailed information about a specific service
  168. - `service_create` - Create new database services with configurable resources
  169. - `service_fork` - Fork an existing database service to create an independent copy
  170. - `service_start` - Start a stopped database service
  171. - `service_stop` - Stop a running database service
  172. - `service_rename` - Rename a database service
  173. - `service_resize` - Resize a database service by changing CPU and memory allocation
  174. - `service_delete` - Permanently delete a database service (asks you to confirm first if the service is tagged PROD)
  175. - `service_update_password` - Set a new, randomly generated master password for a service (asks you to confirm first if the service is tagged PROD)
  176. - `service_logs` - View logs for a database service
  177. **Service Metrics:**
  178. - `service_metrics_available` - List the metric names available for a service (hardware usage, PostgreSQL settings and activity, PgBouncer pools, TimescaleDB internals)
  179. - `service_metrics_details` - Show a metric's description, type, default aggregation and labels
  180. - `service_metrics_series` - Fetch a metric's time series over a time window, with label filters, an aggregation function, group by and bucket size
  181. **Database Operations:**
  182. - `db_query` - Execute SQL queries against a database service, passed inline or as a path to a SQL file within the server's working directory, with support for parameterized queries, custom timeouts, and connection pooling
  183. - `db_schema` - Display a service's database schema (tables, views, materialized views, enums, functions, procedures, indexes, triggers, and TimescaleDB hypertable/continuous aggregate metadata) as readable text for an agent's context
  184. - `db_extensions_list` - List the PostgreSQL extensions installed in a service database, with each extension's version, schema, and description
  185. **Feedback:**
  186. - `feedback` - Submit feedback or a bug report to the Tiger Data team
  187. The MCP server automatically uses your CLI authentication and configuration, so no additional setup is required beyond `tiger auth login`.
  188. #### Proxied Tools
  189. In addition to the service management tools listed above, the Tiger MCP server also proxies tools from a remote documentation MCP server. This feature provides AI assistants with semantic search capabilities for PostgreSQL, TimescaleDB, and Tiger Cloud documentation, as well as prompts/guides for various Tiger Cloud features.
  190. The proxied documentation server ([pg-aiguide](https://github.com/timescale/pg-aiguide)) currently provides the following tools:
  191. - `view_skill` - Retrieve comprehensive guides for Postgres and TimescaleDB features and best practices
  192. - `search_docs` - Search PostgreSQL and TimescaleDB documentation using natural language queries
  193. This proxy connection is enabled by default and requires no additional configuration.
  194. To disable the documentation proxy:
  195. ```bash
  196. tiger config set docs_mcp false
  197. ```
  198. ## Agent Skills
  199. Tiger CLI can install curated PostgreSQL and TimescaleDB skills directly into
  200. your coding agents:
  201. ```bash
  202. # Interactive installation (prompts for install locations)
  203. tiger skills install
  204. # Or name the locations directly
  205. tiger skills install universal claude-code
  206. ```
  207. Skills are installed for the current user. The `universal` location,
  208. `~/.agents/skills`, is read by most coding agents (Cursor, Codex, Gemini CLI,
  209. VS Code, GitHub Copilot CLI, Devin, Pi). Claude Code, Kiro CLI, and Google
  210. Antigravity read their own skills directories, so they're separate locations
  211. (`claude-code`, `kiro-cli`, `antigravity`). Naming a client that reads
  212. `~/.agents/skills`, such as `cursor`, selects `universal`. Use `--skills-dir`
  213. to install into a directory of your choice instead.
  214. Re-run the command to update the skills to the latest version; skills that are
  215. no longer available are removed. With no arguments, the locations you've
  216. installed to before are selected in the picker to start with. Existing skills
  217. that weren't installed by Tiger CLI are never replaced unless you pass
  218. `--force`.
  219. ## Configuration
  220. The CLI stores configuration in `~/.config/tiger/config.yaml` by default, and supports hierarchical configuration through environment variables and command-line flags.
  221. ```bash
  222. # List current configuration
  223. tiger config list
  224. # Set configuration values
  225. tiger config set output json
  226. # Remove configuration value
  227. tiger config unset output
  228. # Reset to defaults
  229. tiger config reset
  230. ```
  231. ### Configuration Options
  232. All configuration options can be set via `tiger config set <key> <value>`:
  233. - `analytics` - Enable/disable analytics (default: `true`)
  234. - `color` - Enable/disable colored output (default: `true`)
  235. - `docs_mcp` - Enable/disable docs MCP proxy (default: `true`)
  236. - `mcp_max_rows` - Maximum number of rows the `db_query` MCP tool returns per result set before truncating, to limit how much data lands in an AI agent's context. Only applies to the MCP tool, not CLI commands. Default: `100`
  237. - `output` - Output format: `json`, `yaml`, or `table` (default: `table`)
  238. - `password_storage` - Password storage method: `keyring`, `pgpass`, or `none` (default: `keyring`)
  239. - `read_only` - Which services this CLI may change: `all`, `prod`, or `off` (default: `off`, which protects nothing). An interactive `tiger auth login` offers a menu of the three modes, and records your choice either way, so it only asks until you answer once. `true` and `on` are accepted as aliases for `all`, and `false` for `off`, so existing config files and `TIGER_READ_ONLY=true` behave as before.
  240. Changing a protected service is refused, and so is creating one: `tiger service create`/`fork`/`start`/`stop`/`rename`/`resize`/`update-password`/`delete` and `tiger db create role` return an error. Connection strings for it open the session in Tiger Cloud's immutable read-only mode, so the server rejects writes and DDL — that covers `tiger db psql`, `tiger db query`, `tiger db uri`, the `db_query` MCP tool, and the connection strings embedded in `tiger service` output and the equivalent MCP tools.
  241. - `all` protects every service, and the MCP write tools aren't registered at all, so they don't appear in `tools/list` and can't be called.
  242. - `prod` protects only services tagged `PROD`, leaving `DEV` services writable. `tiger service create`/`fork` and the `service_create`/`service_fork` MCP tools are gated on the environment they request, so creating a `DEV` service is allowed and a `PROD` one is not — otherwise you could create a service this same mode then refuses to delete. Forking a `PROD` service into a `DEV` fork is allowed, since that reads production without changing it. The MCP write tools stay registered — they still work on `DEV` services — and refuse per call instead. These commands read the tag off the service they resolve, so the tag costs no extra API call, and the operation is refused if that lookup fails. The MCP write tools, which take IDs, fetch the service to read its tag. A read replica is judged on its own tag, so a replica of a `PROD` primary is protected only if that replica set is itself tagged `PROD`.
  243. - `service_id` - Default service ID. Cleared automatically when the active project changes: by `tiger project`, and by `tiger auth login` unless it lands on the same project as the previous login. A service belongs to the project it was created in
  244. - `version_check` - When `true`, the CLI checks for a newer version on each invocation (in an interactive terminal) and prints a notice if one is available. Set to `false` to disable. Default: `true`.
  245. ### Environment Variables
  246. Environment variables override configuration file values. All variables use the `TIGER_` prefix:
  247. - `TIGER_ANALYTICS` - Enable/disable analytics
  248. - `TIGER_COLOR` - Enable/disable colored output
  249. - `TIGER_CONFIG_DIR` - Path to configuration directory (default: `~/.config/tiger`)
  250. - `TIGER_DOCS_MCP` - Enable/disable docs MCP proxy
  251. - `TIGER_OUTPUT` - Output format: `json`, `yaml`, or `table`
  252. - `TIGER_PASSWORD_STORAGE` - Password storage method: `keyring`, `pgpass`, or `none`
  253. - `TIGER_READ_ONLY` - Which services this CLI may change: `all`, `prod`, or `off` (same aliases as `read_only`)
  254. - `TIGER_PUBLIC_KEY` - Public key to use for authentication (takes priority over stored credentials)
  255. - `TIGER_SECRET_KEY` - Secret key to use for authentication (takes priority over stored credentials)
  256. - `TIGER_SERVICE_ID` - Default service ID (a name is refused; see [Naming a Service](#naming-a-service))
  257. - `TIGER_VERSION_CHECK` - When `true`, the CLI checks for a newer version on each invocation (in an interactive terminal) and prints a notice if one is available; `false` to disable
  258. ### Global Flags
  259. These flags are available on all commands and take precedence over both environment variables and configuration file values:
  260. - `--analytics` - Enable/disable analytics
  261. - `--color` - Enable/disable colored output
  262. - `--config-dir <path>` - Path to configuration directory (default: `~/.config/tiger`)
  263. - `--password-storage <method>` - Password storage method: `keyring`, `pgpass`, or `none`
  264. - `--service-id <id>` - Service ID (a name is refused; pass one as an argument instead)
  265. - `--version-check` - Enable/disable checking for updates on startup
  266. - `-h, --help` - Show help information
  267. ## Contributing
  268. We welcome contributions! Here's how to get started:
  269. 1. Fork the repository
  270. 2. Create a feature branch
  271. 3. Make your changes
  272. 4. Add tests for new functionality
  273. 5. Ensure all tests pass (`go test ./...`)
  274. 6. Submit a pull request
  275. For detailed development information, see [docs/development.md](docs/development.md).
  276. ## License
  277. This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.