Skip to main content
Glama
Treasure Data MCP Server

Treasure Data MCP Server

by knishioka

Treasure Data MCP Server

A Model Context Protocol (MCP) server that provides Treasure Data API integration for Claude Code and Claude Desktop.

DISCLAIMER: This is a personal development project and is not affiliated with, endorsed by, or related to Treasure Data Inc. in any way. This software is provided "as is" without warranty of any kind, and should be used at your own risk. The author is not responsible for any consequences resulting from the use of this software.

Reference Documentation

For comprehensive Treasure Data documentation and tools:

Related MCP server: Metabase MCP Plus

Available MCP Tools

This MCP server provides a comprehensive set of tools for interacting with Treasure Data, organized by functionality. Currently offering 23 tools across 6 categories:

Database Management

  1. td_list_databases

    td_list_databases(verbose=False, limit=30, offset=0, all_results=False)
    • Get databases in your Treasure Data account with pagination support

    • Parameters:

      • verbose: If True, return full details; if False, return only names (default)

      • limit: Maximum number of databases to retrieve (defaults to 30)

      • offset: Index to start retrieving from (defaults to 0)

      • all_results: If True, retrieves all databases ignoring limit and offset

    • Examples:

      # Get only database names (default, first 30 databases)
      td_list_databases
      
      # Get full database details
      td_list_databases verbose=True
      
      # Pagination options
      td_list_databases limit=10 offset=20
      
      # Get all databases regardless of the number
      td_list_databases all_results=True
  2. td_get_database

    td_get_database(database_name)
    • Get detailed information about a specific database

    • Parameters:

      • database_name: The name of the database to retrieve information for

    • Example:

      # Get information about a specific database
      td_get_database database_name=my_database_name
  3. td_list_tables

    td_list_tables(database_name, verbose=False, limit=30, offset=0, all_results=False)
    • Get tables in a specific Treasure Data database with pagination support

    • Parameters:

      • database_name: The name of the database to retrieve tables from

      • verbose: If True, return full details; if False, return only names (default)

      • limit: Maximum number of tables to retrieve (defaults to 30)

      • offset: Index to start retrieving from (defaults to 0)

      • all_results: If True, retrieves all tables ignoring limit and offset

    • Examples:

      # Get only table names in a database (default, first 30 tables)
      td_list_tables database_name=my_database_name
      
      # Get detailed information about tables in a database
      td_list_tables database_name=my_database_name verbose=True
      
      # Pagination options
      td_list_tables database_name=my_database_name limit=10 offset=20
      
      # Get all tables in a database
      td_list_tables database_name=my_database_name all_results=True

Workflow Project Management

  1. td_list_projects

    td_list_projects(verbose=False, limit=30, offset=0, all_results=False, include_system=False)
    • Get workflow projects in your Treasure Data account with pagination support

    • Parameters:

      • verbose: If True, return full details; if False, return only names and IDs (default)

      • limit: Maximum number of projects to retrieve (defaults to 30)

      • offset: Index to start retrieving from (defaults to 0)

      • all_results: If True, retrieves all projects ignoring limit and offset

      • include_system: If True, include system-generated projects (with "sys" metadata); defaults to False

    • Examples:

      # Get basic project info (default, first 30 projects)
      td_list_projects
      
      # Get detailed project information
      td_list_projects verbose=True
      
      # Pagination options
      td_list_projects limit=10 offset=20
      
      # Get all projects regardless of the number
      td_list_projects all_results=True
      
      # Include system-generated projects
      td_list_projects include_system=True
  2. td_get_project

    td_get_project(project_id)
    • Get detailed information about a specific workflow project

    • Note: This provides basic project metadata only. For detailed content and files, use td_download_project_archive followed by td_list_project_files and td_read_project_file

    • Parameters:

      • project_id: The ID of the workflow project to retrieve information for

    • Example:

      # Get information about a specific project
      td_get_project project_id=123456
  3. td_download_project_archive

    td_download_project_archive(project_id)
    • Download a project's archive (tar.gz) and return information about the download

    • Recommended for examining detailed project contents including SQL queries and workflow definitions

    • Parameters:

      • project_id: The ID of the workflow project to download

    • Example:

      # Download a project's archive
      td_download_project_archive project_id=123456
  4. td_list_project_files

    td_list_project_files(archive_path)
    • List all files contained in a project archive

    • Parameters:

      • archive_path: The path to the downloaded project archive (.tar.gz file)

    • Example:

      # List files in a downloaded project archive
      td_list_project_files archive_path=/tmp/td_project_123/project_123456.tar.gz
  5. td_read_project_file

    td_read_project_file(archive_path, file_path)
    • Read the contents of a specific file from a project archive

    • Parameters:

      • archive_path: The path to the downloaded project archive (.tar.gz file)

      • file_path: The path of the file within the archive to read

    • Example:

      # Read a specific file from a project archive
      td_read_project_file archive_path=/tmp/td_project_123/project_123456.tar.gz file_path=workflow.dig
  6. td_list_workflows

    td_list_workflows(verbose=False, count=100, include_system=False, status_filter=None)
    • Get workflows across all projects in your Treasure Data account

    • Parameters:

      • verbose: If True, return full details including sessions; if False, return summary (default)

      • count: Maximum number of workflows to retrieve (defaults to 100, max 12000)

      • include_system: If True, include system-generated workflows (with "sys" metadata)

      • status_filter: Filter workflows by their last session status ('success', 'error', 'running', None for all)

    • Examples:

      # Get workflow summary (default)
      td_list_workflows
      
      # Get full workflow details with recent sessions
      td_list_workflows verbose=True
      
      # Get only failed workflows
      td_list_workflows status_filter=error
      
      # Get successful workflows including system workflows
      td_list_workflows status_filter=success include_system=True
      
      # Get more workflows (up to 12000)
      td_list_workflows count=500

Search and Discovery Tools

  1. td_smart_search

td_smart_search(query, search_scope="all", search_mode="fuzzy", active_only=True, min_relevance=0.7)
  • Intelligent search across all Treasure Data resources with fuzzy matching and relevance scoring

  • Parameters:

    • query: Search term or phrase

    • search_scope: Where to search - "projects", "workflows", "tables", "all" (default: "all")

    • search_mode: Search algorithm - "exact", "fuzzy", "semantic" (default: "fuzzy")

    • active_only: Filter to only active/non-deleted resources (default: True)

    • min_relevance: Minimum relevance score (0-1) for results (default: 0.7)

  • Examples:

    # Search everywhere with fuzzy matching
    td_smart_search query="customer clustering"
    
    # Exact search for projects only
    td_smart_search query="my_project" search_scope=projects search_mode=exact
    
    # Semantic search for workflows
    td_smart_search query="recommendation engine" search_scope=workflows search_mode=semantic
    
    # Lower relevance threshold for broader results
    td_smart_search query="sales" min_relevance=0.5
  1. td_find_project

td_find_project(search_term, exact_match=False)
  • Find project by name or partial name match

  • Parameters:

    • search_term: Project name or partial name to search for

    • exact_match: If True, only return exact matches (default: False)

  • Examples:

    # Find projects containing "cluster"
    td_find_project search_term=cluster
    
    # Find exact project name
    td_find_project search_term="customer_analytics" exact_match=True
  1. td_find_workflow

td_find_workflow(search_term, project_name=None, exact_match=False, status_filter=None)
  • Find workflows by name with optional filters

  • Parameters:

    • search_term: Workflow name or partial name to search for

    • project_name: Optional project name to filter by

    • exact_match: If True, only return exact matches (default: False)

    • status_filter: Filter by status ('success', 'error', 'running', None)

  • Examples:

    # Find workflows containing "scoring"
    td_find_workflow search_term=scoring
    
    # Find workflows in specific project
    td_find_workflow search_term=daily project_name=my_project
    
    # Find failed workflows with exact name
    td_find_workflow search_term="ore_heaven_scoring" exact_match=True status_filter=error
  1. td_get_project_by_name

td_get_project_by_name(project_name)
  • Get project details by exact name match (convenient alternative to finding ID first)

  • Parameters:

    • project_name: Exact project name

  • Example:

    # Get project details by name
    td_get_project_by_name project_name="customer_analytics"

URL Analysis Tools

  1. td_analyze_url

td_analyze_url(url)
  • Extract and retrieve information from a Treasure Data console URL

  • Parameters:

    • url: Console URL to analyze

  • Supported URL formats:

    • Workflow: https://console.us01.treasuredata.com/app/workflows/12345678/info

    • Project: https://console.us01.treasuredata.com/app/projects/123456

    • Job: https://console.us01.treasuredata.com/app/jobs/123456

  • Example:

    # Analyze a workflow URL
    td_analyze_url url="https://console.us01.treasuredata.com/app/workflows/12345678/info"
  1. td_get_workflow

td_get_workflow(workflow_id)
  • Get workflow details by numeric ID (useful for console URLs)

  • Parameters:

    • workflow_id: Numeric workflow ID

  • Example:

    # Get workflow by ID
    td_get_workflow workflow_id=12345678

Project Analysis and Diagnostics (New)

  1. td_explore_project

td_explore_project(identifier, analysis_depth="detailed", focus_areas=None)
  • Analyze a TD project comprehensively for documentation or debugging

  • Parameters:

    • identifier: Project name, ID, or search term

    • analysis_depth: Level of analysis - "overview", "detailed", or "deep" (default: "detailed")

    • focus_areas: Specific aspects to analyze - ["code", "data_flow", "performance", "errors"] (default: ["code", "data_flow"])

  • Examples:

    # Get detailed project analysis
    td_explore_project identifier="my_project"
    
    # Deep analysis focusing on performance
    td_explore_project identifier="analytics_workflow" analysis_depth=deep focus_areas=["performance", "errors"]
    
    # Quick overview
    td_explore_project identifier=1664373 analysis_depth=overview
  1. td_diagnose_workflow

td_diagnose_workflow(workflow_identifier, time_window="30d", diagnostic_level="basic")
  • Diagnose workflow health and identify issues

  • Parameters:

    • workflow_identifier: Workflow name, ID, or partial match

    • time_window: Time period to analyze (e.g., "30d", "7d", "24h") (default: "30d")

    • diagnostic_level: "basic" for quick check, "comprehensive" for deep analysis (default: "basic")

  • Examples:

    # Basic health check for last 30 days
    td_diagnose_workflow workflow_identifier="ore_heaven_scoring"
    
    # Comprehensive diagnosis for last week
    td_diagnose_workflow workflow_identifier=12345678 time_window=7d diagnostic_level=comprehensive
    
    # Quick check for recent issues
    td_diagnose_workflow workflow_identifier="daily_batch" time_window=24h
  1. td_trace_data_lineage

td_trace_data_lineage(table_or_project, direction="both", max_depth=3)
  • Trace data dependencies and lineage for tables or projects

  • Parameters:

    • table_or_project: Table name (format: "database.table") or project name/ID

    • direction: "upstream" (sources), "downstream" (consumers), or "both" (default: "both")

    • max_depth: Maximum levels to trace (default: 3)

  • Examples:

    # Trace table dependencies
    td_trace_data_lineage table_or_project="production.customer_segments"
    
    # Find upstream sources only
    td_trace_data_lineage table_or_project="analytics.recommendations" direction=upstream
    
    # Trace project data flow
    td_trace_data_lineage table_or_project="my_project" max_depth=5

Workflow Execution Management Tools

  1. td_get_session

td_get_session(session_id)
  • Get detailed information about a workflow session

  • Parameters:

    • session_id: The ID of the session to retrieve

  • Examples:

    # Get session details
    td_get_session session_id=123456789
  1. td_list_sessions

td_list_sessions(workflow_id=None, count=20)
  • List recent sessions for workflows

  • Parameters:

    • workflow_id: Optional workflow ID to filter sessions

    • count: Number of recent sessions to retrieve (default 20)

  • Examples:

    # List recent sessions across all workflows
    td_list_sessions
    
    # List sessions for a specific workflow
    td_list_sessions workflow_id=12345678 count=50
  1. td_get_attempt

td_get_attempt(attempt_id)
  • Get detailed information about a workflow attempt

  • Parameters:

    • attempt_id: The ID of the attempt to retrieve

  • Examples:

    # Get attempt details
    td_get_attempt attempt_id=987654321
  1. td_get_attempt_tasks

td_get_attempt_tasks(attempt_id)
  • Get all tasks for a workflow attempt

  • Parameters:

    • attempt_id: The ID of the attempt

  • Examples:

    # Get task breakdown for an attempt
    td_get_attempt_tasks attempt_id=987654321
  1. td_analyze_execution

td_analyze_execution(url_or_id)
  • Analyze workflow execution from URL or ID

  • Parameters:

    • url_or_id: Console URL, session ID, or attempt ID

  • Examples:

    # Analyze from console URL
    td_analyze_execution url_or_id="https://console.us01.treasuredata.com/app/sessions/123456"
    
    # Analyze from session ID
    td_analyze_execution url_or_id=123456789
    
    # Analyze from attempt ID
    td_analyze_execution url_or_id=987654321

Testing

Integration Testing

To test the MCP tools with real API calls:

# Set your API key (required)
export TD_API_KEY="your-api-key"

# Run integration tests
python test_mcp_integration.py

The integration test script (test_mcp_integration.py) safely tests all tools by:

  • Using generic search terms (no production data hardcoded)

  • Showing only summary results (no sensitive data exposed)

  • Testing error handling with invalid inputs

  • Requiring explicit API key configuration

Important: Never commit files containing:

  • API keys or credentials

  • Specific project IDs or names from production

  • Detailed query results or data dumps

  • Customer or business-sensitive information

Setup Instructions

Authentication

This MCP server requires a Treasure Data API key for authentication, which should be provided via the TD_API_KEY environment variable. You can also specify the Treasure Data endpoint using the TD_ENDPOINT environment variable (defaults to api.treasuredata.com).

Setting up with Claude Code

  1. Clone the repository

    git clone https://github.com/knishioka/td-mcp-server.git
    cd td-mcp-server
  2. Install dependencies

    # Using pip
    pip install -r requirements.txt
    
    # Or using uv (recommended)
    uv pip install -e .
  3. Set up environment variables and run

    # Set your API key
    export TD_API_KEY="your-api-key"
    export TD_ENDPOINT="api.treasuredata.com"  # Optional, defaults to US region
    
    # Run the MCP server
    mcp run td_mcp_server/server.py

Setting up with Claude Desktop

Configure this MCP server for use with Claude Desktop by editing your configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "td": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/td-mcp-server",
        "run",
        "td_mcp_server/server.py"
      ],
      "env": {
        "TD_API_KEY": "YOUR_API_KEY",
        "TD_ENDPOINT": "api.treasuredata.com"
      }
    }
  }
}

Installation and Requirements

This project requires Python 3.11+ and the following dependencies:

  • requests>=2.28.0 - HTTP client for API requests

  • pydantic>=2.0.0 - Data validation and serialization

  • mcp[cli]>=1.8.1 - Model Context Protocol framework

Install the dependencies:

# Using pip
pip install -r requirements.txt

# Using uv (recommended for development)
uv pip install -e .

Running the Server Directly

You can run the MCP server directly:

# Set your API key
export TD_API_KEY="your-api-key"

# For US region (default)
export TD_ENDPOINT="api.treasuredata.com"

# For Japan region
# export TD_ENDPOINT="api.treasuredata.co.jp"

# Run with MCP CLI
mcp run td_mcp_server/server.py

Development

Running Tests

# Run all tests
pytest

# Run tests with coverage report
pytest --cov=td_mcp_server

# Run tests for a specific module
pytest tests/unit/test_api.py

Code Formatting and Linting

# Run linting with Ruff
uv run ruff check td_mcp_server tests

# Format code with Ruff
uv run ruff format td_mcp_server tests

# Run pre-commit hooks on all files
uv run pre-commit run --all-files

GitHub Actions formatting fix

Available Tools

23 tools
td_analyze_executionA

Analyze workflow execution from console URL or ID - best for debugging.

Smart analysis tool that accepts URLs from error alerts or IDs. Automatically
detects type and provides comprehensive execution analysis with recommendations.

Accepts:
- Console URLs (e.g., https://console.../app/sessions/123456)
- Session IDs (e.g., 123456789)
- Attempt IDs (e.g., 987654321)

Common scenarios:
- Someone shares a workflow URL in Slack during incident
- Quick analysis when you only have an ID from logs
- One-stop debugging for any execution issue

Returns analysis with failures, slow tasks, and actionable recommendations.

Inputs: url_or_id (required).

td_analyze_urlA

Analyze any Treasure Data console URL to get resource details.

Smart URL parser that extracts IDs and fetches information. Use when someone
shares a console link in Slack, email, or documentation.

Common scenarios:
- Someone shares workflow URL during incident investigation
- Documentation contains console links to resources
- Error message includes console URL reference
- Quick lookup from browser URL copy/paste

Supported formats:
- Workflow: https://console.../app/workflows/12345678/info
- Project: https://console.../app/projects/123456
- Job: https://console.../app/jobs/123456

Automatically detects type and returns full resource information.

Inputs: url (required).

td_diagnose_workflowA

Health check for workflows - find why they're failing or slow.

Automated troubleshooting that analyzes execution history to identify
patterns, calculate health scores, and provide fix recommendations.

Common scenarios:
- Workflow suddenly failing - Find root cause
- Performance degradation - Identify slow tasks
- Reliability issues - Pattern analysis
- Pre-deployment check - Ensure workflow health
- Incident response - Quick failure diagnosis

Time windows: "30d", "7d", "24h" for trend analysis
Levels: "basic" (quick stats), "comprehensive" (full analysis)

Returns health score (0-10), failure patterns, and prioritized fixes.

Args:
    workflow_identifier: Workflow name, ID, or partial match
    time_window: Time period to analyze (e.g., "30d", "7d", "24h")
    diagnostic_level: "basic" for quick check, "comprehensive" for deep analysis

Returns:
    Health report with score, issues, trends, and optimization recommendations

Inputs: workflow_identifier (required), time_window, diagnostic_level.

td_download_project_archiveA

Download a project's archive (tar.gz) and return information about the download.

This tool downloads the complete archive of a Treasure Data workflow project,
which contains all SQL queries, Digdag (.dig) files, Python scripts, and other
resources. The file is temporarily stored on the server.

Args:
    project_id: The ID of the workflow project to download

Inputs: project_id (required).

td_explore_projectA

Deep-dive into project to understand workflows, SQL, and architecture.

Comprehensive project analyzer that downloads and examines all files.
Essential for understanding unfamiliar projects or debugging complex issues.

Common scenarios:
- "What does this project do?" - Full project understanding
- Onboarding to new codebase - Architecture overview
- Debugging workflow failures - Code quality analysis
- Documentation generation - Structure and dependencies
- Performance optimization - Finding bottlenecks

Analysis levels:
- overview: Quick project summary and structure
- detailed: Code patterns and common issues (default)
- deep: Full analysis including all SQL/Python code

Focus areas: ["code", "data_flow", "performance", "errors"]
Returns file structure, code patterns, issues, and recommendations.

Inputs: identifier (required), analysis_depth, focus_areas.

td_find_projectA

Find project by name when you don't know the exact ID.

Searches all projects and returns matches. Useful when you know project
name but need the ID for other operations like downloading archives.

Common scenarios:
- User mentions project name, need to find ID
- Looking for projects containing specific keywords
- Getting project ID before using td_download_project_archive
- Finding multiple projects with similar names

Use exact_match=True for precise name matching, False for fuzzy search.
Returns project IDs, names, and metadata for all matches.

Inputs: search_term (required), exact_match.

td_find_workflowA

Find workflows by name to get IDs and check execution status.

Essential for locating specific workflows when you know the name.
Returns workflow IDs, project info, and latest execution status.

Common scenarios:
- User mentions workflow name, need to find details
- Looking for failing workflows with specific names
- Finding workflows within a specific project
- Getting workflow ID before detailed analysis
- Checking if a named workflow is running/failed

Filters: project_name (optional), status ('success', 'error', 'running').
Use exact_match=True for precise names, False for partial matches.

Inputs: search_term (required), project_name, exact_match, status_filter.

td_get_attemptA

Get workflow attempt details to investigate specific execution instance.

An attempt is one execution try of a scheduled session. Use when you have an
attempt ID from error logs or td_get_session and need execution details.

Common scenarios:
- Investigate why a workflow execution failed
- Check how long the execution took
- See if this was a retry after previous failure
- Get execution parameters for debugging

Returns attempt status, timing, retry info, and safe execution parameters.

Inputs: attempt_id (required).

td_get_attempt_tasksA

Get task breakdown to find which step failed or is slow in workflow.

Shows all individual tasks (steps) within a workflow execution with their
status, timing, and dependencies. Essential for debugging failed workflows.

Common scenarios:
- Find exactly which task/query failed in a complex workflow
- Identify slow-running tasks causing delays
- Understand task execution order and dependencies
- Debug data processing issues at task level

Returns task list with names, states, timing, and failure details.

Inputs: attempt_id (required).

td_get_databaseA

Get specific database details like table count, permissions, and metadata.

Shows detailed information about a named database. Use when you need to check
database properties, understand access permissions, or get table statistics.

Common scenarios:
- Verify database exists before running queries
- Check permission level (administrator, read-only, etc.)
- Get table count and creation/update timestamps
- Audit database properties for documentation

Returns creation time, table count, permissions, and protection status.

Inputs: database_name (required).

td_get_projectA

Get workflow project details by ID to check metadata and revision.

Retrieves project information including creation time, last update, and
revision hash. Use after finding project ID from td_list_projects.

Common scenarios:
- Get project metadata before downloading archive
- Check when project was last updated
- Verify project exists by ID
- Get revision for version tracking

Note: Use numeric project ID (e.g., "123456") not project name.
For project contents, use td_download_project_archive.

Inputs: project_id (required).

td_get_project_by_nameA

Get full project details using exact name instead of ID.

Convenient shortcut when you know the exact project name.
Combines find + get operations for immediate detailed results.

Common scenarios:
- User provides exact project name, need full details
- Quick project metadata lookup by name
- Avoiding two-step process (find ID then get details)
- Getting revision/timestamps for known project

Requires exact name match. For fuzzy search use td_find_project.
Returns same details as td_get_project but using name lookup.

Inputs: project_name (required).

td_get_sessionA

Get workflow session details by ID to check execution status and timing.

A session is a scheduled workflow run. Use when you have a session ID and need
to check if it ran successfully, when it was scheduled, or get attempt details.

Common scenarios:
- Verify if a scheduled workflow executed at the expected time
- Get the attempt ID to investigate execution details
- Check overall success/failure status

Returns session info with workflow name, schedule time, and latest attempt status.

Inputs: session_id (required).

td_get_workflowA

Get workflow details using numeric ID - essential for console URLs.

Direct workflow lookup when you have the ID. Handles large workflow IDs
that exceed pagination limits. Returns project info and execution history.

Common scenarios:
- Extracting ID from console URL (../workflows/12345678/info)
- Looking up workflow from error logs containing ID
- Getting project context for a known workflow ID
- Checking execution status by workflow ID

Returns workflow name, project details, schedule, and recent runs.
Includes console URL for quick browser access.

Inputs: workflow_id (required).

td_list_databasesA

List available databases to find data sources and check access.

Shows all databases you can access. Returns just names for quick overview,
or set verbose=True for details like table count and permissions.

Common scenarios:
- Discover what databases are available in your account
- Check permissions on specific databases
- Get database list for documentation or auditing

Use pagination (limit/offset) for large lists or all_results=True for everything.

Inputs: verbose, limit, offset, all_results.

td_list_project_filesA

List all files contained in a project archive.

This tool extracts and lists the content of a previously downloaded
project archive, showing all files and directories within the project.

Args:
    archive_path: The path to the downloaded project archive (.tar.gz file)

Inputs: archive_path (required).

td_list_projectsA

List workflow projects to find data pipelines and scheduled jobs.

Shows all workflow projects containing Digdag workflows, SQL queries, and
Python scripts. Returns names/IDs for navigation or verbose=True for details.

Common scenarios:
- Discover available data processing workflows
- Find specific project by browsing names
- Get project IDs for detailed exploration
- Audit workflow projects in the account
- List user projects (exclude system with include_system=False)

Projects contain .dig files defining scheduled data pipelines.

Inputs: verbose, limit, offset, all_results, +1 more.

td_list_sessionsA

List recent workflow executions to monitor status and find failures.

Shows recent scheduled runs (sessions) with their execution status. Filter by
workflow ID to see history of a specific workflow, or leave empty for all.

Common scenarios:
- Check which workflows ran recently and their status
- Find failed executions that need investigation
- Monitor execution patterns for a specific workflow
- Get session IDs for detailed analysis

Returns list with workflow names, execution times, and success/failure status.

Inputs: workflow_id, count.

td_list_tablesA

List tables in a database to explore data structure and find datasets.

Shows all tables within a specific database. Returns table names for quick
scanning, or set verbose=True for schemas, sizes, and record counts.

Common scenarios:
- Explore available data in a database
- Find specific tables by scanning names
- Check table schemas before writing queries
- Audit table sizes and record counts
- Verify table exists before querying

Supports pagination (limit/offset) or all_results=True for complete list.

Inputs: database_name (required), verbose, limit, offset, +1 more.

td_list_workflowsA

List all workflows to monitor executions and find failed jobs.

Shows workflows across all projects with their latest execution status.
Essential for monitoring data pipeline health and finding issues.

Common scenarios:
- Check which workflows are failing (status_filter="error")
- Monitor currently running workflows (status_filter="running")
- Find workflows by name (use search parameter)
- Get overview of all scheduled jobs
- Audit workflow execution patterns

Filter options: status ('success', 'error', 'running'), search by name.
Set verbose=True for execution history. Limit count to avoid token issues.

Inputs: verbose, count, include_system, status_filter, +1 more.

td_read_project_fileA

Read the contents of a specific file from a project archive.

This tool extracts and reads a specific file from a project archive,
returning its contents. This allows examining SQL queries, workflow
definitions, and other files without fully extracting the archive.

Args:
    archive_path: The path to the downloaded project archive (.tar.gz file)
    file_path: The path of the file within the archive to read

Inputs: archive_path (required), file_path (required).

td_trace_data_lineageA

Map data flow to see what feeds into or depends on tables/projects.

Critical for understanding data dependencies and impact analysis.
Traces through SQL queries to build dependency graph.

Common scenarios:
- "What happens if I change this table?" - Impact analysis
- "Where does this data come from?" - Source tracing
- Data quality issues - Track upstream problems
- Migration planning - Understand dependencies
- Documentation - Data flow diagrams

Directions:
- upstream: What tables/projects feed INTO this
- downstream: What tables/projects CONSUME this
- both: Complete dependency graph

Returns visual-ready dependency tree with table/project relationships.

Args:
    table_or_project: Table name (format: "database.table") or project name/ID
    direction: "upstream" (sources), "downstream" (consumers), or "both"
    max_depth: Maximum levels to trace (default: 3)

Returns:
    Data lineage graph with dependencies and data flow information

Inputs: table_or_project (required), direction, max_depth.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between td_analyze_execution, td_analyze_url, and td_diagnose_workflow, which all involve analyzing workflows or executions. The descriptions help differentiate them, but an agent might occasionally misselect between these three. Other tools like td_find_project and td_get_project_by_name also have overlapping functionality but are clearly distinguished by their use cases.

    Naming Consistency5/5

    All tool names follow a consistent td_verb_noun pattern, such as td_list_projects, td_get_workflow, and td_analyze_execution. The naming is uniform across all 23 tools, with no mixing of conventions like camelCase or snake_case deviations, making it easy to predict and understand tool purposes.

    Tool Count3/5

    With 23 tools, the count is borderline high for a single server, as it may feel heavy and potentially overwhelming for agents. However, given the comprehensive domain of Treasure Data workflow and data management, the number is somewhat justified to cover various aspects like analysis, exploration, and monitoring, though it could benefit from consolidation.

    Completeness5/5

    The tool set provides complete coverage for the Treasure Data domain, including CRUD-like operations (e.g., list, get, find), analysis tools (e.g., diagnose, trace), and exploration features (e.g., download, read). There are no obvious gaps; tools handle projects, workflows, databases, tables, sessions, and attempts, ensuring agents can perform end-to-end tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      F
      maintenance
      A production-ready MCP server that transforms natural language into safe, executable SQL queries with multi-database support and intelligent schema analysis.
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.
      22
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for TeamDesk databases, enabling CRUD operations, search, and document generation via natural language.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server that enables database operations, schema management, and statistics via natural language through SQL queries and resources.
      21 npm
      MIT