Treasure Data (BYOK) — connector documentation
- MCP endpoint:
https://byok-treasuredata.connectorbay.com/mcp - REST API:
POST https://byok-treasuredata.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-treasuredata.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Treasure Data Treasure Data API key (TD1 key, read from your user profile), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-treasuredata.connectorbay.com/health· Tool schemas:https://byok-treasuredata.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-treasuredata · agent@connectorbay.com
What Treasure Data (BYOK) is for
Treasure Data (BYOK) lets an AI assistant read your own Treasure Data data through the Treasure Data API with a key you supply (Treasure Data API key (TD1 key, read from your user profile)). Read-only: 9 tools (get_server_status, list_databases, list_tables, list_jobs, get_job, get_job_status, list_scheduled_queries, get_current_user, list_users). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.treasuredata.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Treasure Data. Treasure Data and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
- "Is the Treasure Data API up?"
- "Which databases do I have in Treasure Data and how many records are in each?"
- "Which tables are in the sample_datasets database and when were they last loaded?"
- "Which Treasure Data queries failed recently?"
- "How long did Treasure Data job 1120145314 run and did it succeed?"
- "Is Treasure Data job 1120145314 finished?"
What it does
get_server_status: Check that the Treasure Data API on the US site is up and that the key is accepted.list_databases: List the databases of the account with record count and creation and update times.list_tables: List the tables of one database with type, record count, estimated storage size and last import time. The schema is left out.list_jobs: List recent query jobs, newest first, with engine type, status, database, SQL text, times and record counts. Result data and result URLs are left out.get_job: Get one query job: engine type, status, database, SQL text, start and end times, CPU time and record count. The result data is not returned.get_job_status: Get only the current status (queued, running, success, error or killed) of one query job.list_scheduled_queries: List scheduled queries with name, cron expression, time zone, engine, database, SQL text and next run time. Result destinations are left out.get_current_user: Show the Treasure Data user the key belongs to: name, roles and administrator flags. Email and phone are left out.list_users: List the users of the account with name, roles and administrator flags. Emails and phone numbers are left out.
BYOK key
You bring your own Treasure Data Treasure Data API key (TD1 key, read from your user profile) (https://docs.treasure.ai/products/my-settings/getting-your-api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.treasuredata.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Data sources
- https://docs.treasure.ai/apis/td-api (the API this connector calls, with a BYOK key)
Live from the Treasure Data API (api.treasuredata.com) with a BYOK key; documentation: https://docs.treasure.ai/apis/td-api. Endpoints checked against that documentation on 2026-10-16.
What it is not
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Treasure Data. Treasure Data and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Treasure Data account.
Built for: Worldwide. Languages: English.