BotConnector
ID

MCP troubleshooting

MCP: stable · public · verified

The checklist below assumes you have run bccli mcp add <name> and are checking the server from bccli mcp list.

Server does not start

  • Check the command exists (npx/binary on PATH).
  • Read the server's stderr in BotConnector logs.
  • stdio servers need the exact command + args as a list, not a shell string.

Tools not visible to the model

  1. Refresh the server in the MCP management surface and confirm its tools list.
  2. The tool must be in allowedTools — see MCP permissions.
  3. The loaded model must support tool calling — Tool use.

Calls fail at runtime

  • Timeout: MCP servers are separate processes; a hung tool blocks the call — check process state.
  • Permission denied: the tool is registered but not allowlisted (intended behavior).
  • Malformed arguments: the model produced JSON that fails the tool's schema; try a more capable model or quantization.

Security incident response

  1. Disable or remove the server, or remove the tool from its allowlist, immediately.
  2. Review logs for the affected window.
  3. Rotate any credentials the exposed tools could read.