Model Context Protocol (MCP) server for OpenMetadata
MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. Model Context Protocol (MCP) server for OpenMetadata.
A Model Context Protocol (MCP) server implementation for OpenMetadata, enabling seamless integration with MCP clients. This project provides a standardized way to interact with OpenMetadata through the Model Context Protocol.
This project implements a Model Context Protocol server that wraps OpenMetadata's REST API, allowing MCP clients to interact with OpenMetadata in a standardized way.
Once MCP is connected, these are the calls the assistant has available:
Feature — API PathLineage — The Lineage tool exposed by this serverUsage — The Usage tool exposed by this serverYou will need 4 environment variables: OPENMETADATA_HOST, OPENMETADATA_JWT_TOKEN, OPENMETADATA_USERNAME, OPENMETADATA_PASSWORD. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — Feature, Lineage, Usage — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Feature | API Path |
| Lineage | The Lineage tool exposed by this server. |
| Usage | The Usage tool exposed by this server. |
{
"mcpServers": {
"mcp-server-openmetadata": {
"command": "uvx",
"args": ["mcp-server-openmetadata"],
"env": {
"OPENMETADATA_HOST": "https://your-openmetadata-host",
"OPENMETADATA_JWT_TOKEN": "your-jwt-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPENMETADATA_HOST | Endpoint or connection string the server talks to. | Optional |
| OPENMETADATA_JWT_TOKEN | Credential the server authenticates with. | Yes |
| OPENMETADATA_USERNAME | Configuration value read at startup. | Optional |
| OPENMETADATA_PASSWORD | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.