RunMat
  • Pricing
RunMat
GitHub
GitHub
Sign inTry in browser
DesktopRuntimePhysicsCADAdministrationAgent

Get RunMat updates

New releases, guides and examples.

Product+
  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download
Math+
  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting
Physics+
  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA
Industries+
  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance
Learn+
  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students
Compare+
  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons
Company+
  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms

Product

  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download

Math

  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting

Physics

  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA

Industries

  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance

Learn

  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students

Compare

  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons

Company

  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms
GitHubXLinkedIn

© Dystr, Inc. · RunMat v0.7.1, Nov 17, 2026

RunMat® is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

/
    • Overview
    • Codex
    • Claude Code
    • Other MCP Clients
Docs>Agent

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:

SettingValue
Namerunmat
TransportStreamable HTTP
URLhttp://127.0.0.1:47862/mcp
HeaderAuthorization: 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:

  1. Initialize MCP protocol version 2025-06-18 or negotiate a supported version.
  2. List tools with JSON Schema input and output contracts.
  3. Call namespaced tools such as runmat.get_status and runmat.execute_code.
  4. Preserve structured tool results.
  5. Send a custom Authorization header 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.
On this page
  • Connect to RunMat Desktop
  • Verify compatibility
  • Security guidance