Custom connectors

Custom connectors let you plug your own MCP servers into BusyBro — the same idea as adding a connector in a consumer AI chat app. Paste a server's URL, pick which of its tools to expose, and those tools become available to BusyBro in your chats only. Connectors are private to your account, so you can wire BusyBro up to the tools you already use without affecting anyone else on the team.

This is different from the admin-managed MCP servers list (the fleet-wide connections an operator configures for everyone — see What it can do). A custom connector is yours: only you see it, only your turns can call it.

Where to manage them

You can add and manage your connectors from either surface — they're the same connectors, backed by your one account:

On busymate.ai — open Settings, then the Your connectors card, and choose Manage connectors.
In the dashboard — open Settings → BusyBro and find the My connectors panel.

Both mount the same wizard and the same management dialog, so it doesn't matter where you start.

Add a connector

Adding a connector is a short three-step wizard. Nothing is saved until the final step.

Paste the server URL. Enter the server's https:// MCP endpoint. BusyBro runs a quick server-side check: it validates the address is a public HTTPS host, opens an MCP handshake, and previews the tools the server advertises — all without storing anything yet. If the server needs authentication or can't be reached, you'll see the honest reason and can continue anyway.
Give it a name and a tool prefix, and pick authentication. The name is just a label. The tool prefix (namespace) is how the server's tools appear to BusyBro — a server with the prefix notion exposes notion__search, notion__create_page, and so on, so its tools never collide with BusyBro's built-ins or another connector's. Then choose how BusyBro authenticates: No authentication for an open server, or API token to paste a credential the server gave you. (OAuth is coming soon — see below.)
Review the tools and add it. The wizard lists the tools the server advertises; leave them all on, or narrow the selection so BusyBro only ever sees the ones you want. Select Add connector and it's live.

Note: If BusyBro couldn't preview the tools during step 1 (for example, the server only answers authenticated requests), you can still add the connector. BusyBro fetches the tool list the first time it actually connects on one of your chats.

Authentication

Option	What it means
No authentication	The server is open — no credential is sent.
API token	You paste a Bearer token the server issued to you. It's stored encrypted and write-only — once saved it's never shown again, only replaced.
OAuth	Coming soon. Signing in to a server with your account (rather than pasting a token) isn't available yet; the option is visible but disabled.

When you use an API token, the connector stores only the token's location in the encrypted secret store — the token value itself never appears in the connector's details, in a tool-call preview, or anywhere else you can read it back. To change it, paste a new one; there's no "reveal".

How BusyBro sees the tools

Every connector's tools are advertised to BusyBro under its prefix as <prefix>__<tool>. You don't call these by name — you just describe what you want in plain language, and BusyBro maps your request to the right tool, exactly as it does with its built-in capabilities. The prefix keeps each connector's tools cleanly separated in the tool list.

How connectors stay safe

Connecting an outside server is powerful, so a few guardrails always apply:

Confirmation before anything changes. BusyBro treats a connector's tools as untrusted by default. A tool the server itself marks read-only can run freely, but any tool that could change something prompts you with a confirm card showing which connector is being called, which tool, and with what arguments — with credential-shaped values masked — before it runs. Nothing external happens on your behalf without that explicit tap.
Private to you. A connector is scoped to your account. BusyBro only ever advertises and calls your connectors on your turns; no one else's chats can see or use them.
Your token is write-only. As above, a stored API token is encrypted and can never be read back on any surface.
Only public HTTPS servers. BusyBro refuses non-HTTPS URLs and blocks internal, loopback, private-network, and cloud-metadata addresses — both when you add the connector and every time it connects — so a connector can't be pointed at something behind your network.

Note: The confirm card is shown on the web surfaces (the busymate.ai chat and the dashboard chat panel). On Telegram, iPhone, and the bmc CLI, BusyBro doesn't yet render an external-tool confirm card, so it will honestly tell you it can't run a change-making connector tool there rather than running it unconfirmed. Read-only connector tools work everywhere.

Manage, disable, or remove

Open any connector to inspect it. From its details dialog you can:

Check the connection — re-run the handshake on demand to confirm the server is reachable and see how many tools it advertises, along with the last connection status or error.
Adjust which tools are exposed — change the tool selection at any time.
Rotate the token — store a fresh API token (write-only, as above).
Disable it — a kill-switch that keeps the connector but stops advertising its tools to BusyBro. Flip it back on whenever you like.
Remove it — deletes the connector and its stored credential. This can't be undone.

Manage them programmatically

Everything the wizard and dialog do is also available as MCP tools, so you can manage your connectors from any MCP client or by asking BusyBro:

Tool	What it does
`list_my_mcp_connectors`	List your own connectors (metadata only — never a token value).
`probe_mcp_connector`	Paste a URL and preview what an MCP client would see, without saving anything.
`upsert_my_mcp_connector`	Create or update a connector (owner pinned to you server-side).
`set_my_mcp_connector_secret`	Store a connector's API token (write-only).
`set_my_mcp_connector_enabled`	Enable or disable a connector.
`delete_my_mcp_connector`	Remove a connector and its credential.

Reads need users:view; the writes need users:edit and a confirmation. The token-setting tool is deliberately kept out of BusyBro's free-text control (it writes a raw credential), so a token is only ever set by you, through the UI or an explicit tool call. The full schemas live in the MCP server tools list.