Jitsu vs Openmetadata
A side-by-side look at the Jitsu and Openmetadata MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Jitsu for data platforms work; choose Openmetadata for data platforms as a local process. 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 41/100 · Fair | 55/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | OPENMETADATA_HOSTOPENMETADATA_TOKENOPENMETADATA_ALLOW_WRITEOM_TOOLSOM_DISABLEMCP_TRANSPORTMCP_HTTP_TOKENMCP_HTTP_PORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5,110 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Jitsu | View Openmetadata |
Tools & capabilities
Jitsu tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Jitsu
No confirmed install command for Jitsu yet — follow the setup steps linked from its listing page rather than a guessed package name.
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"
}
}
}
}
Frequently asked questions
Jitsu is categorized under Data Platforms and uses an install path we have not confirmed yet. Openmetadata belongs to Data Platforms and uses a local stdio subprocess. Pick Jitsu for data platforms work and Openmetadata 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. Jitsu has no confirmed install command yet — follow its own setup instructions.
Jitsu has no declared pricing — check the project's own site. Openmetadata has no declared pricing — check the project's own site. 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 jitsu and openmetadata-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jitsu has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 5,110 GitHub stars. Openmetadata has 55/100 (Good) with 6 views, 0 installs and 0 GitHub stars.