• English

      • Connectors: Extend Agents with Built-in Apps and MCP

      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.

      Connectors

      Connectors

      Built-in connectors

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

      ConnectorWhat it provides
      Tencent DocsRead and write Tencent Docs, smart sheets, and workspace files
      Tencent IMARead, write, search, and manage notes and knowledge bases
      Tencent MeetingMeeting management, lookup, recording, and AI minutes
      Tencent NewsNews search and topic subscriptions
      WeReadBookshelf sync and reading notes
      Tencent LexiangKnowledge base search, reading, authoring, and document management
      Tencent WeiyunOfficial MCP — file listing, upload, download, sharing, and management
      Personal mailboxConnect QQ Mail, NetEase Mail, Gmail, and others over IMAP/SMTP
      QQ MusicSong search, charts, playlists, and listening reports
      FliggyFlight, hotel, attraction, and itinerary search
      Baidu MapsPlace search, route planning, and weather lookup
      Ctrip WendaoHotel, flight, and itinerary Q&A
      Meituan travel assistantHotels, flights, train tickets, attractions, and itinerary Q&A
      YuandianLaws and regulations, case documents, company data, and legal hallucination checks
      Youdao Cloud NotesOfficial MCP — note creation, search, organisation, and management
      NotionOfficial MCP — search and read/write pages and databases
      Feishu CLIDrive docs, Bitable, calendar, and messages via the official lark-cli (requires the CLI on the host)
      WeCom CLIDrive docs, schedules, and messages via the official wecom-cli (requires the CLI on the host)
      Tencent ArdotOfficial MCP OAuth (https://ardot.tencent.com/mcp)
      Dida365 (TickTick)Tasks over official MCP OAuth (https://mcp.dida365.com)
      WeKnoraPrivate knowledge-base search and document reading through a WeKnora service
      DifyPublished Dify apps or workflows exposed through a Dify MCP Server URL
      DidiDidi MCP tools after you paste a personal MCP key from the developer console

      Connect a built-in connector

      Open Connectors

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

      Pick a service

      Find the connector you want and click Connect.

      Authorise access

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

      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.

      WARNING

      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:

      TypeWhen to use
      HTTP serverThe MCP server is reachable over a URL (for example streamable_http)
      Stdio serverThe MCP server runs as a local process that Octop launches
      NOTE

      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.

      For streamable HTTP custom MCP servers, Octop can also complete OAuth when the server exposes standard protected-resource metadata. Save the server first, run Probe connection, then follow One-click OAuth if the probe says authorization is required. Non-loopback OAuth callbacks must use a public HTTPS Octop URL.

      Turn on Selected by default in chat when you want Octop to include that custom MCP server automatically in Dashboard, IM, and cron runs that do not make an explicit connector selection. Leave it off when you prefer to choose the server per chat turn.

      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.