Introduction
Marmot gives people and AI agents one governed way in to your data. It catalogs the tables, topics, dashboards and pipelines you already run, records what each one means and who owns it, and serves that context in the web UI, over the API and to agents through its MCP server.
Start here
What you can do with it
- Find the right asset
- Explain what it means
- See where data flows
- Decide who can read what
- Give agents context
- Keep it current
How it fits together
Plugins read metadata from the systems you already run into one catalog: schemas, owners, descriptions and lineage, never the rows themselves. People use it in the web UI, agents through the MCP server and your own code through the API, CLI and SDKs, so everyone works from the same answers.
Where to run it
Marmot is one Go binary backed by PostgreSQL, and the core is open source under the MIT licence. Everything in these docs applies wherever it runs: the data model, the query language, the plugins and the MCP server are the same in every edition.