Skip to content
Search ⌘K
Start a free trial

Common tasks with Tiger CLI and Tiger MCP

Manage services and work with your data in Tiger Cloud using Tiger CLI commands or Tiger MCP natural-language prompts

Tiger CLI and Tiger MCP let you work with Tiger Cloud in complementary ways. With Tiger CLI you run commands in a terminal, which is precise, scriptable, and repeatable. With Tiger MCP you ask your AI agent in plain language: it runs the same service and data operations, and it can also reason about your database using built-in skills.

There are two levels to work at: managing your services, which has no SQL, and working with your data, which is all SQL. The examples below show the CLI way, and the equivalent Tiger MCP prompt. New to these tools? See Tiger CLI and Tiger MCP.

Prerequisites for this page

To follow these steps, you'll need:

Commands and tools can change between releases, so run tiger --help for the current CLI, and see the Tiger CLI reference and Tiger MCP reference. For agent safety, see best practices.

Manage your services

Section titled “Manage your services”

Every service task is a tiger service command in the CLI, and the Tiger MCP has a matching tool, so you can instead just describe what you want. See the Tiger CLI reference for each command's full flags and sample output, the Tiger MCP reference for each tool's parameters and return value, and the Tiger CLI and Tiger MCP overview for the full command-to-tool mapping.

How do I create a service?

Section titled “How do I create a service?”
Terminal window
tiger service create --name analytics --region us-east-1

Or ask your agent: "Create a time-series service called analytics in us-east-1." (calls service_create).

How do I test a change without risking production data?

Section titled “How do I test a change without risking production data?”
Terminal window
tiger service fork <service-id> --now

Or ask your agent: "Fork service abc123 so I can test a schema change." (calls service_fork). See Test a change safely on a fork for a full workflow.

How do I resize a service?

Section titled “How do I resize a service?”
Terminal window
tiger service resize <service-id> --cpu 4000 --memory 16

Or ask your agent: "Resize service abc123 to 4 CPU and 16 GB." (calls service_resize).

How do I start or stop a service?

Section titled “How do I start or stop a service?”
Terminal window
tiger service start <service-id>
tiger service stop <service-id>

Or ask your agent: "Stop service abc123." (calls service_start or service_stop).

How do I rotate the database password?

Section titled “How do I rotate the database password?”
Terminal window
tiger service update-password <service-id> --auto-generate

Or ask your agent: "Reset the password on service abc123." (calls service_update_password).

How do I list, inspect, and check logs for a service?

Section titled “How do I list, inspect, and check logs for a service?”
Terminal window
tiger service list
tiger service get <service-id>
tiger service logs <service-id> --tail 100

Or ask your agent: "List my services and show recent logs for abc123." (calls service_list, service_get, service_logs).

How do I delete a service?

Section titled “How do I delete a service?”
Terminal window
tiger service delete <service-id> --confirm

There is no Tiger MCP tool for delete; run this CLI command yourself.

Work with your data

Section titled “Work with your data”

Everything inside the database is SQL. With Tiger CLI, open a session and run it (add --read-only for a session that blocks writes):

Terminal window
tiger db connect <service-id>

With Tiger MCP, you skip the connection and describe the task, and the agent runs the SQL against the service you name.

For example, to create a hypertable:

CREATE TABLE metrics (
  time   timestamptz NOT NULL,
  device text,
  value  double precision
) WITH (tsdb.hypertable, tsdb.partition_column = 'time');

Or ask "Create a hypertable called metrics partitioned by time, with device and value columns."

The same pattern covers the rest of your everyday data work. Run the SQL yourself, or describe it to your agent:

  • Query your data, for example "What is the hourly average value in metrics over the last day?"
  • Load data from a file with \COPY, or ask your agent to add small amounts, for example "Insert a few sample rows into metrics for testing."
  • Roll up a continuous aggregate, for example "Create a continuous aggregate on metrics for hourly averages per device."
  • Add compression and retention, for example "Convert metrics chunks older than 7 days to the columnstore and drop data older than 30 days."

Analyze, design, and optimize with Tiger MCP

Section titled “Analyze, design, and optimize with Tiger MCP”

Some data work goes beyond running SQL. Using its built-in skills, Tiger MCP can reason about your database, which the CLI cannot do. Design and analysis are read and advice oriented, so they work in read-only mode:

  • Design a schema: "Design a Tiger Cloud schema for storing IoT device telemetry."
  • Find hypertable candidates: "Analyze my database and tell me which tables should be hypertables."
  • Review and optimize: "Review my schema and indexes against best practices and suggest improvements."

Planning a change is also read-only, but testing it needs write access: forking a service (service_fork) is itself one of the tools read-only mode disables.

  • Plan a schema change: "Plan a zero-downtime migration to add a status column to metrics, and test it on a fork first."

Next steps

Section titled “Next steps”