01 · Records and state owned
Databases, tables, SQL/query results, workflows, and documentation.
Treasure Data
Treasure Data CDP
Curated major addition platform in enterprise customer data platform with material relevance to the Marcom operating stack and a first-party developer surface.
Marketing automation, lifecycle & CDPSystem of engagementExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Databases, tables, SQL/query results, workflows, and documentation.
03 · Actions and write paths
Workflow and supported platform operations may be available through tenant tooling; verify command/tool scope.
04 · Authentication and permissions
Treasure Data account/API credentials Database, workflow, and account privileges govern access.
05 · Monitoring, approval, and recovery
Consequential writes should require explicit review; use vendor confirmation controls where available. Tenant-data and documentation servers are distinct; local tooling carries customer deployment responsibility.
06 · Gaps and implementation limits
Tenant-data and documentation servers are distinct; local tooling carries customer deployment responsibility.
First-party access
Documented surfaces
Treasure Data SQL query ↗Treasure Data documents SQL execution through its Trino (Presto) and Hive query engines and APIs. API keys, regional endpoints, database permissions, selected engine, query cost and priority, result size, and workflow context govern access; this is broader than its separate documentation-oriented MCP surface.Source: pyTD QuickstartMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessProduct ↗Native platform experience
Agent access
MCP and adjacent posture
Verified first-party provider MCPTreasure Data tenant-data MCP plus docs MCPCurrent documented service
Role: provider
Read scope: Databases, tables, SQL/query results, workflows, and documentation.
Write scope: Workflow and supported platform operations may be available through tenant tooling; verify command/tool scope.
Authentication: Treasure Data account/API credentials
Approval boundary: Consequential writes should require explicit review; use vendor confirmation controls where available.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation2
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Treasure Data ships these experiences.
Single-platform patterns
- Enterprise audience, segment, and activation room
- Lifecycle journey debugger
- Audience activation workbench
- Campaign QA and approval room
Multi-platform compositions
- Treasure Data CDP + CRM or commerce system: lifecycle journey debugger
- Treasure Data CDP + warehouse or CDP + content-production platform: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
4 recorded sources
MCP / agent-role validationRepresentative source
https://docs.treasuredata.com/display/public/INT/MCP+Server ↗Treasure Data provides tenant-data tooling through its CLI/ecosystem and a separate documentation-oriented server.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://api-docs.treasuredata.com/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.treasuredata.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Treasure Data SQL queryTargeted review
pyTD Quickstart ↗Treasure Data documents SQL execution through its Trino (Presto) and Hive query engines and APIs. API keys, regional endpoints, database permissions, selected engine, query cost and priority, result size, and workflow…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.