Trackio

Trackio

fcakyon

Automatically adds experiment tracking data access to Gradio applications without any code changes. Just import the package before trackio to enable querying ML experiments, runs, and metrics.

Automatically monkey-patches Gradio applications to expose trackio experiment tracking data, enabling query access to machine learning projects, runs, metrics, and statistics without requiring code changes to existing workflows.

3188 views2Local (stdio)

What it does

  • Query experiment tracking data from Gradio apps
  • Access ML project runs and metrics
  • Retrieve experiment statistics and logs
  • Monitor trackio deployments automatically
  • Enable MCP server functionality on existing workflows

Best for

ML engineers tracking experiments in GradioData scientists analyzing model performanceTeams monitoring ML workflows on Hugging Face Spaces
Zero code changes requiredWorks with Hugging Face SpacesAutomatic monkey-patching integration

About Trackio

Trackio is a community-built MCP server published by fcakyon that provides AI assistants with tools and capabilities via the Model Context Protocol. Trackio auto-exposes experiment tracking from Gradio apps—query ML projects, runs, metrics and stats without changing ex It is categorized under ai ml, analytics data.

How to install

You can install Trackio in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

License

Trackio is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

trackio-mcp

PyPI version License: MIT CI

MCP (Model Context Protocol) server support for trackio experiment tracking

This package enables AI agents to observe and interact with trackio experiments through the Model Context Protocol (MCP). Simply import trackio_mcp before trackio to automatically enable MCP server functionality.

Features

  • Zero-code integration: Just import trackio_mcp before trackio
  • Automatic MCP server: Enables MCP server on all trackio deployments (local & Spaces)
  • Rich tool set: Exposes trackio functionality as MCP tools for AI agents
  • Spaces compatible: Works seamlessly with Hugging Face Spaces deployments
  • Drop-in replacement: No changes needed to existing trackio code

Installation

pip install trackio-mcp

Or with development dependencies:

pip install trackio-mcp[dev]

Quick Start

Basic Usage

Simply import trackio_mcp before importing trackio:

import trackio_mcp  # This enables MCP server functionality
import trackio as wandb

# Your existing trackio code works unchanged
wandb.init(project="my-experiment")
wandb.log({"loss": 0.1, "accuracy": 0.95})
wandb.finish()

The MCP server will be automatically available at:

  • Local: http://localhost:7860/gradio_api/mcp/sse
  • Spaces: https://your-space.hf.space/gradio_api/mcp/sse

Deploy to Hugging Face Spaces with MCP

import trackio_mcp
import trackio as wandb

# Deploy to Spaces with MCP enabled automatically
wandb.init(
    project="my-experiment", 
    space_id="username/my-trackio-space"
)

wandb.log({"loss": 0.1})
wandb.finish()

Standalone MCP Server

Launch a dedicated MCP server for trackio tools:

from trackio_mcp.tools import launch_trackio_mcp_server

# Launch standalone MCP server on port 7861
launch_trackio_mcp_server(port=7861, share=False)

Available MCP Tools

Once connected, AI agents can use these trackio tools:

Core Tools (via Gradio API)

  • log: Log metrics to a trackio run
  • upload_db_to_space: Upload local database to a Space

Extended Tools (via trackio-mcp)

  • get_projects: List all trackio projects
  • get_runs: Get runs for a specific project
  • filter_runs: Filter runs by name pattern
  • get_run_metrics: Get metrics data for a specific run
  • get_available_metrics: Get all available metric names for a project
  • load_run_data: Load and process run data with optional smoothing
  • get_project_summary: Get comprehensive project statistics

Example Agent Interaction

Human: "Show me the latest results from my 'image-classification' project"

Agent: I'll check your trackio projects and get the latest results.

[Tool: get_projects] → finds "image-classification" project
[Tool: get_runs] → gets runs for "image-classification" 
[Tool: get_run_metrics] → gets metrics for latest run
[Tool: get_available_metrics] → gets metric names

Agent: Your latest image-classification run achieved 94.2% accuracy with a final loss of 0.18. The model trained for 50 epochs with best validation accuracy of 94.7% at epoch 45.

MCP Client Configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or equivalent:

Public Spaces:

{
  "mcpServers": {
    "trackio": {
      "url": "https://your-space.hf.space/gradio_api/mcp/sse"
    }
  }
}

Private Spaces/Datasets:

{
  "mcpServers": {
    "trackio": {
      "url": "https://your-private-space.hf.space/gradio_api/mcp/sse",
      "headers": {
        "Authorization": "Bearer YOUR_HF_TOKEN"
      }
    }
  }
}

Local Development:

{
  "mcpServers": {
    "trackio": {
      "url": "http://localhost:7860/gradio_api/mcp/sse"
    }
  }
}
Claude Code

See Claude Code MCP docs for more info.

Public Spaces:

claude mcp add --transport sse trackio https://your-space.hf.space/gradio_api/mcp/sse

Private Spaces/Datasets:

claude mcp add --transport sse --header "Authorization: Bearer YOUR_HF_TOKEN" trackio https://your-private-space.hf.space/gradio_api/mcp/sse

Local Development:

{
  "mcpServers": {
    "trackio": {
      "type": "sse",
      "url": "http://localhost:7860/gradio_api/mcp/sse"
    }
  }
}
Cursor

Add to your Cursor ~/.cursor/mcp.json file or create .cursor/mcp.json in your project folder. See Cursor MCP docs for more info.

Public Spaces:

{
  "mcpServers": {
    "trackio": {
      "url": "https://your-space.hf.space/gradio_api/mcp/sse"
    }
  }
}

Private Spaces/Datasets:

{
  "mcpServers": {
    "trackio": {
      "url": "https://your-private-space.hf.space/gradio_api/mcp/sse",
      "headers": {
        "Authorization": "Bearer YOUR_HF_TOKEN"
      }
    }
  }
}

Local Development:

{
  "mcpServers": {
    "trackio": {
      "url": "http://localhost:7860/gradio_api/mcp/sse"
    }
  }
}
Windsurf

Add to your Windsurf MCP config file. See Windsurf MCP docs for more info.

Public Spaces:

{
  "mcpServers": {
    "trackio": {
      "serverUrl": "https://your-space.hf.space/gradio_api/mcp/sse"
    }
  }
}

Private Spaces/Datasets:

{
  "mcpServers": {
    "trackio": {
      "serverUrl": "https://your-private-space.hf.space/gradio_api/mcp/sse",
      "headers": {
        "Authorization": "Bearer YOUR_HF_TOKEN"
      }
    }
  }
}

Local Development:

{
  "mcpServers": {
    "trackio": {
      "serverUrl": "http://localhost:7860/gradio_api/mcp/sse"
    }
  }
}
VS Code

Add to .vscode/mcp.json. See VS Code MCP docs for more info.

Public Spaces:

{
  "mcp": {
    "servers": {
      "trackio": {
        "type": "http",
        "url": "https://your-space.hf.space/gradio_api/mcp/sse"
      }
    }
  }
}

Private Spaces/Datasets:

{
  "mcp": {
    "servers": {
      "trackio": {
        "type": "http", 
        "url": "https://your-private-space.hf.space/gradio_api/mcp/sse",
        "headers": {
          "Authorization": "Bearer YOUR_HF_TOKEN"
        }
      }
    }
  }
}

Local Development:

{
  "mcp": {
    "servers": {
      "trackio": {
        "type": "http",
        "url": "http://localhost:7860/gradio_api/mcp/sse"
      }
    }
  }
}
Gemini CLI

Add to mcp.json in your project directory. See Gemini CLI Configuration for details.

Public Spaces:

{
  "mcpServers": {
    "trackio": {
      "command": "npx",
      "args": ["mcp-remote", "https://your-space.hf.space/gradio_api/mcp/sse"]
    }
  }
}

Private Spaces/Datasets:

{
  "mcpServers": {
    "trackio": {
      "command": "npx", 
      "args": ["mcp-remote", "https://your-private-space.hf.space/gradio_api/mcp/sse"],
      "env": {
        "HF_TOKEN": "YOUR_HF_TOKEN"
      }
    }
  }
}

Local Development:

{
  "mcpServers": {
    "trackio": {
      "command": "npx",
      "args": ["mcp-remote", "http://localhost:7860/gradio_api/mcp/sse"]
    }
  }
}
Cline

Create .cursor/mcp.json (or equivalent for your IDE):

Public Spaces:

{
  "mcpServers": {
    "trackio": {
      "url": "https://your-space.hf.space/gradio_api/mcp/sse"
    }
  }
}

Private Spaces/Datasets:

{
  "mcpServers": {
    "trackio": {
      "url": "https://your-private-space.hf.space/gradio_api/mcp/sse",
      "headers": {
        "Authorization": "Bearer YOUR_HF_TOKEN"
      }
    }
  }
}

Local Development:

{
  "mcpServers": {
    "trackio": {
      "url": "http://localhost:7860/gradio_api/mcp/sse"
    }
  }
}

Configuration

Environment Variables

  • TRACKIO_DISABLE_MCP: Set to "true" to disable MCP functionality (default: MCP enabled)

Programmatic Control

import os
os.environ["TRACKIO_DISABLE_MCP"] = "true"  # Disable MCP
import trackio_mcp  # MCP won't be enabled
import trackio

How It Works

trackio-mcp uses monkey-patching to automatically:

  1. Enable MCP server: Sets mcp_server=True on all Gradio launches
  2. Enable API: Sets show_api=True to expose Gradio API endpoints
  3. Add tools: Registers additional trackio-specific MCP tools
  4. Preserve compatibility: No changes needed to existing trackio code

The package patches:

  • gradio.Blocks.launch() - Core Gradio launch method
  • trackio.ui.demo.launch() - Trackio dashboard launches
  • Adds new MCP endpoints at /gradio_api/mcp/sse

Deployment Examples

Local Development

import trackio_mcp
import trackio

# Start local tracking with MCP enabled
trackio.show()  # Dashboard + MCP server at http://localhost:7860

Public Spaces Deployment

import trackio_mcp
import trackio as wandb

# Deploy to public Spaces with MCP support
wandb.init(
    project="public-model",
    space_id="username/model-tracking"
)

wandb.log({"epoch": 1, "loss": 

---

*README truncated. [View full README on GitHub](https://github.com/fcakyon/trackio-mcp).*

Alternatives

Related Skills

Browse all skills
data-storytelling

Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.

27
content-trend-researcher

Advanced content and topic research skill that analyzes trends across Google Analytics, Google Trends, Substack, Medium, Reddit, LinkedIn, X, blogs, podcasts, and YouTube to generate data-driven article outlines based on user intent analysis

23
data-scientist

Expert data scientist for advanced analytics, machine learning, and statistical modeling. Handles complex data analysis, predictive modeling, and business intelligence. Use PROACTIVELY for data analysis tasks, ML modeling, statistical analysis, and data-driven insights.

13
google-analytics

Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements. Use when the user asks about analytics, website metrics, traffic analysis, conversion rates, user behavior, or performance optimization.

13
senior-data-scientist

World-class data science skill for statistical modeling, experimentation, causal inference, and advanced analytics. Expertise in Python (NumPy, Pandas, Scikit-learn), R, SQL, statistical methods, A/B testing, time series, and business intelligence. Includes experiment design, feature engineering, model evaluation, and stakeholder communication. Use when designing experiments, building predictive models, performing causal analysis, or driving data-driven decisions.

8
backend-dev-guidelines

Comprehensive backend development guide for Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services), dual database system (PostgreSQL + ClickHouse), projectId filtering for multi-tenant isolation, traceException error handling, observability patterns, and testing strategies (Jest for web, vitest for worker).

7