Skip to main content

MCP

MCP lets Row-Bot use tools exposed by external Model Context Protocol servers. An MCP server can be local or remote, simple or powerful. Treat it like an extension with its own access and trust boundary.

Row-Bot MCP settings.
MCP settings manage global enablement, server rows, add/import/browse actions, tests, diagnostics, and per-server controls.
Row-Bot Browse MCP Servers marketplace with bundled starter servers.
Browse starts with the bundled starter catalogue and exposes publisher, transport, overlap, authentication, and risk labels before import.
Row-Bot Add MCP Server dialog.
Manual server configuration starts disabled so you can review transport, command or URL, environment, and tool risk before testing.

Setup Workflow​

  1. Open Settings -> MCP.
  2. Leave Enable MCP off until a trusted server is configured.
  3. Add, import, or browse for a server.
  4. Review the command, arguments, URL, transport, and expected tools.
  5. Save disabled first if you are unsure.
  6. Test the server.
  7. Enable the server only after you understand what it can access.

Controls​

  • Enable MCP turns all external MCP tools on or off.
  • Add Server opens the manual server form.
  • Import Config imports server definitions from configuration text.
  • Browse MCP Servers searches available server directories.
  • Diagnostics helps explain connection failures.
  • Per-server enablement decides whether a saved server contributes tools.
  • Test, refresh, edit, delete manage the server row.

Safety​

MCP tools can read, write, call APIs, or automate services depending on the server. Row-Bot approvals still matter, but you should also trust the server itself before enabling it.

Troubleshooting​

  • If a server fails to test, check transport, command, arguments, URL, and dependencies.
  • If tools are missing, enable both the global MCP switch and the server.
  • If a prompt asks for unexpected access, reject it and inspect the server configuration.