# openmetadata [Health: Active]

**Category:** 📊 Data Platforms  
**Repository:** https://github.com/us-all/openmetadata-mcp-server  
**GitHub Stars:** 0  
**npm Downloads (last month):** 196  
**Views:** 6  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/openmetadata-2

## Description
OpenMetadata MCP — metadata, lineage, search, data quality, OM 1.12+ Data Contracts

## Tools
Capabilities this server exposes over MCP:

- **search-tools** — Discover available tools by natural language query. Returns matching tool names + descriptions across all categories. Use this to navigate the 154-tool surface efficiently — call this first, then call the specific tool you need.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "openmetadata": {
    "command": "npx",
    "args": ["-y","@us-all/openmetadata-mcp"],
    "env": {
      "OPENMETADATA_HOST": "",
      "OPENMETADATA_TOKEN": "",
      "OPENMETADATA_ALLOW_WRITE": "",
      "OM_TOOLS": "",
      "OM_DISABLE": "",
      "MCP_TRANSPORT": "",
      "MCP_HTTP_TOKEN": "",
      "MCP_HTTP_PORT": ""
    }
  }
}
```

**Requires environment variables:** `OPENMETADATA_HOST`, `OPENMETADATA_TOKEN`, `OPENMETADATA_ALLOW_WRITE`, `OM_TOOLS`, `OM_DISABLE`, `MCP_TRANSPORT`, `MCP_HTTP_TOKEN`, `MCP_HTTP_PORT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/openmetadata-2/readme_