Configure MCP

Beta

Configure in the desktop app

Open the MCP management surface in BotConnector, add a server, choose stdio, and enter the executable plus argument list. The persisted shape is equivalent to:

json

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "D:\\projects"],
      "allowedTools": ["list_directory", "read_file", "search_files"]
    }
  }
}

The allowedTools list is the permission boundary — tools not listed stay hidden from the model.

Local vs remote MCP servers

Transport	Use	Security notes
stdio (local)	Command on your machine	Runs with your user's rights — allowlist narrowly
HTTP/SSE (remote)	Shared/team server	Authenticate; treat as third-party surface

The application starts the configured process with shell:false, performs the MCP initialize handshake, lists tools, and exposes only entries in allowedTools. There is no supported botconnector mcp ... command family in this release; do not copy undocumented commands into production scripts.

Scope notes

Each server runs as a separate process; a crash is contained.
Environment variables passed to MCP servers are explicit, never inherited wholesale.
Disabled servers, malformed commands, timeouts and crashed processes fail closed and do not block unrelated local chat.
See MCP permissions before enabling anything with write access.