OpenMetadata MCP server

What the model can do

OpenMetadata data catalogue: search tables, topics, dashboards, pipelines, containers, glossary terms, tags, domains and data products, a table's columns, owners, tags and constraints, upstream and downstream lineage, data quality test cases with their latest results, open and closed data quality incidents, and glossary terms; when you ask, can acknowledge, assign, resolve, reopen or open a data quality incident, add glossary terms, and rewrite the description of a table or glossary term.

Reads

• openmetadata_searchSearch the OpenMetadata catalogue by words (Elasticsearch syntax; * for everything): tables, topics, dashboards, pipelines, ML models, containers…
• openmetadata_tableOne table from OpenMetadata by fully qualified name (service.database.schema.table): type, description, owners, tags, domains, constraints…
• openmetadata_lineageUpstream and downstream lineage of an OpenMetadata asset by type and fully qualified name, up to 3 hops each way: the assets it reads from and feeds…
• openmetadata_incidentsData quality incidents in OpenMetadata (2.0 and later), open by default: id, task number, name, status, stage (new, ack, assigned, resolved)…
• openmetadata_test_casesData quality test cases in OpenMetadata, optionally for one table: name, test definition, parameters, and the latest result (Success, Failed…
• openmetadata_glossary_termsTerms in an OpenMetadata glossary, or the children of a term, by fully qualified name: name, display name, description, synonyms and status.

Acts, when you ask

These change something in OpenMetadata. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• openmetadata_ack_incidentAcknowledges a data quality incident in OpenMetadata (moves it to stage ack).
• openmetadata_assign_incidentAssigns a data quality incident in OpenMetadata to a user or team (reassign when it is already assigned); the assignee may be notified…
• openmetadata_resolve_incidentResolves a data quality incident in OpenMetadata with a failure reason and a comment, moving it to resolved; alerts set up on incidents may fire.
• openmetadata_reopen_incidentReopens the resolved incident of an OpenMetadata test case, as acknowledged, by posting an Ack status for the test case's fully qualified name.
• openmetadata_open_incidentOpens a new data quality incident (stage new) on an OpenMetadata test case, visible in the Incident Manager.
• openmetadata_create_glossary_termAdds a term to an OpenMetadata glossary (or under a parent term), with a description and synonyms, visible to everyone who uses the glossary.
• openmetadata_update_descriptionReplaces the description of an OpenMetadata table or glossary term (Markdown), by fully qualified name…

Connect it

First connect OpenMetadata on Dashboard → Connections, then add Memtro to your client once. The OpenMetadata tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared OpenMetadata connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which data quality tests are failing right now?
• › What feeds the orders table, and what reads from it?
• › Who owns the customer dimension table?
• › What does the glossary say an active customer is?
• › Acknowledge the incident on the revenue freshness test.

Questions

Is this an official OpenMetadata MCP server?

No. It is Memtro's MCP server with Memtro's OpenMetadata connector behind it: the connector reads OpenMetadata through its API with the credentials you connect on Dashboard → Connections, and OpenMetadata publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in OpenMetadata?

Only when you ask, and only what it has been granted: acknowledge a data quality incident; assign or reassign an incident to a user or team; resolve an incident with a reason and a comment; reopen a resolved incident; open a new incident on a test case; add a glossary term to a glossary; rewrite the description of a table or glossary term. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

• Postgres MCP server
• MySQL and MariaDB MCP server
• SQL Server MCP server
• BigQuery MCP server
• Snowflake MCP server
• AWS Athena MCP server