MCP reference
Quick lookup for what Cubeo's MCP integration supports, what it costs, and what to expect when something goes wrong.
Supported transport
- Streamable HTTP — the modern MCP transport (
/mcpendpoint). - HTTP + SSE — accepted as a fallback for servers that still use the
legacy event-stream framing (
/sseendpoint). - Stdio / local processes — not supported. MCP servers must be reachable over the network.
Supported authentication modes
The connect wizard auto-detects which one applies; you only see fields you need to fill in.
| Mode | What it is | What you provide |
|---|---|---|
| No authentication | Public servers. | Nothing. |
| Bearer token | A static API token in the Authorization header. | The token, once. |
| OAuth 2.1 (auto-register) | Server supports Dynamic Client Registration. Cubeo registers itself per team. | Just consent in the OAuth tab. |
| OAuth 2.1 (shared vendor app) | An admin curated this integration for the whole platform. | Nothing — it's already set up. |
| OAuth 2.1 (your own OAuth app) | The provider needs per-team OAuth credentials you create. | Client ID and Client Secret from the provider. |
If your server uses something else (HMAC-signed requests, mutual TLS, API key in a query string), Cubeo can't speak to it directly today — contact support.
What gets imported
When you connect a server, Cubeo imports every tool the server publishes
in its tools/list. For each one you get:
- A Cubeo tool with the upstream name and description.
- The tool's input schema translated into editable parameters with the right types (string, integer, boolean, enum, list).
- Any annotations the server advertises — Read-only, Destructive, Idempotent — surfaced as labels on the tool card.
You can rename, reword, or restrict any of these per AI Agent without touching the upstream definition.
Sync schedule
- Cubeo syncs every connected MCP server once a day to pick up upstream changes (default: 03:00 UTC, jittered across servers to avoid thundering shared providers).
- You can trigger a manual sync any time from Team → Integrations.
- A failing sync flips the server to a Sync failing state with a clear banner; remove and reconnect to restore credentials.
What changes when the upstream catalog changes
| Upstream change | What Cubeo does |
|---|---|
| Description-only change | Auto-propagated. Your AI Agent sees the new copy on the next call. |
| Inputs / behaviour changed | Recorded but held back. An admin reviews and publishes before agents pick it up — keeps in-flight conversations stable. |
| Tool removed upstream | Marked inactive on every AI Agent that used it, with reason Source tool removed. Past conversations still resolve. |
| New tool appears upstream | Available next time you reconnect or import from the server. |
Billing
| Item | Cost |
|---|---|
| Connecting an MCP server | Free. |
| Syncing the catalog | Free. |
| Each tool call from a team-connected MCP server | 2 credits per call by default. Admins can override per tool. |
| Tool calls from admin-curated MCP servers | Whatever the admin set, surfaced on the tool card. |
The default of 2 credits per call applies to MCP servers connected by your team. If your AI Agent calls the same tool many times in a batch, those credits add up — keep an eye on Analytics.
Per-call timeout
Each MCP tool call has a hard timeout. The default is 60 seconds; slow servers will return a timeout error to the AI Agent rather than hang the conversation.
What stays / what doesn't on delete
When you delete an MCP server from Team → Integrations:
- The server connection is removed.
- Stored credentials and OAuth tokens are revoked on Cubeo's side.
- Where the server supports it, Cubeo also removes the registration on the provider's side, so you don't leave orphan apps behind.
- Every tool that came from that server is removed from every AI Agent in your team.
- Past conversations that called those tools are not modified — the history stays intact and the responses inside the conversation are still readable.
The action is irreversible. Reconnecting later goes through the wizard again from scratch.
Troubleshooting matrix
| Symptom | Likely cause | What to do |
|---|---|---|
| "This URL does not appear to be an MCP server" | URL is wrong or the server isn't actually MCP. | Double-check the path. Most MCP servers expose /mcp or /sse. |
| OAuth redirect fails or returns to an error page | Provider requires pre-registering Cubeo's redirect URI. | Copy the URI shown in the connect form into your OAuth app config in the provider. |
| Sync failing banner on the connection | Credentials expired or were revoked upstream. | Click Sync to retry. If it persists, delete the connection and reconnect. |
| Tool call returns "Internal error: validation failed" | Upstream tool's inputs changed and weren't published yet, OR your AI Agent passed an unexpected field. | Wait for an admin to publish the schema change, or remove and reconnect to pick up the new shape. |
| Tool calls are slow (>60s) | Upstream MCP server is slow on this query. | Reduce the input size, or contact the upstream maintainer. |
| Some tools are missing | Server didn't publish them in tools/list, or upstream removed them. | Trigger a manual sync from Team → Integrations. |
Related
- Connect an MCP server — the connect wizard step by step.
- How MCP integration works — what happens behind the scenes.
- Integrations — manage every connection in one place.