Openmetadata vs Jitsu
A side-by-side look at the Openmetadata and Jitsu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Openmetadata for data platforms work as a local process; choose Jitsu for data platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Openmetadata when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENMETADATA_HOST, OPENMETADATA_TOKEN, OPENMETADATA_ALLOW_WRITE, OM_TOOLS, OM_DISABLE, MCP_TRANSPORT, MCP_HTTP_TOKEN, MCP_HTTP_PORT. - You want tools like
search-tools.
Choose Jitsu when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 55/100 · Good | 58/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | OPENMETADATA_HOSTOPENMETADATA_TOKENOPENMETADATA_ALLOW_WRITEOM_TOOLSOM_DISABLEMCP_TRANSPORTMCP_HTTP_TOKENMCP_HTTP_PORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,112 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Openmetadata | View Jitsu |
Tools & capabilities
Openmetadata tools 1
search-toolsDiscover 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.
Jitsu tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Openmetadata
{
"mcpServers": {
"openmetadata-2": {
"command": "npx",
"args": [
"-y",
"@us-all/openmetadata-mcp"
],
"env": {
"OPENMETADATA_HOST": "YOUR_OPENMETADATA_HOST_HERE",
"OPENMETADATA_TOKEN": "YOUR_OPENMETADATA_TOKEN_HERE",
"OPENMETADATA_ALLOW_WRITE": "YOUR_OPENMETADATA_ALLOW_WRITE_HERE",
"OM_TOOLS": "YOUR_OM_TOOLS_HERE",
"OM_DISABLE": "YOUR_OM_DISABLE_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"MCP_HTTP_TOKEN": "YOUR_MCP_HTTP_TOKEN_HERE",
"MCP_HTTP_PORT": "YOUR_MCP_HTTP_PORT_HERE"
}
}
}
}
Jitsu
{
"mcpServers": {
"jitsu": {
"command": "npx",
"args": [
"-y",
"jitsu"
]
}
}
}
Frequently asked questions
Openmetadata is categorized under Data Platforms and uses a local stdio subprocess. Jitsu belongs to Data Platforms and uses a remote HTTP/SSE transport. Pick Openmetadata for data platforms work and Jitsu for data platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Openmetadata has no declared pricing — check the project's own site. Jitsu has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openmetadata-2 and jitsu as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openmetadata has a quality signal of 55/100 (Good) with 6 views, 0 installs and 0 GitHub stars. Jitsu has 58/100 (Good) with 1 views, 0 installs and 5,112 GitHub stars.