Other MCP-compatible client setup
RunMat Desktop serves RunMat's MCP tools on your computer while the app is open and signed in. An MCP client on the same computer can use them if it supports Streamable HTTP with custom headers. The client works in the Projects open in RunMat's windows, and runs appear in the app.
For Claude Code and Codex, connect from RunMat Desktop instead. See Coding agents on your computer.
Connect to RunMat Desktop
Enter these values in your client's MCP settings:
| Setting | Value |
|---|---|
| Name | runmat |
| Transport | Streamable HTTP |
| URL | http://127.0.0.1:47862/mcp |
| Header | Authorization: Bearer <token>, with the token from ~/.runmat/mcp-headers.json |
RunMat Desktop writes the token file after you sign in. The client must send the header on every request, so read it from the file when the client starts.
The first time a tool works in a Project, RunMat asks in Connected agents: Allow while this project is open, or Always allow.
RunMat keeps using the same Project during a workflow. To switch, ask the model to stop the current work and select the new Project explicitly.
Verify compatibility
The client should be able to:
- Initialize MCP protocol version
2025-06-18or negotiate a supported version. - List tools with JSON Schema input and output contracts.
- Call namespaced tools such as
runmat.get_statusandrunmat.execute_code. - Preserve structured tool results.
- Send a custom
Authorizationheader on every request.
Every compatible client can use RunMat's execution results, diagnostics, variable previews, file summaries, and figure metadata.
Security guidance
- Open only the Projects the task needs in RunMat Desktop while a local client is connected.
- Review file changes and destructive tool approvals in the MCP client.
- Don't copy the RunMat Desktop token into shared configuration files.
- Remove the MCP connection from the client when access is no longer needed.