Skip to content

egeria-mcp

Apache Egeria open-metadata API + MCP Server for the Arbora ecosystem — the metadata / governance / lineage system-of-record federated with the epistemic-graph Knowledge Graph.

Official documentation

This site is the canonical reference for egeria-mcp, maintained alongside every release.

PyPI MCP Server License GitHub

Overview

egeria-mcp wraps the Apache Egeria OMAG platform's View Server (OMVS) REST surface with typed, deterministic MCP tools, and is the write side of the Egeria↔Knowledge-Graph federation. It provides:

  • EgeriaApi — a tolerant raw-httpx REST facade over the View Server (no pyegeria runtime dependency; works on Python 3.11 → 3.14).
  • 21 MCP tools — granular and broad action-dispatch readers across 11 OMVS services, governed_route, and write-gated create/classify/lineage/harvest tools.
  • A 34-source bottom-up harvest that populates Egeria from the data estate.

Two hard invariants: the KG never becomes the lineage store; Egeria never orchestrates.

Explore the documentation

  • :material-rocket-start: Installation — pip, source, extras, and the prebuilt Docker image.
  • Deployment — run the MCP server, Docker Compose, Caddy + Technitium.
  • Usage — the MCP tools, the EgeriaApi client, and the harvest CLI.
  • Backing Platform — deploy Apache Egeria with Docker.
  • Architecture — pipeline, layered client, KG federation.
  • Concepts — the CONCEPT:EG-* registry.

Quick start

pip install "egeria-mcp[mcp]"
egeria-mcp                       # stdio MCP server (default transport)

Connect it to an Egeria platform:

export EGERIA_PLATFORM_URL=https://your-egeria:9443
export EGERIA_VIEW_SERVER=qs-view-server
egeria-mcp --transport http --host 0.0.0.0 --port 8000

See Installation and Deployment for the full matrix (PyPI extras, Docker image, all transports, reverse proxy, DNS).

Spec delivery

Spec delivery dashboard. No owned specs are recorded yet. Missing requirement and code mappings remain unknown.