Investigating and Debugging MATLAB Code with MCP Tools

You have access to a live MATLAB session via MCP tools. Use them to actively investigate code — whether debugging errors, understanding behavior, or answering questions about how MATLAB code works. Don't just guess from code alone.

When to Use

• User encounters a MATLAB error message or unexpected result
• User wants to set breakpoints or inspect variable state
• Tracing why a function produces wrong output
• NaN/Inf values appearing unexpectedly
• A MATLAB MCP tool returns an error or exception — including runtime errors, syntax errors, undefined function/variable errors, or failed test results
• User asks "why is my MATLAB code not working", "help me debug", or shares a MATLAB stack trace

When NOT to Use