Where to Find MatlabMCP Server Logs in Claude Desktop (macOS & Windows)

MatlabMCP server logs are captured by Claude Desktop and stored at ~/Library/Logs/Claude/mcp-server-MatlabMCP.log on macOS and %APPDATA%\Claude\logs\mcp-server-MatlabMCP.log on Windows.

The MatlabMCP server from the jigarbhoye04/matlabmcp repository streams diagnostic output to standard error, which Claude Desktop automatically redirects to its own MCP log files. Understanding these MatlabMCP server logs is essential for debugging MATLAB integration issues, monitoring tool execution, and verifying server initialization. This guide covers the exact file paths on both operating systems and how to configure logging verbosity directly in the source code.

Log File Locations on macOS and Windows

Claude Desktop aggregates MCP server output into dedicated log files based on your operating system. The MatlabMCP server specifically writes to Python's sys.stderr stream, which Claude captures and persists to disk.

macOS Log Path

On macOS, the log file resides in the user's Library Logs directory:

~/Library/Logs/Claude/mcp-server-MatlabMCP.log

To monitor this file in real-time using Terminal, run:

tail -f ~/Library/Logs/Claude/mcp-server-MatlabMCP.log

Windows Log Path

On Windows, the logs are stored in the Application Data folder:

%APPDATA%\Claude\logs\mcp-server-MatlabMCP.log

To view the log continuously in PowerShell, use:

Get-Content "$env:APPDATA\Claude\logs\mcp-server-MatlabMCP.log" -Wait

How Logging Works in the MatlabMCP Server

According to the source code in jigarbhoye04/matlabmcp, the logging configuration is defined in main.py at lines 15‑20. The server uses Python's standard logging module configured to output to sys.stderr, ensuring Claude Desktop can capture all diagnostic messages.

The initialization code sets the default level to INFO and formats timestamps, logger names, and severity levels:

import logging, sys

logging.basicConfig(
    level=logging.INFO,          # Default verbosity level

    stream=sys.stderr,
    format="%(asctime)s - %(name)s - %(levelname)s - %(message)s",
)
logger = logging.getLogger("MatlabMCP")

This configuration means all log output flows through standard error, which Claude Desktop intercepts and writes to the platform-specific files mentioned above.

Changing Log Levels for Detailed Debugging

When troubleshooting complex MATLAB integration issues, you may need more verbose output than the default INFO level provides. To enable DEBUG logging, modify the level parameter in main.py:

import logging, sys

logging.basicConfig(
    level=logging.DEBUG,          # Changed from INFO to DEBUG

    stream=sys.stderr,
    format="%(asctime)s - %(name)s - %(levelname)s - %(message)s",
)
logger = logging.getLogger("MatlabMCP")

After saving this change and restarting the MatlabMCP server in Claude Desktop, the logs will contain detailed information about tool invocations, MATLAB engine interactions, and server lifecycle events. This configuration is documented in the repository's README.md at lines 82‑84.

Viewing Logs in Real-Time

Active monitoring of MatlabMCP server logs helps diagnose issues as they occur during Claude conversations. Use the following platform-specific commands to stream log updates continuously.

macOS Terminal:

tail -f ~/Library/Logs/Claude/mcp-server-MatlabMCP.log

Windows PowerShell:

Get-Content "$env:APPDATA\Claude\logs\mcp-server-MatlabMCP.log" -Wait

Both commands display new log entries immediately as the MatlabMCP server writes them to standard error.

Summary

• MatlabMCP server logs on macOS are located at ~/Library/Logs/Claude/mcp-server-MatlabMCP.log
• Windows logs are stored at %APPDATA%\Claude\logs\mcp-server-MatlabMCP.log
• The server writes to sys.stderr as configured in main.py lines 15‑20, which Claude Desktop captures automatically
• Change the logging level from INFO to DEBUG in main.py for detailed troubleshooting
• Use tail -f on macOS or Get-Content -Wait on Windows to monitor logs in real-time

Frequently Asked Questions

Where does MatlabMCP write its log messages?

MatlabMCP writes log messages to Python's standard error stream (sys.stderr), not to a dedicated file. Claude Desktop captures this output and saves it to ~/Library/Logs/Claude/mcp-server-MatlabMCP.log on macOS or %APPDATA%\Claude\logs\mcp-server-MatlabMCP.log on Windows.

How do I enable DEBUG level logging for MatlabMCP?

Open main.py in the jigarbhoye04/matlabmcp repository and change the level parameter from logging.INFO to logging.DEBUG in the logging.basicConfig() call at lines 15‑20. Restart the server in Claude Desktop to apply the changes.

Can I view MatlabMCP logs while Claude Desktop is running?

Yes. Use tail -f ~/Library/Logs/Claude/mcp-server-MatlabMCP.log in a macOS Terminal or Get-Content "$env:APPDATA\Claude\logs\mcp-server-MatlabMCP.log" -Wait in Windows PowerShell to stream live log updates as the server processes requests.

What if the log file doesn't exist on Windows?

If the file is missing, ensure Claude Desktop has launched the MatlabMCP server at least once and that the server has generated output. The file is created when Claude first captures stderr from the server. Verify that the server path in Claude's configuration points correctly to the main.py file from the jigarbhoye04/matlabmcp repository.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}