🤖 Computational Research
A Wolfram-centric Claude plugin for AI-assisted computational research.
- 📁 Turns a folder with resources (code, PDFs, Markdown, notebooks, ...) into an organized git repo, which it maintains.
- 🐺 Imports and exports Wolfram notebooks via conversion to Markdown.
- 📚 Grows and maintains a wiki knowledge base.
- 🔍 Gathers and summarizes resources, keeping a Markdown summary and recovery options (e.g. where to download).
- 📦 Converts code into a paclet and helps with its build and deployment (e.g. with or without docs, local build or cloud).
- 📓 Generates expository Wolfram notebooks and helps publish them on Wolfram Cloud (explicitly marked as LLM-generated, keeping a Markdown mirror).
- 📝 Scaffolds a LaTeX or Typst paper and edits the user-owned document on request.
- 🧬 Optionally records the prompt and intent behind every generated artifact, keeping it traceable.
- 📔 Optionally keeps a running scientific journal in LaTeX or Typst — concise, cited def/thm/rem entries of what was learned.
- 🧭 Offers a guided tour through the project for a human, and a revision protocol (stateful for multi-session work).
- ✅ Tracks plans, todos, and state.
⚠️ Disclaimer. This repo grows on the fly out of my own thoughts and needs around AI assistance in computational research. It is a working draft, in need of human revision and selective improvement. Helpers and testers welcome!
📥 Installation
The plugin is distributed through the WolframInstitute plugin marketplace.
Claude Code (CLI / VS Code extension) — the author's setup:
claude plugin marketplace add WolframInstitute/ClaudePluginMarketplace
claude plugin install computational-research@WolframInstitute
Claude Desktop app — install from the marketplace GUI.
Note: Operation in Cowork mode and Chat mode has not been tested.
⚙️ Recommended Setup
The plugin works best with Wolfram Engine (or Mathematica).
MCP servers — the plugin draws on these:
Installing the official Wolfram server:
InstallMCPServer["ClaudeCode", "WolframLanguage"]
Note: On older Wolfram versions, the legacy Wolfram/MCPServer paclet still works as a fallback if that is what you have installed.
🔑 License seats. Each running kernel — every Wolfram MCP server, every
open front-end, every wolframscript call — consumes one of your license's
$MaxLicenseProcesses seats. The plugin is MCP-first: it routes Wolfram
work through the official server's single persistent kernel and treats the
.wls scripts as a fallback for when no MCP is attached (e.g. headless runs).
Before spawning wolframscript it checks headroom and warns rather than
failing opaquely. Running both Wolfram MCP servers at once uses two seats —
/check-env reports live headroom and flags this.
🧩 Skills
Skills share their name with the matching slash command (one name per feature), grouped by domain.
