Altium MCP server status
get_server_statusInspect the MCP-Altium bridge setup to verify installation paths and diagnostics before running other tools. Start a session or troubleshoot after path/install errors.
Instructions
Purpose: Inspect MCP + Altium bridge setup before other tools.
When to use: First call in a session, or after MCP/Altium install or path errors.
Parameters: None.
Returns: JSON with platform, workspaceRoot, requestPath, responsePath, scriptProjectPath, altiumExePath, altiumExeFound, scriptProjectFound, bundledScriptsDir, bridgeLastError (contents of bridge_last_error.txt if present), bridgeUserReportedError (user-pasted Altium Messages / compile text from bridge_user_reported_error.txt), diagnosticsHint, env (ALTIUM_MCP_WORKSPACE, ALTIUM_MCP_ALTIUM_EXE).
Prerequisites: None. Triggers script bundle sync into workspace/AltiumScript.
How to interpret: If altiumExeFound or scriptProjectFound is false, fix paths (configure_altium_exe or env) before live tools. For DelphiScript compile errors Altium does not send to the bridge: paste the Messages output into workspace bridge_user_reported_error.txt, then re-run get_server_status so the agent can read it. Failed bridge runs also write bridge_last_error.txt and live tools append that file into the error field when success is false.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_server_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||