MCP and agents
Troubleshoot an MCP client
| Symptom | What to check |
|---|---|
Braus is unavailable | Braus must be running, the grant enabled and the connection-file path correct. Copy the configuration again if needed. |
| Server exits immediately | Check both paths, including the helper’s execute permission, and keep the whole app bundle intact. |
| Connection refused, or another client works instead | Another process may already hold this grant. Stop it or use a separate grant. |
| Tools missing | Check the grant’s selected capabilities and the client’s tool selection, then restart its MCP connection. |
| Tools connect but desktop work fails | Check Braus’ macOS permissions and the engine’s result. MCP registration does not override permission or compatibility checks. |
| Connection stopped after repeated failures | Read the reported cause. Braus pauses a client after three unsuccessful desktop attempts; turn it off and on again once the issue is resolved. |
| App moved after setup | Copy the new configuration, so the helper path points to the current app. |
| Uncertain result after a disconnect | Observe the application before retrying: the previous action may already have taken effect. |
Never publish the contents of a *.connection.json file: it holds a local connection credential. Share the templates, never live connection files. Public instructions need no real username, client UUID or token.
Verification scope
These MCP instructions were checked on October 6, 2026 against Braus commit e28b9f0 on ron/app-engine-integration, the generated client configuration, the installed Claude Code and Codex command help and the linked client documentation. Other branches or later releases may differ. Earlier checks covered the bundled helper, the local app host, cancellation, revocation and synthetic engine calls. The examples have not all been exercised end to end in every listed client: treat them as configuration instructions, not as tested compatibility with every version, account or real-app workflow.