current_database
Get the current database context being used for queries
LABSCO SUMMARY
It opens read-only and stays that way until you say otherwise — the write tool does nothing unless TD_ENABLE_UPDATES is on.
Queries run as Trino SQL with Treasure Data's own UDFs, and on a large table td_interval keeps a question from scanning years of history. The CDP and workflow tools are what make it more than a SQL client: you can read the SQL that defines an audience, and retry a failed Digdag session from a named task without leaving the conversation.
What it is
An MCP server over Treasure Data that opens read-only: catalogue browsing and SELECT queries by default, with writes behind an explicit switch.
What you get
- The catalogue through information_schema: databases, the tables in one, and a table's columns
- query for read-only SQL — SELECT, SHOW, DESCRIBE — in the Trino dialect with Treasure Data's own UDFs, and an automatic result limit so a wide table does not flood the context
- execute for writes, active only when TD_ENABLE_UPDATES is turned on
- A database context you can switch and read back, so queries stop repeating it
- Customer Data Platform tools, marked experimental: parent segments (audiences), the segments beneath one, a segment's filtering rules, the activations attached to it, and the SQL behind either a parent segment or a filtered segment
- Digdag workflow monitoring: projects, workflows, execution sessions filtered by status and time window, the attempts for a session, the tasks inside an attempt with their status, and a task's logs
- Recovery on failed runs: cancel a running attempt, retry a session from the beginning or from a named task, and retry an attempt with resume
- Audit logging across every operation
Requirements
A Treasure Data API key in TD_API_KEY, and Node.js 18 or higher. TD_SITE picks the region — us01 by default, with jp01, eu01, ap02, ap03 and dev available — and TD_DATABASE sets a default database. Writes stay off unless TD_ENABLE_UPDATES is true, which is what keeps the execute tool inert on a read-only setup. Run it over stdio with npx @treasuredata/mcp-server. The server is in public preview: free during the preview, with usage-based pricing on query volume planned afterwards.
Setup effort
One command plus a key — npx @treasuredata/mcp-server, then supply credentials
USE CASES
01
Finding the table you actually need
List the databases, then the tables in one, then the columns on the candidate.
02
Asking a question of the data
Set the database context once, then run the SELECT against it.
03
Keeping a query off a full-history scan
Bound the time range with td_interval rather than filtering after the fact.
04
Understanding how an audience is actually defined
Find the parent segment, read the SQL behind it, then open the segment's filtering rules.
05
Working out why a workflow failed
Find the session, open its attempts, list the tasks, then read the failing task's log.
06
Getting a failed run going again
Cancel what is still running, then retry the session from the task that broke.
23 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
describe_table
Get column information for a specific table
execute
Execute write operations (UPDATE, DELETE, INSERT, etc.) when enable_updates=true
get_attempt_tasks
List all tasks within an attempt with their execution status
get_parent_segment
[EXPERIMENTAL] Get details of a specific parent segment by its ID. Requires parent_segment_id parameter. Use list_parent_segments first to find available parent segment IDs.
get_segment
[EXPERIMENTAL] Get detailed information about a specific segment including its filtering rules. Requires both parent_segment_id and segment_id parameters. Use list_parent_segments and list_segments first to find available IDs.
get_session_attempts
Get detailed information about all attempts for a specific session
get_task_logs
Retrieve logs for a specific task
kill_attempt
Request cancellation of a running attempt
list_activations
[EXPERIMENTAL] List all activations (syndications) for a specific segment. Requires both parent_segment_id and segment_id parameters. Use list_parent_segments and list_segments first to find available IDs.
list_databases
List all available databases in Treasure Data
list_parent_segments
[EXPERIMENTAL] List all parent segments (audiences) in Customer Data Platform. No parameters required.
list_projects
List all workflow projects
list_segments
[EXPERIMENTAL] List all segments under a specific parent segment. Requires parent_segment_id parameter. Use list_parent_segments first to find available parent segment IDs.
list_sessions
List workflow execution sessions with filtering options
list_tables
List all tables in a specific database
list_workflows
List workflows. Optionally filter by project name.
parent_segment_sql
[EXPERIMENTAL] Get the SQL statement for a parent segment (audience). Requires parent_segment_id parameter. Use list_parent_segments first to find available parent segment IDs.
query
Execute a read-only SQL query (SELECT, SHOW, DESCRIBE) using Trino SQL dialect with Treasure Data UDFs. For better performance on large tables, use td_interval(time, '-30d/now') to limit the time range.
retry_attempt
Retry a specific failed attempt with resume capabilities
retry_session
Retry a failed session from the beginning or a specific task
segment_sql
[EXPERIMENTAL] Get the SQL statement for a segment with filtering conditions applied to the parent segment (audience) SQL. Requires both parent_segment_id and segment_id parameters. Use list_parent_segments and list_segments first to find available IDs.
use_database
Switch the current database context for subsequent queries
BEFORE YOU INSTALL
What to know first
Tools you get
23 tools when we connected. execute, the only SQL-writing tool, refuses unless TD_ENABLE_UPDATES=true (default false). The CDP and Digdag workflow tools are marked experimental, and kill_attempt, retry_session and retry_attempt work even in read-only mode.
Requires
- npx on PATH
- TD_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 23 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @treasuredata/mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"treasuredata": {
"command": "npx",
"args": [
"@treasuredata/mcp-server"
],
"env": {
"TD_API_KEY": "<YOUR_TD_API_KEY>",
"TD_SITE": "us01",
"TD_ENABLE_UPDATES": "false",
"TD_DATABASE": "sample_datasets"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add td -e TD_API_KEY=$TD_API_KEY -- npx @treasuredata/mcp-server
