Scherlok vs Capsulemcp
A side-by-side look at the Scherlok and Capsulemcp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Scherlok for data platforms work as a local process; choose Capsulemcp 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 Scherlok 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.
Choose Capsulemcp 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:
CAPSULE_API_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 55/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | CAPSULE_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 5 |
| Directory activity | 3 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Scherlok | View Capsulemcp |
Tools & capabilities
Scherlok tools
No tool names declared yet. Check the project README from the listing page.
Capsulemcp 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.
Scherlok
{
"mcpServers": {
"rbmuller-scherlok": {
"command": "uvx",
"args": [
"--from",
"scherlok[duckdb]",
"scherlok"
]
}
}
}
Capsulemcp
{
"mcpServers": {
"soil-dev-capsulemcp": {
"command": "npx",
"args": [
"-y",
"cache"
],
"env": {
"CAPSULE_API_TOKEN": "YOUR_CAPSULE_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Scherlok is categorized under Data Platforms and uses a local stdio subprocess. Capsulemcp belongs to Data Platforms and uses a local stdio subprocess. Pick Scherlok for data platforms work and Capsulemcp 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.
Scherlok is listed as free. Auth: api key required. Capsulemcp is listed as free. Auth: api key required. 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 rbmuller-scherlok and soil-dev-capsulemcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Scherlok has a quality signal of 55/100 (Good) with 3 views, 0 installs and 11 GitHub stars. Capsulemcp has 60/100 (Good) with 5 views, 0 installs and 5 GitHub stars.