Open-source data catalog. Search assets, explore lineage, and find ownership.
MCP Server: io.github.marmotdata/marmot
This MCP server exposes an open-source data catalog. It helps users search assets, explore data lineage, and find ownership. The project is positioned as a “context layer” that catalogs metadata (including tables, topics, queues, and APIs) and makes that metadata available for AI agents.
🛠️ Key Features
Open-source data catalog
Data discovery and asset search
Data lineage exploration
Ownership lookup
Metadata exposure for AI agents
🚀 Use Cases
Finding relevant data assets quickly
Investigating relationships via data lineage
Verifying who owns a specific asset
Supplying catalog metadata to AI-driven workflows
⚡ Developer Benefits
Standard metadata for AI agents from cataloged tables, topics, queues, and APIs
Supports MCP integration patterns (listed topics include “mcp” and “mcp-server”)
⚠️ Limitations
No additional MCP tool capabilities are described in the provided data beyond metadata/catalog access
Marmot knows what your data means, governs who may use it and runs every query through it, for people and agents alike. It catalogs your tables, topics, dashboards and pipelines with 70+ plugins, records their lineage, owners and definitions,
and lets people and agents query the data through it, with every query checked and audited.
Use it from the web UI, the CLI, the SDKs or its built-in MCP server. It runs as one Go binary backed by PostgreSQL.
A tour of Marmot: Discover narrowed to finance tables, the orders_daily asset page with its owners and glossary terms, a governed query that returns rows and a refused one in the query audit, then the lineage of orders_daily from source to dashboard
What you can do with it
Marmot catalogs the tables, topics, dashboards and pipelines you already run, records what each one means and who owns it, and serves that context to everyone from one place:
Search every source in plain words, then narrow the results with the query language.
Trace lineage upstream and downstream, from plugins and OpenLineage runs, before you change something. See lineage.
Explain what data means with owners, descriptions, a glossary and data products that travel with every asset.
Give agents the same context through the MCP server, the CLI and SDKs for Go, Python and TypeScript.
Run SQL through Marmot against the sources you connect. Each query is checked against the caller's roles and recorded in the query audit, so an agent never needs a database password of its own.
Keep it current with 70+ plugins for systems such as PostgreSQL, BigQuery, Kafka, dbt and Airflow, or declare assets yourself with Terraform and the API.
Try it locally
You need Docker with Docker Compose, and port 8080 free. Save this as docker-compose.yaml. It's for trying Marmot out, so it stores credentials unencrypted:
Open http://localhost:8080 and sign in as admin with the password admin. Marmot asks you to choose a new password, then you can open Plugins and pick a system under Add a source to catalog it. The quick start walks through the first pipeline.
To skip running it yourself, Marmot Cloud launches a managed instance. The free plan needs no card.
Connect an agent
Create an API key under Account → API keys, then add Marmot to your client's MCP configuration. For Claude Code, that's .mcp.json in your project's root:
The core is open source under the MIT licence and runs anywhere you can run a container or a binary. Self-host covers Docker Compose, Docker, Helm and the binary, with an encryption key for stored credentials. Marmot Cloud runs it for you and adds access control per resource, secret stores and keyless pipelines. The data model, query language, plugins and MCP server are the same in both.
Get help
Discord for questions and talking to the team and other people running Marmot.