MCP

BotConnector is an MCP host: register MCP servers, list their tools, and expose allowlisted tools to local models through tool calling. Server configuration is persisted by the application.

What is implemented

Persistence, explicit tool allowlists, permission modes, safe stdio lifecycle, timeouts and isolated failures — each covered by acceptance tests. It is a local preview: the packaged UI and supported server set can vary by build.

Design principles

• Explicit allowlists — a tool does nothing until you allow it.
• Auditable — every registered server and invocation is logged.
• Least privilege — read/search defaults; write/execute requires opt-in.

Setup guides

• Configure MCP — registering stdio servers
• MCP permissions — allowlists and consent
• MCP troubleshooting

Full details: MCP docs. Tool calling on the Hosted API is available; the local runtime path is Experimental — model compatibility varies (tool use). Status: status page.