Datris MCP Server
io.github.datris/datris
The data control plane for AI agents — acquire, validate, land, and query data over MCP.
What is the Datris MCP server?
The Datris MCP server is a data control plane that enables AI agents to acquire, validate, transform, and query data across multiple sources and destinations without holding credentials. It exposes 75 MCP tools for pipeline management, data quality, transformation, and observability, running on open-source infrastructure (MinIO, PostgreSQL, MongoDB, Kafka, Vault) that you self-host anywhere.
Datris centralizes data operations for AI agents behind a single MCP interface. Instead of agents managing 73 separate integrations, they call Datris tools to ingest files or databases, apply AI-generated validation rules and transformations, land data to PostgreSQL, MongoDB, MinIO, Kafka, vector databases, or REST endpoints, and query results with full provenance. It brokers credentials through Vault so agent code never holds keys, records every job's state and lineage, and explains failures in plain English.
How to install Datris
Copy-paste configuration for popular MCP clients.
DATRIS_API_URLrequiredURL of the Datris server API (default http://localhost:8080)
DATRIS_API_KEYsecretAPI key for the Datris server (only when USE_API_KEYS=true)
Tools & capabilities
Tools this server exposes to the agent.
Pipeline CRUD— Create, read, update, delete data pipelines with schema validation and transformation rulesFile Upload & Ingest— Upload CSV, JSON, XML, Excel, PDF, Word, or plain text; trigger preprocessing and validationAI Data Quality— Define validation rules in plain English; AI generates and executes validation scriptsAI Transformation— Specify transformations in plain English; AI generates and runs transformation codeAI Schema Generation— Upload a file and receive a complete pipeline configuration with inferred schemaAI Data Profiling— Analyze uploaded files for statistics and suggested validation rulesQuery & Search— Execute SQL queries and natural-language searches across destinations; RAG pipeline for vector searchTap Management— Create, list, and manage AI-generated data taps (e.g., fetch S&P 500 prices from yfinance)Job Monitoring— Track pipeline runs, row counts, job state, and provenance; retrieve error explanationsMulti-Destination Output— Land data in parallel to PostgreSQL, MongoDB, MinIO (Parquet/ORC), Kafka, ActiveMQ, REST, Qdrant, Weaviate, Milvus, Chroma, pgvector
Use cases
- Ingest CSV or database tables, apply AI-generated validation rules, and land clean data to PostgreSQL or MongoDB without writing code
- Upload a file and ask Datris to profile it, suggest validation rules, and generate a complete pipeline configuration
- Query your data warehouse in plain English and get SQL results with semantic search across vector databases
- Create AI-powered data taps (e.g., fetch stock prices daily from yfinance) that run on schedule and sync to your data lake
- Debug pipeline failures with AI-generated explanations in plain English, then regenerate and re-run without losing job state
Datris MCP server FAQ
Datris is a data control plane that sits beside your warehouse and lake, exposing 75 MCP tools for AI agents to acquire, validate, transform, and query data. It brokers credentials through Vault, records every job's provenance, and supports 10+ destination types (PostgreSQL, MongoDB, MinIO, Kafka, vector databases, REST, etc.).
Yes. Datris is 100% open-source under AGPL-3.0 and self-hosted on your infrastructure (MinIO, PostgreSQL, MongoDB, Kafka, Vault). No managed service or subscription required.
Run `curl -fsSL https://get.datris.ai/install.sh | sh` to start the Docker stack locally, then add the MCP server config to your client (Claude Desktop, Cursor, etc.) pointing to `http://localhost:3000/sse` via the `mcp-remote` stdio bridge. Full walkthroughs are in the docs.
Datris requires an AI provider key (Anthropic Claude, OpenAI, Azure OpenAI, AWS Bedrock, Grok, or local Ollama) for AI features. Database and API credentials for your data sources are stored in HashiCorp Vault; agents reference secrets by name and never hold keys.
Yes. The minimal install (set `TEI_ENABLED=0` and `EMBEDDING_PROVIDER=openai` in `.env`) runs in ~3.5 GB of memory and skips the 2.2 GB embedding model download. The full stack needs ~8 GB.
CSV, JSON, XML, Excel, PDF, Word (DOCX), and plain text. Files are ingested, validated, transformed, and landed to your chosen destinations.
README (reference)
Source of truth, from the repository.
Datris — The Data Control Plane for AI Agents
datris.ai · Documentation · MCP Registry · PyPI
Agents ask Datris for data. Datris finds it, acquires it, validates it, lands it in the stores you already run, and returns it with provenance — over MCP, without ever holding your keys. It sits beside your warehouse and lake; it doesn't replace them.
Why Datris?
Your agents already acquire, validate, and load data. Without a control plane, they do it badly. Datris puts that work behind one governed surface:
- One MCP door — 73 capabilities behind a single MCP server. Claude, Cursor, and any MCP-compatible agent learn one interface instead of 73 integrations
- Vault-brokered credentials — the agent references a secret by name and never holds a key; agent-written code runs in an isolated container with no keys inside
- Every run recorded — job state, row counts, and provenance for every run; every generated script versioned in git
- Durable state — pipelines and sync bookmarks live in the platform, not the chat, so regenerating a script never loses its place
- The operating loop — Acquire (AI-generated taps) → Validate (plain-English rules) → Land (multi-destination pipelines) → Observe (provenance and job state) → Explain & Repair (AI error explanation), with the same audit trail every time
- Self-host anywhere — on-prem, any cloud, or your laptop; 100% open-source infrastructure (MinIO, PostgreSQL, MongoDB, Kafka, Vault), AGPL-3.0, no managed service
Quick Start
You only need Docker. This pulls pre-built images and runtime files, seeds a
.env, and starts the stack into ./datris — no git checkout required:
curl -fsSL https://get.datris.ai/install.sh | sh
Minimal install (laptop-friendly). The default stack runs about ten
containers and the bundled embedding server downloads a 2.2 GB model on first
boot. None of that is required. Three settings in .env cut it to eight small
containers, no download, and roughly 3.5 GB of memory (4 GB of Docker memory
is enough; the full stack wants 8 GB):
TEI_ENABLED=0 # skip the local embedding server and its 2.2 GB download
EMBEDDING_PROVIDER=openai # semantic search via OpenAI (needs OPENAI_API_KEY); omit if you have no OpenAI key
POSTGRES_ENABLED=0 # optional: skip bundled Postgres; MongoDB stays as the destination
The installer sets the first two when you choose OpenAI embeddings. The datris server itself runs on a 2 GB heap by default. Details: Installation → Minimal install.
<details> <summary>Single file, no installer (works on Windows)</summary>The
install.shinstaller is a POSIX shell script (macOS/Linux). On Windows, run it from WSL2 or Git Bash, or use the single-file Compose option below, which works natively in PowerShell.
A fully self-contained Compose file — the init scripts and config are inlined, so nothing else is needed (requires Docker Compose ≥ 2.23):
# macOS / Linux
curl -O https://get.datris.ai/docker-compose.standalone.yml
ANTHROPIC_API_KEY=sk-ant-... docker compose -f docker-compose.standalone.yml up -d
# Windows (PowerShell) — use curl.exe, and set the key with $env:
curl.exe -O https://get.datris.ai/docker-compose.standalone.yml
$env:ANTHROPIC_API_KEY="sk-ant-..."
docker compose -f docker-compose.standalone.yml up -d
</details>
<details>
<summary>From a git clone</summary>
git clone https://github.com/datris/datris-platform-oss.git
cd datris-platform-oss
cp .env.example .env # Add your ANTHROPIC_API_KEY and/or OPENAI_API_KEY (or the AZURE_OPENAI_* trio, XAI_API_KEY, or AI_PROVIDER=bedrock)
docker compose up -d
</details>
UI: http://localhost:4200 · API: http://localhost:8080
Connect an AI Agent
Add to your MCP client config (Claude Desktop, Claude Code, Cursor, etc.). With the Docker stack running, the npx mcp-remote stdio bridge connects to the bundled MCP server on port 3000 — your client appears in the Datris UI Agent Monitor tab with live tool-call streaming:
{
"mcpServers": {
"datris": {
"command": "npx",
"args": ["-y", "mcp-remote", "http://localhost:3000/sse", "--transport", "sse-only"]
}
}
}
Paste-and-go for the default local setup — no API key required when USE_API_KEYS=false (the OSS default). If your instance enables auth (USE_API_KEYS=true or hosted/multi-tenant), append "--header", "x-api-key:<your-key>" to the args array. The Configuration → Connect Your Agent page generates the snippet for you and adds the header automatically when you paste your key.
Requires Node.js on your PATH (brew install node). For a stdio alternative without Docker, or full Claude Desktop / Claude Code / Cursor walkthroughs, see Configuring Claude.
CLI
brew tap datris/tap
brew install datris
datris ingest data.csv --dest postgres
datris ingest sales.csv --ai-validate "prices > 0" --ai-transform "convert dates to YYYY/MM/DD"
datris query "SELECT * FROM sales"
datris search "quarterly revenue" --store pgvector
datris tap create "Fetch S&P 500 daily prices from yfinance" --pipeline stocks
datris taps
What It Does
Source (File Upload / MinIO Event / Database Pull / Kafka)
→ Preprocessor (optional REST endpoint)
→ Data Quality (AI rules, header validation, schema validation)
→ Transformation (AI transformation, destination schema)
→ Destinations (in parallel):
PostgreSQL, MongoDB, MinIO (Parquet/ORC), Kafka, ActiveMQ,
REST Endpoint, Qdrant, Weaviate, Milvus, Chroma, pgvector
→ Notifications (ActiveMQ topic)
AI-Powered Features
| Feature | Description |
|---|---|
| MCP Server | 75 tools for AI agents — pipeline CRUD, upload, query, search, profiling, taps |
| AI Data Quality | Plain English validation rules — AI generates and runs a validation script |
| AI Transformation | Plain English transformations — AI generates and runs a transformation script |
| AI Schema Generation | Upload a file, get a complete pipeline config |
| AI Data Profiling | Upload a file, get statistics + suggested validation rules |
| AI Error Explanation | Job failures explained in plain English |
| Natural Language Query | Ask questions in English, get SQL results |
| RAG Pipeline | Chunk, embed, and search across 5 vector databases |
Supported Formats
CSV, JSON, XML, Excel, PDF, Word (DOCX), plain text
AI Providers
Anthropic Claude (Opus 4.8 default for chat and CodeGen) · OpenAI (GPT-5.5) · Azure OpenAI (bring your Azure resource; models by deployment name) · Amazon Bedrock (Claude through your AWS account — IAM auth, AWS billing, IAM-role support with zero stored keys) · Grok (xAI's models through their OpenAI-compatible API) · Ollama (local models, optional). Embeddings via OpenAI text-embedding-3-small (recommended when you have an OpenAI key), Azure OpenAI, the bundled TEI sidecar (BAAI/bge-m3 — fully local, no API key), or Ollama.
Architecture
| Service | Purpose |
|---|---|
| MinIO | S3-compatible object store for file staging and data output |
| PostgreSQL | Default structured destination, also hosts pgvector for RAG |
| MongoDB | Configuration store, job status tracking, metadata |
| ActiveMQ | File notification queue, pipeline event notifications |
| HashiCorp Vault | Secrets management (database credentials, API keys) |
| TEI | Text Embeddings Inference sidecar (BAAI/bge-m3) — local vector embeddings when you're not using OpenAI embeddings |
| Apache Kafka | Optional streaming source and destination |
| Apache Spark | Local Spark for writing Parquet/ORC to MinIO |
Documentation
Full documentation at docs.datris.ai or locally at docs/.
License
Related MCP servers

D'AUBE // BRIDGE²
Universal AI skill compiler and MCP bridge. Write once, run across agents.

RCA-MCP
Causal root-cause analysis MCP server -- 56 tools across graphs, RCA models, PyRCA.

UML Forge
Architecture intelligence, security analysis, and living docs. 14 Mermaid tools.

io.github.davegomez/fizzy
MCP server for Fizzy task management

Shared records for AI agents: engineering decisions, bug history, rules, and work state through MCP.

Hashloom
Content-addressed contracts and a verification cache that cut agent context by skipping proven code.