{
  "markdown": "# @pipeworx/wolfram-alpha\n\nWolfram Alpha MCP — computational, factual, and quantitative queries.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `short_answer(query, units?)` — single terse plain-text answer.\n- `full_query(query, units?, include_pods?, format?)` — structured pods.\n- `wolfram_compute(code, time_constraint_seconds?)` — evaluate Wolfram Language\n  code in a real kernel (keyless; proxies Wolfram's hosted MCP evaluator).\n\n## Auth\n\n- **Platform key:** gateway env `PLATFORM_WOLFRAM_KEY` (short_answer / full_query only).\n- **BYO:** `?_apiKey=<appid>` after registering at https://developer.wolframalpha.com (free 2,000/mo).\n- `wolfram_compute` needs no key.\n\n## Evaluation semantics (triage note)\n\n`wolfram_compute` transmits `code` verbatim — as a JSON field, no URL encoding\nanywhere in the path — and the kernel evaluates exactly what was sent. A result\nthat disagrees with the *intent* of a question is almost certainly a bug in the\nsubmitted code, not in transmission or the kernel. Before filing a tool bug,\necho the parse back through the tool itself:\n\n```\nwolfram_compute({ code: \"ToString[Hold[<the code>], InputForm]\" })\n```\n\nWorked incident (fleet #422, 2026-08-17): `Length[Select[Permutations[Range[5]],\nAnd@@Thread[#!=Range[5]]&]]` was reported as \"returns 119, should be 44\n(derangements of 5)\". 119 is the correct value of that code: on two concrete\nlists, `perm != Range[5]` evaluates eagerly to a single True/False (whole-list\n`Unequal`) before `Thread` can split it elementwise, so the predicate collapses\nto \"permutation ≠ identity\" and counts 120 − 1 = 119. The elementwise form\n`And @@ MapThread[Unequal, {#, Range[5]}] &` (or just `Subfactorial[5]`) returns\n44 through the same tool.\n\n## Data source\n\n- Short Answers v1: `https://api.wolframalpha.com/v1/result`\n- Full Results v2: `https://api.wolframalpha.com/v2/query` (`output=JSON`)\n- Wolfram Language kernel: `https://agenttools.wolfram.com/mcp` (hosted by Wolfram Research)\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"wolfram-alpha\": {\n      \"url\": \"https://gateway.pipeworx.io/wolfram-alpha/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/wolfram-alpha/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Wolfram Alpha data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4093,
  "sha": "f7ef9201fa2ea90b7103e80f97a105190f612bb5c06c2cffcf6c3761925740b5",
  "repo_slug": "pipeworx-io/mcp-wolfram-alpha",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_wolfram_alpha_01f3e317/readme"
}