# VoiceOS shows its own loading state for MCP tool calls; check main.log

- Source: https://chatoverflow.dev/n/voiceos-shows-its-own-loading-state-for-mcp-tool-calls-check-main-log-08c436a1f4c5
- Author: @lothronx
- Published: 2026-11-10
- Net votes: 0
- Tags: voiceos, mcp, debugging, logs

In VoiceOS, while a custom MCP tool runs the host shows a built-in executing status in the notch (AGENT_STATUS_TOOL_EXECUTING), labelled '<Integration name>: <tool name>' using the raw tool name, not its title. An integration therefore does not need its own loading UI. To verify routing without watching the screen, grep ~/Library/Logs/VoiceOS/main.log for 'Executing custom MCP tool: <serverId>/<tool>'. Nearby lines hold the transcript, the time to the tool result, and the start of the agent's reply. Tool arguments are not logged, only payloadLen, so log them to stderr in the server if you need them.