# SecretiveShell/MCP-wolfram-alpha [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/SecretiveShell/MCP-wolfram-alpha  
**GitHub Stars:** 75  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/secretiveshell-mcp-wolfram-alpha

## Description
An MCP server for querying wolfram alpha API.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-wolfram-alpha": {
    "command": "npx",
    "args": ["-y","@wong2/mcp-cli"],
    "env": {
      "WOLFRAM_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `WOLFRAM_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What SecretiveShell/MCP-wolfram-alpha MCP server does

SecretiveShell/MCP-wolfram-alpha MCP server exposes Wolfram Alpha through the Model Context Protocol. Its primary tool accepts a text query and returns a string containing the Wolfram Alpha API result. This lets an MCP client send questions to Wolfram Alpha without implementing the API call as part of the client application.

The project also defines a `wa` prompt. Given a query, the prompt produces an instruction asking Wolfram Alpha to answer that question. The README compares this behavior to the `!wa` command used in DuckDuckGo search.

## How it works

The server receives a query through the MCP tool and forwards it to the Wolfram Alpha API. The exposed function is named `query_wolfram_alpha` and accepts one string parameter, `query`. The prompt is named `wa` and also accepts a query string.

The repository's example configuration runs the project with `uv`, using the project's directory and the `MCP-wolfram-alpha` run target. The provided examples are intended for an MCP client configuration, including Claude Desktop-style configuration files.

## Setup and configuration

SecretiveShell/MCP-wolfram-alpha MCP server requires the `WOLFRAM_API_KEY` environment variable. The README directs users to obtain an API key from Wolfram Alpha's API site. In the example client configuration, the key is passed in the server's `env` object under that exact variable name.

The documented launch configuration uses `uv --directory <project-directory> run MCP-wolfram-alpha`. Because the directory value in the README is an example path, it must be replaced with the actual local checkout path before use. The README says the project was tested with Wolfram Alpha's full results API, while noting that this API mode may not be required.

## Tools and capabilities

- `query_wolfram_alpha(query: str)`: queries the Wolfram Alpha API.
- `wa(query: str)`: creates a prompt instructing Wolfram Alpha to answer the supplied question.

## Limitations and notes

SecretiveShell/MCP-wolfram-alpha MCP server cannot run without a Wolfram API key according to the setup instructions. The supplied material does not document additional tools, authentication methods beyond the environment variable, response schemas, rate limits, or supported client behavior beyond the Claude Desktop-style configuration example.

For debugging, the README recommends creating a configuration file in the same general format as a Claude Desktop configuration and using `npx @wong2/mcp-cli -c <config-file>`. That command is described as a debugging approach rather than the server itself.

_Full upstream README: https://allmcps.com/mcp/secretiveshell-mcp-wolfram-alpha/readme_