Best for
- Data teams with an OpenMetadata deployment
- AI assistants and agents that need governed data context
- Organizations performing discovery across semantics, lineage, quality, policies, and business terms
O
OpenMetadata
Official
Governed data context and business semantics for AI assistants and agents.
GitHub source repository ↗
51FMRS · D
Official OpenMetadata MCP server for AI assistants and agents that need governed data context, business semantics, lineage, quality, policy, and organizational memory from an OpenMetadata deployment. The source provides no specific tool identifiers or client support levels, so those lists remain empty.
The official OpenMetadata MCP server exposes an OpenMetadata deployment's metadata graph to MCP-compatible assistants and agents. Supported capabilities described by the source include metadata search, semantic search, entity details, lineage, data-contract and policy context, memory retrieval and preservation, metadata updates, glossary and lineage creation, data-quality tests, and root-cause analysis. This profile covers only openmetadata-mcp/server.json and does not attribute sibling repository servers to it. The server is version 1.1.0 and uses the deployment's /mcp endpoint.
Tools
The tool list has not been reviewed yet.
Setup
Replace openmetadata_host with the hostname of an OpenMetadata deployment; include a non-standard port when needed, such as metadata.example.com:8585. Connect to https://{openmetadata_host}/mcp and authenticate through the existing OpenMetadata SSO provider using OAuth 2.0 with PKCE, or use Basic Auth.
Fit and risk
Not for
- Users without an OpenMetadata deployment
- Use cases that only require direct access to a raw database or files
- Browser automation, cloud storage, or general collaboration workflows
Required permissions
- Access to the target OpenMetadata deployment's /mcp endpoint is required
- Authentication is required through OAuth 2.0 with PKCE and the existing SSO provider, or through Basic Auth
- The available metadata and data-quality operations are controlled by OpenMetadata authentication, authorization, roles, and policies
Risks and side effects
- The connection may expose permission-controlled metadata, lineage, quality, policy, and memory content from the deployment
- Accounts with write permissions may update descriptions, tags, owners, and other metadata, or create glossary terms, lineage, and quality tests
- Semantic-search results or memories may contain internal organizational knowledge and should be governed accordingly
Troubleshooting
- Verify the openmetadata_host hostname and required port
- Confirm that the deployment is reachable at /mcp
- Check OAuth 2.0 with PKCE or Basic Auth configuration against OpenMetadata SSO or account settings
- Verify that the account has the required OpenMetadata roles and policy permissions
- Confirm that the client supports streamable HTTP
Use cases
Search data assets and metadata with natural language
Retrieve entity details, lineage, ownership, quality, and governance context
Retrieve or preserve organizational memories attached to data context
Support data-quality test creation, failure analysis, and root-cause analysis
Update descriptions, tags, and owners, or create glossary terms and lineage
Supported clients
Supported clients have not been confirmed yet.