Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
MCP server for Wolfram Alpha queries
This repo provides an MCP server that lets an agent send questions to Wolfram Alpha. It includes a prompt helper for `!wa`-style questions and a tool for direct API queries.
Builders who want Claude, Cursor, or another MCP client to answer questions with Wolfram Alpha.
You can ask your agent computational questions and get grounded answers without leaving the chat.
What it does
Wolfram Alpha prompt
A `wa(query: str)` prompt that frames a question for Wolfram Alpha.
Query tool
A `query_wolfram_alpha(query: str)` tool that calls the Wolfram Alpha API.
API key configuration
Uses the `WOLFRAM_API_KEY` environment variable for authentication.
MCP server packaging
Ships as a Python MCP server runnable through `uv`.
How to get it
- 1Then run
npx @wong2/mcp-cli -c .\config.json
README
MCP-wolfram-alpha
A MCP server to connect to wolfram alpha API.
Components
Prompts
This is analogous to the !wa bang in duckduckgo search.
def wa(query: str) -> f"Use wolfram alpha to answer the following question: {query}"
Tools
Query Wolfram Alpha api.
def query_wolfram_alpha(query: str) -> str
Configuration
You must set the WOLFRAM_API_KEY environment variable. Get an api ket from Wolfram Alpha.
This was tested with the full results API, but it might not be required.
{
"mcpServers": {
"MCP-wolfram-alpha": {
"command": "uv",
"args": [
"--directory",
"C:\\Users\\root\\Documents\\MCP-wolfram-alpha",
"run",
"MCP-wolfram-alpha"
],
"env": {
"WOLFRAM_API_KEY": "your-app-id"
}
}
}
}
Development
Debugging
Since the official MCP inspector does not have good environment support, I reccommend using wong2's mcp-cli-inspector.
Create a config.json file in the same style as claude desktop.
{
"mcpServers": {
"MCP-wolfram-alpha": {
"command": "uv",
"args": [
"--directory",
"/full/path/to/MCP-wolfram-alpha",
"run",
"MCP-wolfram-alpha"
],
"env": {
"WOLFRAM_API_KEY": "your-app-id"
}
}
}
}
Then run:
npx @wong2/mcp-cli -c .\config.json
Files in the repo
- .github
- src
- .dockerignore
- .gitignore
- .python-version
- config.json.example
- Dockerfile
- LICENSE
- pyproject.toml
- README.md
- smithery.yaml
- uv.lock
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More connectors
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama…) with Codex CLI, App, SDK, and Claude Code
Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.
Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.
Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.