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.
curl -fsSL https://tiger-cli-releases.s3.amazonaws.com/install/install.sh | sh
brew install --cask timescale/tap/tiger-cli
# 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.
# 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.
go install github.com/timescale/tiger-cli/cmd/tiger@latest
After installing Tiger CLI, authenticate with your Tiger Cloud account:
# Login to your Tiger account
tiger auth login
# View available commands
tiger --help
# List your database services
tiger service list
# Create a new database service
tiger service create --name my-database
# Get connection string
tiger db connection-string
# Connect to your database
tiger db connect
# Install the MCP server
tiger mcp install
Tiger CLI provides the following commands:
tiger auth
- Authentication managementlogin
- Log in to your Tiger accountlogout
- Log out from your Tiger accountwhoami
- Show current authentication status
tiger service
- Service lifecycle managementlist
- List all servicescreate
- Create a new serviceget
- Show detailed service information (aliases:describe
,show
)fork
- Fork an existing servicedelete
- Delete a serviceupdate-password
- Update service master password
tiger db
- Database operationsconnect
- Connect to a database with psqlconnection-string
- Get connection string for a servicetest-connection
- Test database connectivity
tiger config
- Configuration managementshow
- Show current configurationset
- Set configuration valueunset
- Remove configuration valuereset
- Reset configuration to defaults
tiger mcp
- MCP server setup and managementinstall
- Install and configure MCP server for an AI assistantstart
- Start the MCP server
tiger version
- Show version information
Use tiger <command> --help
for detailed information about each command.
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.
Configure the MCP server for your AI assistant:
# Interactive installation (prompts for client selection)
tiger mcp install
# Or specify your client directly
tiger mcp install claude-code # Claude Code
tiger mcp install codex # Codex
tiger mcp install cursor # Cursor IDE
tiger mcp install gemini # Gemini CLI
tiger mcp install vscode # VS Code
tiger mcp install windsurf # Windsurf
After installation, restart your AI assistant to activate the Tiger MCP server.
If your MCP client is not supported by tiger mcp install
, follow the client's
instructions for installing MCP servers. Use tiger mcp start
as the command to
start the MCP server. For example, many clients use a JSON file like the
following:
{
"mcpServers": {
"tiger": {
"command": "tiger",
"args": [
"mcp",
"start"
]
}
}
}
The above instructions install the MCP server using the stdio transport. If you
need to use the Streamable HTTP transport instead, you can start the server with
tiger mcp start http --port 8080
and install it into your client using
http://localhost:8080
as the URL.
The MCP server exposes the following tools to AI assistants:
Service Management:
service_list
- List all database services in your projectservice_get
- Get detailed information about a specific serviceservice_create
- Create new database services with configurable resourcesservice_update_password
- Update the master password for a service
Database Operations:
db_execute_query
- Execute SQL queries against a database service with support for parameterized queries, custom timeouts, and connection pooling
The MCP server automatically uses your CLI authentication and configuration, so no additional setup is required beyond tiger auth login
.
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.
The proxied documentation server (tiger-docs-mcp-server) currently provides the following tools:
get_guide
- Retrieve comprehensive guides for TimescaleDB features and best practicessemantic_search_postgres_docs
- Search PostgreSQL documentation using natural language queriessemantic_search_tiger_docs
- Search Tiger Cloud and TimescaleDB documentation using natural language queries
This proxy connection is enabled by default and requires no additional configuration.
To disable the documentation proxy:
tiger config set docs_mcp false
The CLI stores configuration in ~/.config/tiger/config.yaml
by default, and supports hierarchical configuration through environment variables and command-line flags.
# Show current configuration
tiger config show
# Set configuration values
tiger config set output json
# Remove configuration value
tiger config unset output
# Reset to defaults
tiger config reset
All configuration options can be set via tiger config set <key> <value>
:
docs_mcp
- Enable/disable docs MCP proxy (default:true
)project_id
- Default project ID (set viatiger auth login
)service_id
- Default service IDoutput
- Output format:json
,yaml
, ortable
(default:table
)analytics
- Enable/disable analytics (default:true
)password_storage
- Password storage method:keyring
,pgpass
, ornone
(default:keyring
)debug
- Enable/disable debug logging (default:false
)
Environment variables override configuration file values. All variables use the TIGER_
prefix:
TIGER_CONFIG_DIR
- Path to configuration directory (default:~/.config/tiger
)TIGER_DOCS_MCP
- Enable/disable docs MCP proxyTIGER_PROJECT_ID
- Default project IDTIGER_SERVICE_ID
- Default service IDTIGER_OUTPUT
- Output format:json
,yaml
, ortable
TIGER_ANALYTICS
- Enable/disable analyticsTIGER_PASSWORD_STORAGE
- Password storage method:keyring
,pgpass
, ornone
TIGER_DEBUG
- Enable/disable debug logging
These flags are available on all commands and take precedence over both environment variables and configuration file values:
--config-dir <path>
- Path to configuration directory (default:~/.config/tiger
)--project-id <id>
- Specify project ID--service-id <id>
- Specify service ID--analytics
- Enable/disable analytics--password-storage <method>
- Password storage method:keyring
,pgpass
, ornone
--debug
- Enable/disable debug logging-h, --help
- Show help information
We welcome contributions! Here's how to get started:
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests for new functionality
- Ensure all tests pass (
go test ./...
) - Submit a pull request
For detailed development information, see docs/development.md.
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.