---
name: project-check-env
description: Check local research tools, connected Wolfram MCP capabilities and license headroom without starting a kernel.
---

Before acting, read [the runtime guidance](../../RUNTIME.md).


Run `${PLUGIN_ROOT}/scripts/check-env.sh` using the shell tool and display the full output.

Then test MCP availability directly:

1. **Official Wolfram MCP** (primary): evaluate `1+1` with `mcp__Wolfram__WolframLanguageEvaluator`.
   Required for computation.
2. **WolframPacletDevelopment tools**: try calling `mcp__Wolfram__CodeInspector` on a trivial expression.
   If it works, the full tool set is available (ReadNotebook, WriteNotebook, SymbolDefinition, CodeInspector, TestReport, CreateSymbolDoc, EditSymbolDoc, EditSymbolDocExamples).
3. **Unofficial Wolfram MCP** (optional): call `mcp__wolfram__ping`.
   If available, its LSP tools can be used for code navigation.

Then check **license headroom** (this is the usual cause of `wolframscript` failures).
On the official MCP — which reuses one persistent kernel and costs no extra seat — evaluate with `mcp__Wolfram__WolframLanguageEvaluator`:

```wolfram
With[{free = $MaxLicenseProcesses - $LicenseProcesses},
  <|"Max" -> $MaxLicenseProcesses, "InUse" -> $LicenseProcesses,
    "Free" -> free, "Saturated" -> free <= 0|>]
```

Report `Max / InUse / Free`.
If `Free <= 0`, warn that **any `wolframscript` spawn will fail with a license error** — each running Wolfram MCP server and each open front-end holds one of the seats, and two Wolfram MCP servers (official `Wolfram` + unofficial `wolfram`) are commonly configured at once.
Tell the user to either route work through the MCP (preferred — no new seat) or free a seat (close a front-end, or disable whichever Wolfram MCP server is unused).

After showing the output, summarize:
1. Whether the Wolfram kernel is available and working
2. Whether the official Wolfram MCP is available (required)
3. Which MCP profile is active (Wolfram vs WolframPacletDevelopment)
4. Whether the unofficial Wolfram MCP is available (optional, for LSP)
5. Whether this appears to be a **remote environment** (MCP succeeds but script reports no local kernel)
6. **License headroom** — `Free` seats, and whether the environment is saturated (so the plugin should stay on the MCP path and avoid spawning `wolframscript`)
7. What to do if anything is missing

If WolframPacletDevelopment is not active, suggest switching by setting `MCP_SERVER_NAME=WolframPacletDevelopment` in the MCP server config.

Also check whether Wiki/ exists in the current directory.
If not, suggest running wiki-init to set up the knowledge base.