Skip to main content
hc
Submit
mcpSource-backed
OpenMetadata logo

OpenMetadata MCP Server

OpenMetadata MCP OAuth server that lets Claude-compatible clients access OpenMetadata metadata tools through user SSO or Basic Auth, PKCE, dynamic client registration, and OpenMetadata's normal permission model.

by OpenMetadata · submitted by oktofeesh1·added 2026-06-06·
Claude CodeClaude Desktop
HarnessClaude CodeClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/mcp/openmetadata-mcp-server
Source URLs
https://raw.githubusercontent.com/open-metadata/OpenMetadata/main/openmetadata-mcp/README.md, https://github.com/open-metadata/OpenMetadata
Brand
OpenMetadata
Brand domain
open-metadata.org
Brand asset source
brandfetch
Safety notes
OpenMetadata MCP tools execute with the authenticated user's OpenMetadata permissions, not with a generic connector identity., OAuth support includes Authorization Code Flow with PKCE, dynamic client registration, refresh-token rotation, encrypted token storage, rate limiting, CORS configuration, and audit logging., Tools can search metadata, inspect entities, use semantic search, patch entities, create glossary resources, and edit lineage depending on the deployed tool set and user permissions., Metadata mutations can change catalog governance, lineage, ownership, descriptions, tags, glossary definitions, and downstream trust signals., Require approval before entity patching, glossary changes, lineage edits, or any action that changes catalog state used by analysts, data products, or compliance workflows.
Privacy notes
OpenMetadata catalog content can reveal table names, columns, schemas, dashboards, pipelines, services, owners, tags, classifications, glossary terms, lineage, usage patterns, data-quality context, and internal business semantics., OAuth access tokens, refresh tokens, authorization codes, client IDs, redirect URIs, CORS origins, SSO identities, audit logs, and MCP transcripts can contain sensitive security or user information., Search and semantic-search results can surface restricted metadata if roles, policies, ownership, or impersonation settings are misconfigured., Redact tokens, user identifiers, internal hostnames, private service names, lineage diagrams, and regulated metadata before sharing prompts, logs, screenshots, or generated notes.
Author
OpenMetadata
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

45 minutes

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

5 to clear

Platforms

2 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/5 ready
Account & credentials4Review & approval145 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.

4 areas
  • SafetyPermissions & scopesOpenMetadata MCP tools execute with the authenticated user's OpenMetadata permissions, not with a generic connector identity.
  • SafetyCredentials & tokensOAuth support includes Authorization Code Flow with PKCE, dynamic client registration, refresh-token rotation, encrypted token storage, rate limiting, CORS configuration, and audit logging.
  • SafetyPermissions & scopesTools can search metadata, inspect entities, use semantic search, patch entities, create glossary resources, and edit lineage depending on the deployed tool set and user permissions.
  • SafetyExecution & processesMetadata mutations can change catalog governance, lineage, ownership, descriptions, tags, glossary definitions, and downstream trust signals.
  • SafetyData retentionRequire approval before entity patching, glossary changes, lineage edits, or any action that changes catalog state used by analysts, data products, or compliance workflows.
  • PrivacyData retentionOpenMetadata catalog content can reveal table names, columns, schemas, dashboards, pipelines, services, owners, tags, classifications, glossary terms, lineage, usage patterns, data-quality context, and internal business semantics.
  • PrivacyCredentials & tokensOAuth access tokens, refresh tokens, authorization codes, client IDs, redirect URIs, CORS origins, SSO identities, audit logs, and MCP transcripts can contain sensitive security or user information.
  • PrivacyPermissions & scopesSearch and semantic-search results can surface restricted metadata if roles, policies, ownership, or impersonation settings are misconfigured.
  • PrivacyCredentials & tokensRedact tokens, user identifiers, internal hostnames, private service names, lineage diagrams, and regulated metadata before sharing prompts, logs, screenshots, or generated notes.

Disclosure: Apache-2.0 OpenMetadata project module for OAuth-backed MCP access to the metadata catalog. It should be enabled only where OpenMetadata user permissions, audit logging, and governance workflows are ready for AI-assisted metadata access and mutation.

Safety notes

  • OpenMetadata MCP tools execute with the authenticated user's OpenMetadata permissions, not with a generic connector identity.
  • OAuth support includes Authorization Code Flow with PKCE, dynamic client registration, refresh-token rotation, encrypted token storage, rate limiting, CORS configuration, and audit logging.
  • Tools can search metadata, inspect entities, use semantic search, patch entities, create glossary resources, and edit lineage depending on the deployed tool set and user permissions.
  • Metadata mutations can change catalog governance, lineage, ownership, descriptions, tags, glossary definitions, and downstream trust signals.
  • Require approval before entity patching, glossary changes, lineage edits, or any action that changes catalog state used by analysts, data products, or compliance workflows.

Privacy notes

  • OpenMetadata catalog content can reveal table names, columns, schemas, dashboards, pipelines, services, owners, tags, classifications, glossary terms, lineage, usage patterns, data-quality context, and internal business semantics.
  • OAuth access tokens, refresh tokens, authorization codes, client IDs, redirect URIs, CORS origins, SSO identities, audit logs, and MCP transcripts can contain sensitive security or user information.
  • Search and semantic-search results can surface restricted metadata if roles, policies, ownership, or impersonation settings are misconfigured.
  • Redact tokens, user identifiers, internal hostnames, private service names, lineage diagrams, and regulated metadata before sharing prompts, logs, screenshots, or generated notes.

Prerequisites

  • Running OpenMetadata deployment with the MCP module and OAuth settings available.
  • OpenMetadata user account authenticated through SSO or Basic Auth.
  • MCP client support for OAuth discovery, dynamic client registration, and bearer-token authenticated requests.
  • Reviewed `baseUrl`, `allowedOrigins`, token lifetime, CORS, SSO provider, and cluster configuration for the OpenMetadata MCP deployment.
  • Catalog-governance policy for AI-assisted search, entity patching, glossary changes, lineage edits, and audit logging.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
45 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
Apache-2.0 OpenMetadata project module for OAuth-backed MCP access to the metadata catalog. It should be enabled only where OpenMetadata user permissions, audit logging, and governance workflows are ready for AI-assisted metadata access and mutation.
Full copyable content
{
  "mcpServers": {
    "openmetadata": {
      "url": "https://<openmetadata-host>/mcp"
    }
  }
}

About this resource

Content

OpenMetadata MCP Server is OpenMetadata's OAuth-backed MCP integration for Claude Desktop and other MCP clients. It uses OpenMetadata user authentication through SSO or Basic Auth, then runs MCP tools under the authenticated user's normal OpenMetadata permissions.

Use it when Claude needs governed access to metadata search, semantic search, entity lookup, catalog updates, glossary workflows, or lineage edits inside an OpenMetadata deployment that already has roles, policies, SSO, and audit logging configured.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, MCP OAuth README, license, OAuth transport provider, search tools, entity tools, glossary tool, and lineage tool for current setup and behavior details.

Features

  • Authenticate MCP clients with OAuth Authorization Code Flow with PKCE.
  • Support SSO providers such as Google, Okta, Azure AD, Auth0, AWS Cognito, Custom OIDC, LDAP, and SAML through OpenMetadata's existing authentication.
  • Support Basic Auth with OpenMetadata credentials where that mode is configured.
  • Use dynamic client registration and OAuth discovery endpoints.
  • Rotate refresh tokens and encrypt token storage.
  • Apply OpenMetadata authorizer checks using the authenticated user's identity.
  • Search metadata and run semantic search.
  • Inspect entities, patch catalog metadata, create glossary resources, and add lineage edges when the user has permission.

Installation

Enable and configure OpenMetadata's MCP settings with a production baseUrl, explicit allowedOrigins, and reviewed SSO settings. Then connect an OAuth- capable MCP client to the deployment's MCP endpoint:

{
  "mcpServers": {
    "openmetadata": {
      "url": "https://<openmetadata-host>/mcp"
    }
  }
}

Use the endpoint and OAuth discovery details from the approved OpenMetadata deployment. Keep OAuth client details, access tokens, refresh tokens, and SSO configuration out of prompts, issue comments, and repository files.

Use Cases

  • Search catalog metadata before answering questions about trusted datasets.
  • Inspect ownership, descriptions, tags, classifications, and lineage for a table, dashboard, pipeline, or service.
  • Use semantic search to find related data products or glossary terms.
  • Draft and review catalog metadata patches before applying them.
  • Create glossary resources through an approved governance workflow.
  • Add or review lineage edges with the same permissions used in OpenMetadata.
  • Help data stewards investigate root-cause or discovery questions without bypassing OpenMetadata roles and policies.

Safety and Privacy

OpenMetadata MCP Server can expose and mutate catalog metadata. Keep it tied to named user authentication, tested authorization policies, explicit CORS origins, short-lived tokens, and audit logging. Require human approval before any patch, glossary, lineage, or governance update.

Treat metadata as sensitive. Dataset names, columns, owners, tags, classifications, lineage, service names, data-quality context, and glossary terms can reveal regulated systems, customer domains, business strategy, or security architecture even when raw data is not returned.

Duplicate Check

No open-metadata/OpenMetadata, OpenMetadata MCP, OpenMetadata MCP Server, openmetadata-mcp, or matching source URL entry was found in content/mcp or README.md. Existing database, catalog, and governance entries do not cover OpenMetadata's OAuth-backed MCP server.

#data-catalog#metadata#oauth#governance#lineage

Source citations

Add this badge to your README

Show that OpenMetadata MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/openmetadata-mcp-server.svg)](https://heyclau.de/entry/mcp/openmetadata-mcp-server)

How it compares

OpenMetadata MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field
OpenMetadata logoOpenMetadata MCP Server

OpenMetadata MCP OAuth server that lets Claude-compatible clients access OpenMetadata metadata tools through user SSO or Basic Auth, PKCE, dynamic client registration, and OpenMetadata's normal permission model.

Open dossier
DataHub MCP Server for Claude

Connect Claude to DataHub — search assets, trace data lineage, explore schemas, retrieve real query history, and enrich metadata — with the official DataHub MCP server from Acryl Data, supporting the full DataHub data catalog platform.

Open dossier
Data API Builder logoData API Builder MCP Tools

MCP support in Azure Data API Builder for exposing configured database entities as MCP tools, including entity discovery and DML operations over Azure databases and supported on-premises data stores.

Open dossier
data.gouv.fr logodata.gouv.fr MCP Server

Official data.gouv.fr MCP server for searching French national open datasets, exploring organizations and data services, inspecting resources, querying tabular data, and retrieving dataset metrics through Claude.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1—oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandOpenMetadata logoOpenMetadata—Data API Builder logoData API Builderdata.gouv.fr logodata.gouv.fr
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorOpenMetadataAcryl DataAzuredata.gouv.fr
Added2026-06-062026-06-182026-06-062026-06-06
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Harness
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓OpenMetadata MCP tools execute with the authenticated user's OpenMetadata permissions, not with a generic connector identity. OAuth support includes Authorization Code Flow with PKCE, dynamic client registration, refresh-token rotation, encrypted token storage, rate limiting, CORS configuration, and audit logging. Tools can search metadata, inspect entities, use semantic search, patch entities, create glossary resources, and edit lineage depending on the deployed tool set and user permissions. Metadata mutations can change catalog governance, lineage, ownership, descriptions, tags, glossary definitions, and downstream trust signals. Require approval before entity patching, glossary changes, lineage edits, or any action that changes catalog state used by analysts, data products, or compliance workflows.✓Metadata mutation tools (add/remove tags, terms, owners) are disabled by default — set `TOOLS_IS_MUTATION_ENABLED=true` to enable write operations. Mutations affect production data catalog metadata; confirm before enabling in shared environments.✓Data API Builder MCP tools can expose database entity metadata and perform DML operations depending on DAB configuration and permissions. Built-in tools include entity discovery and record read, create, update, delete, aggregate, and execute-style workflows in the MCP source tree. The upstream README still labels endpoint support as coming soon while source, samples, and testing docs expose MCP behavior; verify the exact release before production use. Use least-privilege roles, disable DML tools where not required, and require approval before write, delete, execute, or stored-procedure operations. Do not connect MCP clients to production databases without backups, audit logging, query limits, and rollback procedures.✓The hosted endpoint is documented as publicly available without access restrictions, so treat requests and returned public-data context as externally visible. Tools are read-only but can retrieve dataset metadata, resource URLs, rows from tabular resources, service OpenAPI specs, metrics, and organization details that may influence decisions. Public open data can be stale, incomplete, licensed with reuse conditions, or unsuitable for operational decisions without checking the dataset publisher and update cadence. Tabular queries can return rows from large resources; use small page sizes and pagination instead of asking an agent to pull entire datasets through chat. If self-hosting, review MCP_HOST, allowed hosts, allowed origins, Sentry, Matomo, and API-environment settings before exposing the server.
Privacy notes✓OpenMetadata catalog content can reveal table names, columns, schemas, dashboards, pipelines, services, owners, tags, classifications, glossary terms, lineage, usage patterns, data-quality context, and internal business semantics. OAuth access tokens, refresh tokens, authorization codes, client IDs, redirect URIs, CORS origins, SSO identities, audit logs, and MCP transcripts can contain sensitive security or user information. Search and semantic-search results can surface restricted metadata if roles, policies, ownership, or impersonation settings are misconfigured. Redact tokens, user identifiers, internal hostnames, private service names, lineage diagrams, and regulated metadata before sharing prompts, logs, screenshots, or generated notes.✓Dataset schemas, table previews, lineage graphs, real SQL query history, and data owner information from your DataHub instance are surfaced in Claude's context. Your `DATAHUB_GMS_TOKEN` grants catalog access — treat it as a secret.✓Entity metadata can expose database names, table names, view names, stored procedure names, field names, key fields, relationships, permissions, and role design. Read and DML tool calls can expose or change customer records, internal data, regulated fields, identifiers, audit fields, and business workflow state. Connection strings, role headers, MCP URLs, logs, request bodies, result payloads, and MCP transcripts can contain sensitive operational or personal data. Redact database values, connection details, entity names, role names, and query results before sharing prompts, screenshots, logs, or generated notes.✓Search terms, dataset interests, resource IDs, user-agent headers, request URLs, tool names, and returned dataset rows may be visible to the hosted MCP service, MCP client, model provider, and logs. The server includes optional Matomo and Sentry instrumentation in source; hosted deployments may apply their own analytics and error-reporting policies. Public datasets can still contain personal data, geographic sensitivity, business identifiers, or regulated information; review source metadata and reuse terms before sharing results. Avoid placing private investigation notes, customer context, or unpublished analysis inside prompts when a generic dataset search is enough.
Prerequisites
  • Running OpenMetadata deployment with the MCP module and OAuth settings available.
  • OpenMetadata user account authenticated through SSO or Basic Auth.
  • MCP client support for OAuth discovery, dynamic client registration, and bearer-token authenticated requests.
  • Reviewed `baseUrl`, `allowedOrigins`, token lifetime, CORS, SSO provider, and cluster configuration for the OpenMetadata MCP deployment.
  • A running DataHub instance (self-hosted or DataHub Cloud) with GMS endpoint accessible.
  • A DataHub personal access token: Settings → Access Tokens → + Generate Access Token.
  • Python with `uv` or `uvx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • Reviewed Azure Data API Builder configuration with the MCP runtime section enabled.
  • Supported Azure or on-premises database connection configured through DAB.
  • DAB entity permissions, role headers, DML tool flags, and per-entity MCP settings reviewed before exposing tools.
  • MCP client support for the transport used by the deployed DAB server.
  • MCP client that supports Streamable HTTP or a remote MCP bridge such as mcp-remote.
  • Agreement on whether hosted data.gouv.fr MCP requests may be sent to the public hosted endpoint.
  • Public-data review process for datasets that may contain personal, sensitive, stale, or jurisdiction-specific information.
  • Python 3.13 or newer only if self-hosting the repository instead of using the hosted endpoint.
Install
Enable OpenMetadata MCP configuration, then connect an OAuth-capable MCP client to the OpenMetadata MCP endpoint.
claude mcp add datahub -e DATAHUB_GMS_URL=https://your-datahub.example.com/api/gms -e DATAHUB_GMS_TOKEN=<your-token> -- uvx mcp-server-datahub
Enable the DAB runtime MCP section, start Data API Builder with the reviewed configuration, and connect an MCP client to the configured MCP path.
claude mcp add --transport http datagouv https://mcp.data.gouv.fr/mcp
Config
Manual-only setup:
Configure OpenMetadata MCP settings with a production baseUrl, explicit allowedOrigins, and enabled=true before connecting clients.
{
  "mcpServers": {
    "datahub": {
      "command": "uvx",
      "args": ["mcp-server-datahub"],
      "env": {
        "DATAHUB_GMS_URL": "https://your-datahub.example.com/api/gms",
        "DATAHUB_GMS_TOKEN": "<your-token>",
        "TOOLS_IS_MUTATION_ENABLED": "false",
        "SEMANTIC_SEARCH_ENABLED": "false"
      }
    }
  }
}
Manual-only setup:
"mcp": {
  "enabled": true,
  "path": "/mcp"
}
{
  "mcpServers": {
    "datagouv": {
      "url": "https://mcp.data.gouv.fr/mcp",
      "type": "http"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by YB0y

Auto Mode Hard-Deny Policies For Safe Automation

Set autoMode.hard_deny rules to block risky actions in auto mode.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by kiannidev

MCP OAuth Token Audience Checklist

Review remote MCP OAuth and token-audience handling before connecting clients.

Added 1mo ago
guidesReview firstSource-backedReview first
Safety ✓ Privacy ✓by JSONbored

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.