Skip to main content

MATLAB Simulink MCP Server

This Model Context Protocol (MCP) server lets MCP clients (such as Claude Desktop or other LLM-based agents) to interact with MATLAB and Simulink in real time. It runs locally, is built on FastMCP 2.0, and communicates with MATLAB and Simulink via the MATLAB Engine for Python API.

Features

  • Allows an LLM client to

    • Read, write, and execute MATLAB code and scripts
    • Parse and interact with Simulink models
    • Access workspace and results (inculding visualizations)
  • Execution Safety

    • Basic safeguards against unsafe commands
    • Restricted to current working directory (only manually changeable)
  • Robust Runtime

    • Non-blocking execution (asyncronous MATLAB engine calls)
    • Automatic installation of MATLAB Engine library if unavailable

Requirements

  • MATLAB R2022b or later
  • Python 3.10–3.12 (check which version is supported by your MATLAB installation)

Installation

  1. Create and activate a Python virtual environment (uv is recommended, automatically installs Python version if missing):

    uv venv --python 3.12           # match Python to your MATLAB-supported version
    source .venv/Scripts/activate   # on macOS/Linux: source .venv/bin/activate
    

    Without uv, you will first need to download and install the required Python version manually:

    python3.12 -m venv .venv        # match Python to your MATLAB-supported version
    source .venv/Scripts/activate   # on macOS/Linux: source .venv/bin/activate
    
  2. Install:

    uv pip install matlab-simulink-mcp
    # or without uv
    pip install matlab-simulink-mcp
    
  3. On the first run, if MATLAB Engine is not found, the server will open a console window and guide you through installation.

Configuration

Claude Desktop

  1. Open Claude Desktop Settings → Developer → Edit Config.

  2. In the claude_desktop_config.json, add or update:

    {
    "mcpServers": {
        "MATLAB_Simulink_MCP": {
            "command": "<absolute-path-to>/.venv/Scripts/python.exe", // absolute path to your Python environment executable
            "args": [
                "-m", 
                "matlab_simulink_mcp"
                ],
            "env": {
                "LOG_DIR": "<absolute-path-to>/logs" // Optional: absolute path to a folder for logs
                }
            }
        }
    }
    
  3. Save and restart Claude Desktop. (Ensure it is fully closed in Task Manager/Activity Monitor.)

  4. Server's status can be checked from Settings → Developer, or the equalizer button in Claude's chat box.

Claude Code / Codex CLI

  1. Run the following command in terminal:

    claude mcp add MATLAB_Simulink_MCP --env LOG_DIR="<absolute-path-to>/logs" -- "<absolute-path-to>/.venv/bin/python" -m matlab_simulink_mcp
    

    For Codex CLI, use codex instead of claude.

  2. Restart by opening a new terminal.

  3. To check server status, run claude mcp list or codex mcp list.

For more information, see documentation for Claude Code or Codex CLI.

Notes

  1. On macOS/Linux, use <absolute-path-to>/.venv/bin/python instead for the path to Python.

  2. Only use / or \\ in the paths, not \.

  3. On first launch, the server may open multiple consoles to install MATLAB Engine. Interact with one, complete installation, then restart the application if needed.

  4. Any client is restricted to the current MATLAB working directory, which can only be changed manually for safety reasons.

  5. The server logs outputs and errors its own log file as well. To keep a log file tracking console open, add "--console" to config args. The log file is in the folder specified via environment variable LOG_DIR, or otherwise in the user log directory.

Debugging

FastMCP 2.0 includes an MCP Inspector for manual testing and debugging without an LLM client. It launches a web UI to send dummy requests directly to the server. The inspector finds and runs a server object named mcp itself. So you will need to import matlab_simulink_mcp.server.mcp as mcp in a script and then run it:

fastmcp dev script_name.py

Metadata

Release files for matlab-simulink-mcp 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for matlab-simulink-mcp 0.1.6
File Size Uploaded Provenance Actions
matlab_simulink_mcp-0.1.6.tar.gz 74.5 kB Without provenance Details for matlab_simulink_mcp-0.1.6.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for matlab-simulink-mcp 0.1.6
File Interpreter ABI Platform Actions
matlab_simulink_mcp-0.1.6-py3-none-any.whl Python 3 none any Details for matlab_simulink_mcp-0.1.6-py3-none-any.whl

Total release size: 150.8 kB

Security for matlab-simulink-mcp 0.1.6

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page