Skip to main content

How MCP integration works

This page explains what happens behind the scenes when you connect an MCP server, so you know what to expect — especially around authentication, tool syncing, and removing a server.

What MCP brings to your AI Agent​

The Model Context Protocol is an open standard for AI tools. An MCP server publishes a list of tools, each with a description and inputs, and answers when a tool is called. Cubeo connects to that server on your AI Agent's behalf so the agent can use those tools alongside its native ones.

Concretely, this means:

  • You bring a server URL.
  • Cubeo handles authentication, the catalog, and the runtime calls.
  • Your AI Agent gets new tools — same look and feel as the built-in ones.

Connect once, use across every agent​

A connected MCP server is team-wide. You set it up once and every AI Agent in your team can pick its tools up from their Tools tab. There's no per-agent reconnect.

Every AI Agent's Tools catalog shows two flavours of MCP servers, both listed alongside the native integrations:

  • Curated by Cubeo admins — set up for the whole platform. They're ready to use without any credentials on your side.
  • Connected by your team — set up by you or a teammate from the Integrations page. Scoped to your team only.

Each agent keeps its own copy of the tools it adds, so renaming a tool or overriding a default value on one agent doesn't leak to the others.

Where MCP servers live in Cubeo​

You'll find every external connection your team uses on the Team → Integrations page: native integrations (HubSpot, LinkedIn, Tavily, etc.) and MCP servers, all in the same table.

The table shows each connection's logo / name, a tag indicating whether it's an MCP server, the number of tools it provides, when it was last synced, and quick actions (Sync, Edit, Delete).

Authentication, made simple​

Cubeo supports the four common ways MCP servers authenticate:

  • None — public servers, no credentials.
  • Static token — paste a single token once.
  • OAuth (auto-register) — Cubeo registers itself per team, no setup needed beyond consent.
  • OAuth with shared or BYO credentials — an admin curates a shared OAuth app, or each team brings their own.

You don't have to pick — the connect wizard auto-detects what the server expects and pre-selects the simplest path.

Keeping tools fresh (drift sync)​

MCP servers can update their tools at any time without notifying anyone. Cubeo runs a daily sync against every server you've connected. The behaviour depends on what changed upstream:

  • Description-only change — the new copy flows in automatically. Your agent sees it next call.
  • Inputs or behaviour changed — the new shape is recorded but your agent keeps using the old one until an admin reviews and publishes the change. This prevents an upstream break from instantly destabilising every conversation in flight.
  • A tool is removed upstream — Cubeo marks the corresponding tool in your agent as inactive, with a clear reason. Past conversations still resolve correctly.
  • A new tool appears upstream — it's available the next time you connect or reimport from the server.

You can also trigger a sync manually any time from Team → Integrations.

Calling a tool at runtime​

When the AI Agent decides to use an MCP tool, Cubeo:

  1. Picks up your team's stored authentication.
  2. Opens a short-lived session to the MCP server.
  3. Sends the tool call and reads the answer.
  4. Hands the result back to the agent in the conversation.

If the server rejects the credentials (e.g. an OAuth token has expired), Cubeo flags the connection as needing attention so you can reconnect — the agent never silently sends stale tokens.

Removing a server cleanly​

When you delete an MCP server from Team → Integrations, Cubeo:

  • Revokes any stored credentials on your side.
  • Removes the tools that server contributed to every AI Agent.
  • Where the server supports it, also cleans up the registration on the provider's side, so you don't leave orphan apps behind.

The action is irreversible — if you reconnect later, you'll go through the connect wizard again. Cubeo deliberately keeps the integrations list to "only what you intentionally connected" so you always see the current state at a glance.

Where to look in Cubeo​

  • AI Agent → Tools — Connect MCP for one specific agent and customise how each tool is exposed.
  • Team → Integrations — Every connection your team has, with sync / delete actions and the Connect MCP server CTA.