Connectors: let an expert use your apps
A connector is an external app an expert can operate. You authorize it once. After that you do not need the tool name: say “Check my Tencent Meeting schedule for tomorrow” or “Write these notes into Tencent Docs.” The expert decides when to call it.

Connect one app you already use
Open Built-in connectors
In the sidebar, open Connectors, then Built-in connectors.
Click to connect
Pick a service and click Click to connect. You can create several instances of the same service, for example two mail accounts.
Authorize and probe
Follow the page to scan a QR code, click Authorize, or paste a secret, then click Probe. Save after the probe succeeds. Tokens stay on this machine under ~/.octop/secrets/.
Select it in Conversation and ask in plain language
Open Conversation, open Connectors in the composer, and tick the instance. Then say what you want done. To include it every time, edit the instance and turn on Enable by default. That switch applies only to your own new chats.
Turn on Share with others and other people signed in on this instance can select the instance. They cannot view or edit its configuration. Only the owner can edit it.
If you revoke access in the external service, the stored token stops working. The next call fails. Authorize again from Connectors to restore it.
Pick by the job
The groups below match the categories on the page.
Office
Notes and knowledge
Travel and maps
Mail and tasks
News and media
Professional
Self-hosted
CLI connectors need the matching command on the machine that runs octop run. The page can Install CLI, or you can hand the command to an administrator.
When the built-in list does not have it
Under Connectors → Custom connectors, register any MCP server with the visual form or by pasting JSON:
A stdio program must be installed on the machine running octop run. An HTTP URL must be reachable from that machine. Custom MCP on public HTTPS can use OAuth: Octop discovers the authorization server from the MCP URL (401 / RFC 9728), stores encrypted tokens, and sends Authorization: Bearer when it loads tools. When the server has no dynamic client registration, the probe sets oauth.client_required and you fill in a pre-registered client id. A client secret is optional and is not returned after you save. Register <public base>/api/connectors/oauth/callback as the redirect URI. Loopback and private addresses skip remote OAuth discovery. Only the person who created a shared connector can edit it.
When the server exposes standard protected-resource metadata, save first, then click Probe. If the probe says authorization is required, click Authorize. OAuth callbacks on a non-loopback address need a public HTTPS URL for this Octop.
Turn on Selected by default in chat when web UI chats, IM, and scheduled tasks that do not pick a connector should include this MCP automatically. Leave it off to choose it on each turn.
If no public server exists yet, you can run your own and register it here.

