Connectors: Extend Agents with Built-in Apps and MCP

Octop ships built-in connectors for docs, cloud drives, mailboxes, and MCP OAuth apps, plus custom MCP servers over HTTP or stdio.

Connectors give your agents access to external services and tools. Octop groups them into built-in connectors — ready-made integrations you authorise once — and custom connectors, which are MCP servers you point Octop at yourself. You can create multiple instances of the same connector and share an instance with other people on this instance. During a conversation you pick which instances the agent may use.

​

Built-in connectors

Octop ships built-in connectors (including catalog-driven MCP OAuth):

Connector	What it provides
Tencent Docs	Read and write Tencent Docs, smart sheets, and workspace files
Tencent IMA	Read, write, search, and manage notes and knowledge bases
Tencent Meeting	Meeting management, lookup, recording, and AI minutes
Tencent News	News search and topic subscriptions
WeRead	Bookshelf sync and reading notes
Tencent Lexiang	Knowledge base search, reading, authoring, and document management
Tencent Weiyun	Official MCP — file listing, upload, download, sharing, and management
Personal mailbox	Connect QQ Mail, NetEase Mail, Gmail, and others over IMAP/SMTP
QQ Music	Song search, charts, playlists, and listening reports
Fliggy	Flight, hotel, attraction, and itinerary search
Baidu Maps	Place search, route planning, and weather lookup
Ctrip Wendao	Hotel, flight, and itinerary Q&A
Meituan travel assistant	Hotels, flights, train tickets, attractions, and itinerary Q&A
Yuandian	Laws and regulations, case documents, company data, and legal hallucination checks
Youdao Cloud Notes	Official MCP — note creation, search, organisation, and management
Notion	Official MCP — search and read/write pages and databases
Feishu CLI	Drive docs, Bitable, calendar, and messages via the official lark-cli (requires the CLI on the host)
WeCom CLI	Drive docs, schedules, and messages via the official wecom-cli (requires the CLI on the host)
Tencent Ardot	Official MCP OAuth (https://ardot.tencent.com/mcp)
Dida365 (TickTick)	Tasks over official MCP OAuth (https://mcp.dida365.com)
WeKnora	Read-only search and document reading against a private WeKnora knowledge base
Dify	Connect a published Dify app or workflow MCP server
Didi	Didi MCP tools after you paste a personal MCP key from the developer console

​

Connect a built-in connector

1. Open Connectors

   Navigate to Connectors in the sidebar and stay on the Built-in connectors tab.

2. Pick a service

   Find the connector you want and click Connect.

3. Authorise access

   Complete the authorisation flow. Octop stores the resulting token under ~/.octop/secrets/ — it never leaves your machine.

4. Select it in chat

   In a conversation, tick the connector instances the agent should be able to use. Shared instances appear for everyone who can see them.

Revoking authorisation from the external service invalidates the stored token. The agent reports a tool error the next time it tries to use that connector. Re-authorise from the Connectors page to restore access.

​

Custom connectors (MCP)

The Model Context Protocol (MCP) is an open standard for connecting AI agents to external tool servers. Under Connectors → Custom connectors you can register any MCP-compatible server, either through the visual editor or by pasting JSON:

{
  "deepwiki": {
    "display_name": "DeepWiki",
    "url": "https://mcp.deepwiki.com/mcp",
    "transport": "streamable_http"
  }
}

Two server types are supported:

Type	When to use
HTTP server	The MCP server is reachable over a URL (for example streamable_http)
Stdio server	The MCP server runs as a local process that Octop launches

A stdio server must be installed on the machine running octop run, and an HTTP server must be reachable from it. Custom MCP over public HTTPS can use OAuth: Octop discovers the authorization server (401 / RFC 9728), requires dynamic client registration, stores encrypted tokens, and injects Authorization: Bearer when loading tools. Loopback MCP URLs skip remote OAuth discovery.

​

How connectors appear to an agent

From the agent’s perspective, every active connector — built-in or MCP — is simply a tool available during a conversation. When you ask the agent to do something that needs an external service, it picks the appropriate tool, calls it, and folds the result into its reply. You do not need to invoke tools manually.

​

Next steps

Agents

Learn how to create and configure the agents that use your connectors.

Overview

See how connectors fit into Octop’s overall single-process architecture.