Log inSubmit server
Openmetadata logo

Openmetadata

Connects AI agents to OpenMetadata for metadata CRUD, lineage, data quality, search, and workflow automation.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Openmetadata

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "openmetadata-2": {
      "command": "npx",
      "args": [
        "-y",
        "@us-all/openmetadata-mcp"
      ],
      "env": {
        "OPENMETADATA_HOST": "YOUR_VALUE_HERE",
        "OPENMETADATA_TOKEN": "YOUR_VALUE_HERE",
        "OPENMETADATA_ALLOW_WRITE": "YOUR_VALUE_HERE",
        "OM_TOOLS": "YOUR_VALUE_HERE",
        "OM_DISABLE": "YOUR_VALUE_HERE",
        "MCP_TRANSPORT": "YOUR_VALUE_HERE",
        "MCP_HTTP_TOKEN": "YOUR_VALUE_HERE",
        "MCP_HTTP_PORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 1 tools correctly (5d ago).

Overview

The openmetadata MCP server connects AI agents to OpenMetadata through stdio or Streamable HTTP, using a host URL and JWT or bot token. It exposes 172 tools for metadata search, full entity CRUD, lineage, data quality, governance, services, and OM 1.12+ entities such as Data Contracts and Metrics. Four workflow prompts, seven read-only resources, and aggregation tools support lineage impact analysis, quality rollups, domain summaries, and table summaries. Reach for it when you need broader automation and entity coverage than OpenMetadata's embedded MCP, including older 1.x clusters.

Use cases

  • Analyze downstream and upstream lineage before changing a table
  • Investigate failing data-quality tests across time windows
  • Create glossary terms and link related concepts
  • Reassign ownership across multiple OpenMetadata entities
  • Summarize domains, tables, lineage, and quality metadata

Key features

  • 172 tools across ten OpenMetadata categories
  • Full CRUD for OpenMetadata entity types
  • Lineage impact, domain summary, and table summary aggregations
  • Four MCP workflow prompts
  • Seven URI-based read-only resources
  • stdio and Streamable HTTP transports

Tools1

What Openmetadata lets your agent do. Expand a tool for its parameters.

Verified live~196 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

What it can do

From the 1 tool this server returned when we ran it; 1 declare their own safety hints.

Makes network requests · 1Read-only tools · 1
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age187 days
Maintainers1

Observed 2026-10-19 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @us-all/openmetadata-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads196Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed1Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Openmetadata works

What openmetadata MCP server does

The openmetadata MCP server gives MCP-compatible AI clients access to an OpenMetadata deployment. It covers metadata search, lineage, data quality, governance, services, events, administration, and entity operations. The implementation advertises 172 tools across ten categories and supports CRUD operations across OpenMetadata entity types, including Data Contracts, Metrics, Search Indexes, API Collections, and API Endpoints.

It also adds operations that combine several OpenMetadata requests. lineage-impact walks upstream and downstream lineage, counts affected consumers, groups them by entity type, and resolves owners for notifications. get-domain-summary and get-table-summary collect related metadata in fewer calls than retrieving each part separately. semantic-search queries the OpenMetadata vector index for cases where keyword matching does not find synonymous terms.

How it works

The openmetadata MCP server runs as a standalone npm package, Docker image, or built Node.js application. Its default transport is stdio. Setting MCP_TRANSPORT=http enables Streamable HTTP with a /mcp JSON-RPC endpoint and a public /health liveness endpoint. HTTP mode uses Bearer authentication unless explicitly disabled or handled by a reverse proxy.

Clients can access seven URI-based resources, including table, glossary-term, lineage, search, dashboard, pipeline, and schema resources. Four MCP prompts provide reusable workflows for lineage impact analysis, data-quality investigation, glossary-term creation, and owner reassignment. The lineage-impact result can render as an Apps SDK card in ChatGPT clients; other clients receive the same information as JSON content.

Setup and configuration

The server requires OPENMETADATA_HOST and OPENMETADATA_TOKEN. The host points to the OpenMetadata API, while the token is a JWT or bot token obtained from OpenMetadata's Settings and Bots area. Run the package with npx, add it to Claude Desktop or Claude Code, use the published Docker image, or build it from source with pnpm.

Writes are disabled by default. Set OPENMETADATA_ALLOW_WRITE=true to permit create, update, and delete operations. Use OM_TOOLS to allow selected categories, or OM_DISABLE to deny categories when no allowlist is present. HTTP deployments can set MCP_HTTP_TOKEN, MCP_HTTP_PORT, MCP_HTTP_HOST, and MCP_HTTP_SKIP_AUTH as needed.

Tools and capabilities

The openmetadata MCP server supports projection of selected response fields through extractFields on 28 read tools. This can reduce response size when an agent needs only names, columns, or data types. The search-tools meta-tool helps clients discover available tools at runtime.

Supported categories include search, core operations, discovery, governance, quality, services, administration, events, entities, and metadata utilities. Read-only resources expose common OpenMetadata objects by URI. The server is intended for bulk metadata operations, automation, sample-data access, full entity CRUD, and clusters running OpenMetadata versions before 1.12.

Limitations and notes

The openmetadata MCP server uses a JWT or bot token and its own write gate; it does not provide the embedded OpenMetadata MCP's OAuth2, personal-access-token, or Authorization Engine behavior. For SSO-oriented, RBAC-aware governance, the embedded MCP may be a better fit. This server and the embedded MCP are complementary rather than interchangeable.

The package supports OpenMetadata 1.x, while the embedded MCP ships with OpenMetadata 1.12 and later. Data Contract features described here depend on the relevant OpenMetadata API support. In HTTP mode, secure the Bearer token appropriately; MCP_HTTP_SKIP_AUTH removes the server's own authentication check.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Openmetadata

openmetadata is an MCP server that connects AI clients to an OpenMetadata deployment through stdio or Streamable HTTP. Its main tools cover metadata search, full entity CRUD, lineage, data quality, governance, semantic search, Data Contracts, Metrics, and related OpenMetadata resources for automation and investigation.

Install it with npx, Docker, or from source with pnpm. For npx, configure an MCP client to run `npx -y @us-all/openmetadata-mcp`, then provide `OPENMETADATA_HOST` and `OPENMETADATA_TOKEN`. The README includes configurations for Claude Desktop and Claude Code.

Yes, it works with Claude Desktop over the default stdio transport. Add an `openmetadata` MCP entry that runs the npm package with `npx`, and set the OpenMetadata host URL and JWT or bot token in the entry's environment.

Set `OPENMETADATA_ALLOW_WRITE=true` before starting the server. Mutations remain disabled by default; enabling this variable permits create, update, and delete operations using the configured OpenMetadata token.

Yes, set `MCP_TRANSPORT=http` to enable Streamable HTTP. The server exposes `/mcp` for Bearer-authenticated JSON-RPC requests and `/health` for liveness checks. Set `MCP_HTTP_TOKEN` unless authentication is intentionally skipped or delegated to a reverse proxy.

Related MCP servers

All in Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenmetadata AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/openmetadata-2?style=directory)](https://allmcps.com/mcp/openmetadata-2)
HTML Embed
<a href="https://allmcps.com/mcp/openmetadata-2"><img src="https://allmcps.com/api/badge/openmetadata-2?style=directory" alt="Openmetadata on AllMCPs" /></a>