mcp-dataforge
Provides data profiling and quality checks for DuckDB databases.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-dataforgeprofile customers table for nulls and anomalies"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
⚒️ mcp-dataforge
Multi-agent data engineering framework — MCP-native.
Turn natural language into data pipeline actions. Six specialist agents collaborate through the Model Context Protocol (MCP) to build, validate, and monitor your data infrastructure.
Quick Start
# Install
pip install mcp-dataforge
# Initialize a project
dataforge init
# Run a task
dataforge run "profile the customers table and check for nulls"
# Start the web dashboard
dataforge web
# → http://localhost:8080Related MCP server: Alma Atlas
Architecture
MCP Client (Claude Code, Cursor, etc.)
│
│ MCP Protocol (stdio)
▼
┌─────────────────────────────────────┐
│ Orchestrator MCP Server │
│ route_task · execute_task │
│ execute_parallel · execute_mixed │
│ list_agents · get_pipeline_status │
├─────────────────────────────────────┤
│ │
│ ┌──────┐ ┌──────┐ ┌──────┐ │
│ │Pipeline│ │ DQ │ │Schema│ │
│ └──────┘ └──────┘ └──────┘ │
│ ┌──────┐ ┌──────┐ ┌──────┐ │
│ │Catalog│ │Observ│ │Orch │ │
│ └──────┘ └──────┘ └──────┘ │
│ │
│ Sequential · Parallel · Mixed │
└─────────────────────────────────────┘Execution Modes
Mode | Description | Example |
Sequential | Agents run one after another, context passes between them | Profile → Detect drift → Generate migration |
Parallel | Multiple agents run concurrently, results merged | Scan schema + check health + search catalog |
Mixed | Multi-stage: parallel groups followed by sequential steps | [DQ + Schema] in parallel → Catalog |
Built-in Agents
Agent | Tools | Description |
🔧 Pipeline |
| SQL generation, debugging, and optimization |
✅ Data Quality |
| Data profiling, anomaly detection, rule validation |
📐 Schema |
| Schema comparison, migration scripts, linting |
📚 Catalog |
| Data discovery, documentation, change impact |
🔍 Observability |
| Pipeline health, alerts, cost optimization |
⚡ Orchestration |
| DAG management, scheduling, dependency resolution |
CLI Usage
# Project setup
dataforge init # Create config.yaml
dataforge agent list # List configured agents
# Execution
dataforge run "task description" # Run a one-off task
dataforge start # Start orchestrator + agents
# Server modes
dataforge mcp-server # Run as MCP server (stdio)
dataforge mcp-server --transport sse --port 8080 # SSE mode
dataforge mcp # Print MCP config for Claude Code
# Web dashboard
dataforge web # Start web UI (http://localhost:8080)
dataforge web --port 9000 # Custom portRun Complex Pipelines
# Sequential — agents run in order, context flows between them
dataforge run "profile customers table, detect schema drift, and generate migration"
# Multi-agent — single task routed to relevant agents
dataforge run "check data quality and search catalog for PII data"Claude Code Integration
Add to your ~/.claude/settings.json:
{
"mcpServers": {
"dataforge": {
"command": "dataforge",
"args": ["mcp-server"]
}
}
}Then from Claude Code:
route_task("check null rates in orders table")
→ Returns execution plan with 1 agent (dq)
execute_task("profile customers and fix schema drift")
→ Auto-routes to DQ + Schema agents, runs sequentially, returns results
execute_parallel({"steps": [
{"agent": "catalog", "task": "search for PII data"},
{"agent": "observability", "task": "health check"}
]})
→ Both agents run concurrently, results merged
execute_custom_pipeline({"pipeline": [
{"agent": "dq", "task": "profile orders"},
{"agent": "schema", "task": "detect drift"}
]})
→ Custom sequential pipeline with context passingWeb Dashboard
Start the dashboard to monitor pipelines, agents, and execution history:
dataforge web
# Open http://localhost:8080Endpoint | Method | Description |
| GET | List all agents with capabilities |
| GET | List all tracked pipelines |
| GET | Get pipeline status |
| POST | Execute a task |
| POST | Run parallel pipeline |
| POST | Run custom sequential pipeline |
| POST | Run mixed (parallel + sequential) pipeline |
Configuration
# config.yaml
version: "1.0"
project: "my-data-platform"
agents:
pipeline:
command: "python -m d4.agents.pipeline.server"
transport: stdio
capabilities: ["sql", "spark"]
dq:
command: "python -m d4.agents.dq.server"
transport: stdio
capabilities: ["data_quality", "profiling", "validation"]
schema:
command: "python -m d4.agents.schema.server"
transport: stdio
capabilities: ["schema", "drift", "migration", "lineage"]
catalog:
command: "python -m d4.agents.catalog.server"
transport: stdio
capabilities: ["catalog", "discovery", "documentation", "tagging"]
observability:
command: "python -m d4.agents.observability.server"
transport: stdio
capabilities: ["observability", "monitoring", "alerts", "cost"]
orchestration:
command: "python -m d4.agents.orchestration.server"
transport: stdio
capabilities: ["orchestration", "dag", "scheduling", "backfill"]Deploy to Production
See the full Deployment Guide for Docker Compose, Kubernetes, and SSE mode setup.
---
```bash
# Clone and install
git clone git@github.com:Prometheus-agent/mcp-dataforge.git
cd mcp-dataforge
pip install -e ".[dev]"
# Run tests (153+ tests)
python3 -m pytest
# Run specific test file
python3 -m pytest tests/test_orchestrator.py -v
# Run the MCP server locally
dataforge mcp-server
# Run the web dashboard
dataforge webProject Structure
src/d4/
├── agents/
│ ├── pipeline/ # SQL pipeline generation
│ ├── dq/ # Data profiling & validation
│ ├── schema/ # Drift detection & migration
│ ├── catalog/ # Data discovery & docs
│ ├── observability/ # Health & cost monitoring
│ └── orchestration/ # DAG management & scheduling
├── config/ # YAML config loader
├── registry/ # Agent registry & discovery
├── orchestrator/ # Core orchestrator + MCP server
├── web/ # FastAPI web dashboard
├── cli/ # Click CLI
└── models/ # Pydantic data models
tests/ # 153+ tests across all modulesBuilding a Plugin
DataForge supports third-party agent plugins:
cp -r templates/d4-plugin d4-plugin-my-agent
cd d4-plugin-my-agent
# Rename <name> to your agent name
pip install -e .Register in config.yaml:
agents:
my_agent:
command: "python -m d4_plugin_my_agent.server"
transport: stdio
capabilities: ["my_capability"]See docs/guides/creating-a-plugin.md for full documentation.
Roadmap
Phase 1 — Core Foundation ✅
6 specialist agents with 22+ tools
Orchestrator MCP server (stdio + SSE)
CLI with init, run, agent, mcp commands
Sequential, parallel, mixed pipeline execution
FastAPI web dashboard
153+ tests, 100% passing
Phase 2 — Agent Expansion 🚧
Data Quality agent with DuckDB profiling
Schema agent with migration generation
Catalog agent with impact analysis
Phase 3 — Ecosystem 🌐
Docker deployment
Plugin API documentation
Third-party plugin support
License
Apache 2.0. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Let AI agents query data and act across all your business apps via MCP.
- DazbenchOAuthapp.dazbench
Task management your AI agents can actually run. One line becomes a context-ready task over MCP.
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Agent-first data marketplace — AI agents search, purchase, and sell datasets via MCP.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceOpen-source autonomous agent swarm of 15 MCP-native AI agents for data engineering — catalog, quality, incidents, schema evolution, governance, migration, observability, ML. 212+ tools, Apache 2.0. Works with Claude Code, Cursor, ChatGPT, and any MCP client.12-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query live schema, lineage, and query-context across data warehouses, dbt projects, orchestration systems, and BI tools via MCP tools.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables multi-model leader-worker agent orchestration, workflow execution, and deterministic validation via structured MCP tools.16Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to operate a US power-grid data pipeline – ingest, plan, run, and monitor datasets like CAISO, ERCOT, and EIA-930 through MCP tools that mirror the CLI.Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Prometheus-agent/mcp-dataforge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server