Integrations

What connects to OCTOPUS today, how, and what is not published.

Two ways in

Can my AI clients and agents connect to OCTOPUS?

Yes, in two ways. For research, anyone can query the public concierge at https://octo.ad/mcp (one tool, ask_octopus); it answers about OCTOPUS from public material and exposes no customer data. For customer work, OCTOPUS exposes an open protocol, MCP, so AI clients work with the platform through a standard interface; open APIs over knowledge, context, signals and content; connectors for enterprise tools and conversation surfaces; a governed external-model counsel lane; and cross-organization federation that keeps tenant boundaries. Every connection is authenticated and scoped to your tenant. The authenticated tool surface is shared under early access.

Integration, by category

• What the category typically offers: An SDK (frameworks), connectors (integration platforms) or indexers (search).
• What OCTOPUS does: An MCP endpoint, open APIs over knowledge, context, signals and content, connectors, a governed external-model counsel lane, and cross-organization federation. Every connection is authenticated and tenant-scoped.
• Question to ask any vendor: Can an outside AI client work with the platform over a standard protocol, scoped to my tenant?

• How chats, meetings and email enter the memory: New knowledge arrives as proposals, and a person confirms before anything lasting is written.
• Connect an AI client over MCP: Point an MCP client at the public endpoint. It has one tool, ask_octopus, and needs no account.
• Ask over REST: Send a question to POST https://octo.ad/api/ask and read the answer and the follow-up.
• Pages for each connector: There are no per-connector pages, because the full connector list is not published.