mcpbeat

Wolfram MCP Server

com.wolfram/mcp
answering

Wolfram is answering right now. Last checked 12 min ago. It exposes 3 tools.

Integrates Wolfram Language and Wolfram|Alpha accessing curated data and sophisticated algorithms.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
741 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add mcp --transport http https://agenttools.wolfram.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://agenttools.wolfram.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://agenttools.wolfram.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://agenttools.wolfram.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://agenttools.wolfram.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

wolframalpha
WolframAlpha
Use natural language queries with Wolfram|Alpha to get up-to-date computational results about entities in chemistry, physics, geography, history, art, astronomy, and more.
wolframcontext
WolframContext
Uses semantic search to retrieve any relevant information from Wolfram. Always use this tool at the start of new conversations or if the topic changes to ensure you have up-to-date relevant information. This uses semantic search, so the context argument should be written in natural language (not a search query) and contain as much detail as possible (up to 250 words).
wolframlanguageevaluator
WolframLanguageEvaluator
Evaluates Wolfram Language code for the user in a Wolfram Language kernel. If a formatted result is provided as a markdown link, use that in your response instead of typing out the output. Parse natural language input with `\[FreeformPrompt]["query"]`, which is analogous to ctrl+= input in notebooks. Natural language input is parsed before evaluation, so it works like macro expansion. You should ALWAYS use this natural language input to obtain things like `Quantity`, `DateObject`, `Entity`, etc. This is a stateless kernel, so you cannot reuse definitions from previous evaluations.

Endpoints

URLTransportStateLatencyChecked
https://agenttools.wolfram.com/mcp streamable-http answering 667 ms 12 min ago

Wolfram — questions

Answers built from our own checks of this server.

What can Wolfram do?
It exposes 3 tools, read directly from the server on our last check. Among them: WolframAlpha, WolframContext, WolframLanguageEvaluator. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Wolfram working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 741 ms. The bar chart above shows every period we have measured.
How do I connect Wolfram?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Wolfram need an API key?
No. Wolfram completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Wolfram?
It answers our handshake in 741 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.