MATLAB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MATLAB_PATH | Yes | Path to the MATLAB executable |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_matlab_codeC | Execute MATLAB code and return the results |
| generate_matlab_codeC | Generate MATLAB code from a natural language description |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| MATLAB Getting Started Guide | Basic guide for getting started with MATLAB through the MCP server |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one generates MATLAB code and the other executes it. There is no ambiguity or overlap in their purposes.
Both tool names follow the same verb_noun pattern: generate_matlab_code and execute_matlab_code. The naming is perfectly consistent and predictable.
Two tools is on the low end and feels thin for a server, but each tool has a meaningful role. The set is coherent, yet minimal.
The core workflow of generating and executing MATLAB code is covered without dead ends. Some auxiliary capabilities like persistent workspace management or file I/O are missing, but agents can likely work around these with generated code.