Alkemi MCP vs Marmot Data Catalog
A side-by-side look at the Alkemi MCP and Marmot Data Catalog MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Alkemi MCP for data platforms work as a local process; choose Marmot Data Catalog for data platforms. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Alkemi MCP when
- You need dedicated capabilities in the Data Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
BEARER_TOKEN.
Choose Marmot Data Catalog when
- You need dedicated capabilities in the Data Platforms domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 45/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | BEARER_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 620 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Alkemi MCP | View Marmot Data Catalog |
Tools & capabilities
Alkemi MCP tools
No tool names declared yet. Check the project README from the listing page.
Marmot Data Catalog 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.
Alkemi MCP
{
"mcpServers": {
"alkemiai-alkemi-mcp": {
"command": "npx",
"args": [
"@alkemiai/alkemi-mcp"
],
"env": {
"BEARER_TOKEN": "YOUR_BEARER_TOKEN_HERE"
}
}
}
}
Marmot Data Catalog
No confirmed install command for Marmot Data Catalog yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Alkemi MCP is categorized under Data Platforms and uses a local stdio subprocess. Marmot Data Catalog belongs to Data Platforms and uses an install path we have not confirmed yet. Pick Alkemi MCP for data platforms work and Marmot Data Catalog 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. Marmot Data Catalog has no confirmed install command yet — follow its own setup instructions.
Alkemi MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Marmot Data Catalog 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 alkemiai-alkemi-mcp and marmot-data-catalog as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Alkemi MCP has a quality signal of 45/100 (Fair) with 4 views, 0 installs and 4 GitHub stars. Marmot Data Catalog has 40/100 (Fair) with 1 views, 0 installs and 620 GitHub stars.