Mathematica Documentation MCP Server

MCP server for checking Mathematica documentation via local MMA installation. The mathematica documentation mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

Made with mcp-python-sdk

Its toolset

Everything the assistant can do here goes through one of these:

• get_docs — support factory functions, function via an addon, and function via a package
• list_package_symbols — list all symbols/functions in a package

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need one environment variable: WOLFRAMSCRIPT_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Mathematica Documentation's toolset — get_docs, list_package_symbols — is a fair guide to whether it matches your workflow. It is maintained by benhaotang; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mathematica documentation mcp server does with a few real requests.