Skip to main content

Bring your own tool: connecting a custom integration via MCP

If the app or service you need isn't in Octonous's built-in integrations, you can connect it yourself using MCP.

Octonous ships with integrations for 25 apps out of the box. But if you use an internal tool, a niche API, or anything that isn't on that list, you can connect it yourself via MCP. Once connected, Octonous can call your custom tool the same way it calls any other integration.

What is MCP?

MCP is an open protocol for exposing tools to AI agents. If a service exposes an MCP server over HTTP, Octonous can discover its tools automatically and make them available in the chat and in automations.

Your MCP server needs to use the Streamable HTTP transport (the standard for remote MCP servers). Local stdio-based servers are not supported.

Before you start

You'll need:

  • The URL of your MCP server (a public or network-accessible HTTPS endpoint)

  • Any authentication headers the server requires (typically a Bearer token or API key)

How to connect an MCP server

  1. Go to App Connections in the sidebar.

  2. Click Bring your own tools.

  3. Give it a name. This is how it will appear in the tool picker and in automations.

  4. Paste in the server URL.

  5. If your server requires authentication, add the auth header (for example, Authorization: Bearer your-token). Auth headers are encrypted at rest and never exposed in the UI after saving.

  6. Click Connect. Octonous will probe the server, discover the tools it exposes, and save the connection.

Once connected, the server's tools appear in the chat composer and in the automation tool picker under the name you gave it.

Tool discovery

When you connect an MCP server, Octonous fetches the list of tools it exposes and caches their names. If you update your server and add or remove tools, click Refresh on the connection in App Connections to pull the latest list.

Limits

You can connect up to 20 personal MCP servers. In a workspace context, the limit is 50 servers per workspace.

Personal vs. workspace MCP servers

MCP servers can be personal or shared across a workspace.

  • Personal servers are only visible to you. They appear in your personal chat and automations.

  • Workspace servers are connected by a workspace Owner and are available to every member of the workspace, unless access has been restricted for specific members via the workspace Permissions tab.

Disconnecting an MCP server

Go to App Connections, find the server, and click Disconnect. This removes the connection and all associated credentials. Any automations that were using this server's tools will need to be updated.

A note on security

Auth headers are stored encrypted using the same KMS envelope encryption used for OAuth tokens. The raw header values are never logged or displayed after the initial save. Make sure the server URL uses HTTPS.

Using a different authentication method? Contact us (in Octonous Help panel) and we'll help you get connected.

Did this answer your question?