Wolfram Alpha vs Jacobian
A side-by-side look at the Wolfram Alpha 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 Wolfram Alpha for data science tools work as a local process; 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 Wolfram Alpha when
- You need dedicated capabilities in the Data Science Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_WOLFRAM_KEY.
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 | 41/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | PLATFORM_WOLFRAM_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 322 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Wolfram Alpha | View Jacobian |
Tools & capabilities
Wolfram Alpha 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.
Wolfram Alpha
{
"mcpServers": {
"wolfram-alpha": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-wolfram-alpha"
],
"env": {
"PLATFORM_WOLFRAM_KEY": "YOUR_PLATFORM_WOLFRAM_KEY_HERE"
}
}
}
}
Jacobian
{
"mcpServers": {
"jacobian": {
"command": "npx",
"args": [
"-y",
"jacobian@latest"
]
}
}
}
Frequently asked questions
Wolfram Alpha is categorized under Data Science Tools and uses a local stdio subprocess. Jacobian belongs to Data Science Tools and uses a local stdio subprocess. Pick Wolfram Alpha for data science tools work and Jacobian for data science tools.
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.
Wolfram Alpha has no declared pricing — check the project's own site. Jacobian 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 wolfram-alpha and jacobian as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Wolfram Alpha has a quality signal of 41/100 (Fair) with 3 views, 0 installs and 0 GitHub stars. Jacobian has 49/100 (Fair) with 1 views, 0 installs and 322 GitHub stars.