Mathematica Mcp

io.github.lars20070Published by GitHub account lars20070v0.1.11Updated Oct 24, 2026

MCP server for WolframScript

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Local MCP server that wraps WolframScript so an assistant can evaluate Wolfram Language code and inspect the Wolfram Engine installation.

What you can do
Evaluate Wolfram Language scripts through the local wolframscript command line and return the results to the assistant. Query the installed wolframscript version. Query the Wolfram Engine version. Query the Wolfram Engine license type.
When to use it
Useful when you want an assistant to run symbolic math, calculus, or other Wolfram Language computations on your own machine, or to check which Wolfram Engine and wolframscript versions are installed.
Requirements
Runs as a local process on the user's machine (desktop only). Requires WolframScript installed and activated, plus the uv package manager; the README configures it through uvx or a local clone. No API keys or environment variables are declared.
Before you install
The evaluate tool runs arbitrary Wolfram Language code on your machine through wolframscript, so only use it with code you trust. It depends on a locally activated Wolfram Engine license; the README notes Wolfram Engine and WolframScript are free for personal use, but other uses may require a license.

Installation

In SourceWeft

  1. Open Mathematica Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Mathematica MCP Server

[codecov] [Build] [Python Version] [License] [PyPI version]

MCP server that wraps Mathematica's wolframscript command-line interface. It provides tools to evaluate Wolfram Language code and retrieve information about the Wolfram Engine installation.

ToolDescription
evaluateEvaluates a Wolfram Language script
version_wolframscriptReturns version of wolframscript
version_wolframengineReturns version of Wolfram Engine
licensetypeReturns license type of Wolfram Engine

Background

  • Wolfram Language: symbolic programming language e.g. Integrate[x*Sin[x], x]
  • Wolfram Engine: kernel for running Wolfram Language code
  • WolframScript: command-line interface to Wolfram Engine
  • Mathematica: notebook interface to Wolfram Engine

Both Wolfram Engine and WolframScript are freely available for personal use.

Installation

  1. Please ensure WolframScript is installed and activated on your system.
bash
wolframscript -versionwolframscript -activatewolframscript -code "Integrate[x*Sin[x], x]"
  1. Install the uv package manager.
bash
curl -LsSf https://astral.sh/uv/install.sh | sh
  1. Edit the Claude Desktop config file and add the mathematica-mcp server. Note that uvx sets up an environment, installs the mathematica-mcp package, and runs the server by calling the mathematica-mcp entry point defined in pyproject.toml. No cloning of the repository is necessary. The logs are written to the default user log directory, e.g. ~/Library/Logs/mathematica_mcp/mathematica_mcp.log on macOS.
json
{  "mcpServers": {    "mathematica-mcp": {      "command": "uvx",      "args": [        "mathematica-mcp"      ]    }  }}

Claude Desktop config file on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  1. Alternatively, you can clone the repository and then modify or extend the MCP server code. In this case, make sure to update the path to the local repository in the Claude Desktop config file.
json
{  "mcpServers": {    "mathematica-mcp": {      "command": "uv",      "args": [        "--directory",        "/Users/lars/Code/mathematica-mcp",        "run",        "mathematica-mcp"      ]    }  }}

Claude Desktop config file on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Source: README.md at commit 2ddd459

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.11LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts