Connect MCP tools

Remie, the AI assistant, can use tools from external MCP servers you connect, on top of SenditCold's built-in ones. Connect your own server or a third-party one, review the tools it offers, and enable it. From then on Remie can call those tools, always asking you first.

Connections live under Settings, Connections and require the Manage settings permission.

Connecting a server

Press Add server and provide:

• Name: how the connection appears, and part of each tool's name in Remie.
• Server URL: an https URL to a streamable-HTTP MCP endpoint. Only public https URLs are allowed; internal or private addresses are rejected. A self-hosted instance can allow a server on its own network (an http:// URL or a private address) by setting WARMBLY_ALLOW_UNSAFE_WEBHOOK_URLS=true on the backend; see configuration.
• Authentication: None, or a Bearer token. A bearer token is stored encrypted with your workspace key and is never shown again or returned by the API.

When you connect, SenditCold reaches out to the server, runs the MCP handshake, and lists the tools it offers. The connection starts disabled so nothing is exposed to Remie until you have looked at the tools.

Reviewing and enabling

Each connected server shows the tools SenditCold discovered. Read them, and when you are comfortable, flip the toggle to enable the server. Only enabled servers' tools reach Remie, which finds them on demand by searching, so a server with many tools never crowds out the rest.

If the server could not be reached, the connection shows the error instead of a tool list. Fix the URL or token and press the refresh icon to try discovery again. Refresh also picks up any new tools a server has added.

How Remie uses external tools

External tools behave like SenditCold's own write actions with one important difference: they are always approval-gated when Remie calls them by name. Remie can never call an external tool automatically, even when a settings manager has chosen "Always allow" for built-in actions. Every such call shows you what it will do and waits for your approval. The one exception is a tool you picked as the workspace's web search, which receives only a search query.

Each tool appears in Remie namespaced by your connection, so it is always clear which server a tool belongs to.

Use a tool as your web search

A search tool on a connected server can be the workspace's web search, for example search_text on the DDGS MCP server, or any tool that takes a search query. Open the server's card, pick the tool under Web search, and keep the server enabled. SenditCold offers only tools whose arguments it can fill in: one that takes the query (query, q, search and similar names, or its only required text argument) and, optionally, a result count.

Once picked, the tool runs without asking, because it only ever receives a search query:

• the lead finder searches with it for a missing website, or for the addresses a site it could not read shows elsewhere, before any search the instance charges for
• Remie's built-in search_web uses it when the instance has no web search configured

SenditCold reads back the links, titles and text the tool returns, as JSON in any of the usual shapes or as plain text. Clear the setting to stop. Refreshing a server whose tool has gone, or no longer takes a query, clears it too.

Removing a connection

Disconnect a server any time from its card. Its tools are removed from Remie immediately, and the stored credentials are deleted.