Integrate Tiger Cloud with your AI Assistant

tiger service list

Copy

tiger mcp install

Copy

Select an MCP client to configure:

> 1. Claude Code
2. Codex
3. Cursor
4. Gemini CLI
5. VS Code
6. Windsurf

Use ↑/↓ arrows or number keys to navigate, enter to select, q to quit

Copy

claude

Copy

> is the tigerdata mcp server active for you?

Copy

MCP server is active. I can see the following Tiger Data-related tools available:

- mcp__tiger__get_guide - Retrieve TimescaleDB guides and best practices
- mcp__tiger__semantic_search_postgres_docs - Search PostgreSQL documentation
- mcp__tiger__semantic_search_tiger_docs - Search Tiger Cloud and TimescaleDB documentation
- mcp__tiger__tiger_service_create - Create new database services
- mcp__tiger__tiger_service_list - List all database services
- mcp__tiger__tiger_service_show - Show detailed service information
- mcp__tiger__tiger_service_update_password - Update service passwords

Is there something specific you'd like to do with the Tiger Data MCP server?

Copy

> can you list my active services please

Copy

⏺ You have 3 active services, all with the same name "my-first-service":

1. tgrservice1 - READY - TimescaleDB - us-east-1 - 1 CPU/4GB - Created: 2025-09-30
2. tgrservice1 - READY - TimescaleDB - us-east-1 - 1 CPU/4GB - Created: 2025-09-30
3. tgrservice1 - READY - TimescaleDB - us-east-1 - 1 CPU/4GB - Created: 2025-09-30

Copy

Can you create a new ai service called bob with a replica for me please

Copy

tiger - Create Database Service (MCP)(name: "bob", addons: ["ai"], replicas: 1, wait: false)

Copy

>  I need to migrate a database with 25 million rows of data to Tiger Cloud, 
please tell me what service optimizations i should do before migration.

Copy

⏺ For migrating a database with 25 million rows to Tiger Cloud, here are the key service optimizations to do before migration:

Pre-Migration Service Optimizations

1. Right-size your compute resources:
  - For 25M rows, start with at least 2 CPU/8GB or 4 CPU/16GB
  - You can scale up during migration if needed, then scale down after

2. Enable the appropriate addons:
  - Use time-series addon if you are working with time-series data
  - Use ai addon if you need vector/AI capabilities

3. Choose optimal region:
  - Select the region closest to your current database to minimize network transfer time
  - This significantly reduces migration duration

4. Consider enhanced storage (Enterprise only):
  - If you expect high write throughput during migration, enhanced storage provides better IOPS (up to 32,000)

5. Skip replicas initially:
  - Start with 0 replicas during migration
  - Add replicas after migration completes to avoid duplicate data copying

6. Plan for storage space:
  - Estimate your uncompressed data size
  - Allocate sufficient high-performance storage (scales automatically but good to plan)
  - You can enable tiered storage later for older data

During Migration Best Practices

Migration method selection:
  - 25M rows: Use schema-then-data migration (migrate schema first, then copy data in chunks)
  - Allows restart if a copy operation fails
  - Better for databases >10GB

Database configuration to set AFTER migration:
  - Set up compression policies (once data is loaded)
  - Configure retention policies
  - Create continuous aggregates
  - Enable tiered storage for cost optimization

Connection settings:
  - Use the pooled connection endpoint for better performance during bulk inserts
  - Disable unnecessary constraints/indexes during migration, re-enable after

Would you like me to help you create an optimized service for this migration?

Copy