MCP Bridge

MiniBot can discover and expose remote Model Context Protocol tools as local tool bindings at startup.

Note

Requires the mcp extra:

poetry install --extras mcp

Tool Naming

For each configured server, MiniBot calls tools/list and exposes tool names as:

<name_prefix>_<server_name>__<remote_tool_name>

Example: prefix mcp, server dice_cli, remote tool roll_dice → mcp_dice_cli__roll_dice.

Configuration

[tools.mcp]
enabled = true
name_prefix = "mcp"
timeout_seconds = 10

Stdio transport example:

[[tools.mcp.servers]]
name = "dice_cli"
transport = "stdio"
command = "python"
args = ["tests/fixtures/mcp/stdio_dice_server.py"]
env = {}
cwd = "."

HTTP transport example:

[[tools.mcp.servers]]
name = "dice_http"
transport = "http"
url = "http://127.0.0.1:8765/mcp"
headers = {}

Playwright MCP example (requires Node.js / npx on the host):

[[tools.mcp.servers]]
name = "playwright-cli"
transport = "stdio"
command = "npx"
args = [
  "@playwright/mcp@0.0.64",
  "--headless",
  "--browser=chromium",
  "--caps=vision,pdf,network",
  "--block-service-workers",
  "--image-responses=omit",
  "--snapshot-mode=incremental",
  "--timeout-action=2000",
  "--timeout-navigation=8000",
]
cwd = "."

For server name playwright-cli, MiniBot injects --output-dir automatically from [tools.browser].output_dir.

Tool Filtering

• enabled_tools — if empty, all discovered tools are allowed; if set, only listed remote tool names are exposed.

• disabled_tools — always excluded, even if also present in enabled_tools.

Troubleshooting

• If discovery fails, startup logs include failed to load mcp tools with the server name.

• If the main agent answers without using tools (common with some OpenRouter models), set [orchestration].main_tool_use_guardrail = "llm_classifier" to enforce a tool-routing classification step before each final answer.