Add the Tiger Data (Tiger Cloud) MCP server to Codex

# ~/.codex/config.toml
[mcp_servers.tiger_data]
command = "docker"
args = ["run", "-i", "--rm", "-e", "TIGER_PUBLIC_KEY", "-e", "TIGER_SECRET_KEY", "ghcr.io/timescale/tiger-cli:0.26.0"]

[mcp_servers.tiger_data.env]
TIGER_PUBLIC_KEY = "<your TIGER_PUBLIC_KEY>"
TIGER_SECRET_KEY = "<your TIGER_SECRET_KEY>"

Scopes, env vars, OAuth and limits: Codex MCP config guide

Run codex mcp login <name> to complete OAuth for a remote server. Tiger Data (Tiger Cloud) runs locally and needs TIGER_PUBLIC_KEY, TIGER_SECRET_KEY. Replace the placeholder values above with your own before starting Codex.

Ask Codex for something Tiger Data (Tiger Cloud) can do. Create, fork, resize and query Tiger Cloud Postgres services, with metrics and docs search. Approve the first tool call and check the result before allowing write actions automatically.

• · Each server is a [mcp_servers.<name>] table in config.toml.
• · Use enabled_tools or disabled_tools to keep the tool list short.

How do I add the Tiger Data (Tiger Cloud) MCP server to Codex?

Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.

Is this the official Tiger Data (Tiger Cloud) MCP server?

Yes. It is published by Tiger Data as io.github.timescale/tiger-cli in the official MCP registry.

Does the Tiger Data (Tiger Cloud) MCP server need an API key?

Yes. It runs locally and requires TIGER_PUBLIC_KEY, TIGER_SECRET_KEY.