Skip to main content

Settings: MCP

MCP, the Model Context Protocol, lets Row-Bot use tools provided by another local or remote server. Treat MCP servers like extensions: only connect servers you trust and understand.

Settings: MCP in Row-Bot.
The MCP tab manages external MCP tool servers, global enablement, per-server settings, tests, imports, and diagnostics.

Where To Find It​

Open Settings, then choose MCP from the left tab list.

Controls​

  • Enable MCP is the global on/off switch for external MCP tools.
  • Add Server opens fields for name, transport, command, arguments, or URL.
  • Import Config accepts a server configuration from another source.
  • Browse MCP Servers searches directories for server candidates.
  • Diagnostics opens a health view for troubleshooting.
  • Per-server enablement decides whether a configured server can provide tools.
  • Test checks a server before you rely on it.
  • Edit, refresh, and delete manage saved server definitions.
  • Approval and advanced options decide how MCP tools interact with Row-Bot's safety policy.

Common Workflow​

  1. Leave MCP disabled until at least one trusted server is configured.
  2. Add or import a server, then save it disabled first if you are unsure.
  3. Test the server and inspect the available tools.
  4. Enable the server only when you are comfortable with what those tools can access.

What Is Saved​

MCP server definitions are local settings. A server may still access files, accounts, or networks according to its own implementation, so review its command or URL.

Privacy And Safety​

Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services. Local-only features stay on your machine until you ask Row-Bot to use a provider, account, channel, MCP server, plugin, or tool that sends data elsewhere.

Control-Level Reference​

The generated Settings Controls reference lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations.

Troubleshooting​

  • If a server test fails, check command, arguments, URL, and local dependencies.
  • If tools do not appear in Chat, confirm the global and server toggles are both enabled.
  • If a tool asks for risky access, reject the approval and inspect the server config.