Autocarver vs Jacobian
A side-by-side look at the Autocarver and Jacobian MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Autocarver for data science tools work; choose Jacobian for data science tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Autocarver when
- You need dedicated capabilities in the Data Science Tools domain.
Choose Jacobian when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Science Tools | Data Science Tools |
| Quality signal | 37/100 · Fair | 49/100 · Fair |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 318 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Autocarver | View Jacobian |
Tools & capabilities
Autocarver tools
No tool names declared yet. Check the project README from the listing page.
Jacobian 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.
Autocarver
No confirmed install command for Autocarver yet — follow the setup steps linked from its listing page rather than a guessed package name.
Jacobian
{
"mcpServers": {
"jacobian": {
"command": "npx",
"args": [
"-y",
"jacobian@latest"
]
}
}
}