Wolfram Alpha

What Wolfram Alpha MCP server does

The Wolfram Alpha MCP server exposes Wolfram Alpha’s computational and factual query capabilities through MCP tools. It can return a concise plain-text result for a question, provide structured result pods for applications that need more detail, or evaluate Wolfram Language code in a hosted kernel.

The package is available through the Pipeworx gateway or as a local npm-based stdio process. The gateway route can also expose shared Pipeworx meta-tools, while the standalone process presents only the Wolfram Alpha tool set.

How it works

The server maps natural-language questions to two Wolfram Alpha API versions. short_answer uses the Short Answers endpoint and is intended for one terse result. full_query uses the Full Results endpoint and can return structured pods, with options for units, pod inclusion, and output format.

wolfram_compute sends Wolfram Language source to a hosted Wolfram Research kernel. The submitted code is evaluated as written, so the result reflects the code’s semantics rather than an interpretation of the user’s intended question. When debugging a surprising result, first send code that renders the expression with Hold and InputForm to inspect how it parses.

Setup and configuration

For a hosted connection, add the gateway’s streamable HTTP endpoint to an MCP client. The README names Claude Desktop, Cursor, and Windsurf as examples. The full Pipeworx endpoint is another option when agents should access all available packs directly; either gateway route can use ask_pipeworx for broader catalog routing.

A local installation can run with npx -y @pipeworx/mcp-wolfram-alpha and communicate over standard input and output. This mode does not require a Pipeworx account and does not add the gateway’s shared meta-tools. The gateway also offers HTTP tool calls for clients that do not use MCP directly.

short_answer and full_query can authenticate with the gateway’s PLATFORM_WOLFRAM_KEY, or with a Wolfram Alpha app ID supplied as the _apiKey query parameter. The app ID requires registration with Wolfram Alpha. wolfram_compute is keyless.

Tools and capabilities

• short_answer(query, units?) returns one short, plain-text answer.
• full_query(query, units?, include_pods?, format?) returns structured result data.
• wolfram_compute(code, time_constraint_seconds?) evaluates Wolfram Language code in a real hosted kernel.

These tools cover direct calculations, factual lookups, quantitative questions, unit-sensitive requests, and code-driven Wolfram Language computations. The time_constraint_seconds argument can set a time limit for kernel evaluation.

Limitations and notes

The Wolfram Alpha MCP server does not make wolfram_compute infer or repair incorrect code. Expressions are transmitted verbatim, and a logically incorrect predicate or grouping can produce a valid but unexpected result. Validate the parsed expression through the compute tool before treating a surprising calculation as a transport or kernel defect.

Gateway pack endpoints include shared Pipeworx tools in addition to the pack’s own tools, so their tool list is larger than the three capabilities described here. The standalone process lists only these Wolfram Alpha tools. Wolfram Alpha app-ID access is limited by the registered service’s quota, which the README identifies as 2,000 requests per month for the free tier.