English

Português

English

Português

Appearance

MCP Connections ​

An MCP connection is a reusable MCP server of the project: the address, the credential and the tool cache are stored once and can be used by several agents. It is the right place for OAuth servers, which require browser authorization, and for avoiding the same configuration repeated in every agent.

If you want to use SIPPulse AI from inside another MCP client, see Remote MCP. Here the direction is the opposite: your agents consuming external MCP servers.

What an MCP connection is ​

A connection belongs to the active project. Created without an active project, it is available to the whole organization. Each connection stores:

FieldWhat it is
NameHow the connection appears in the list and in agents
URLThe server MCP endpoint
TransportNegotiated automatically (Streamable HTTP with HTTP+SSE fallback)
AuthenticationNo credential, headers with secret references, or OAuth 2.1
Tool cacheThe tools discovered in the last Connect, Test or Sync

In the headers you reference project secrets with the {{$SECRET_NAME}} syntax; the actual value is resolved in memory only at call time. See the Secrets Vault.

Creating and connecting ​

The modal follows the "give a URL and click Connect" model:

  1. Open Settings > MCP connections and click Create connection.
  2. Enter the URL. The Name is optional: if left empty, the platform uses the name reported by the server itself.
  3. If the server requires header authentication, open Headers (optional) and add the secret references.
  4. Click Connect. The platform negotiates the transport, discovers the tools and, if the server asks for a credential, opens the provider authorization page in a popup.

The transport is decided automatically: the default tries Streamable HTTP and falls back to HTTP+SSE when the server does not accept the first one. You do not choose it.

Connection status ​

The status badge says whether the credential exists and how the last check went:

BadgeMeaning
ConnectedThe credential exists and the last check succeeded
Not connectedThere is no credential yet, or the server was never checked
Needs re-authenticationThe server rejected the credential; reconnect
ErrorThe last check failed; the detail appears on the row

Connection actions ​

ActionWhat it does
ConnectOpens the provider authorization page in a popup and stores the credential
Re-authenticateRepeats the OAuth authorization of an already authorized connection
RevokeDrops the local credential; the connection goes back to unconfigured
Sync toolsRefreshes the server tool cache
TestConnects, discovers the tools and updates the status and the cache
EditChanges name, URL and headers. Changing the URL or credentials requires reconnecting
DeleteRemoves the connection. Blocked while one or more agents reference it

When you try to delete a connection in use, the platform answers: "This MCP connection is used by one or more agents. Remove it from them first."

The tool cache only changes through an explicit action: Sync, Test, Connect or saving the agent. It does not expire on its own.

Using in agents ​

In the agent MCP Servers modal:

  1. Enter name, URL, transport (auto by default) and headers, or pick an existing connection in the or use an existing connection selector.
  2. Click Connect to discover the tools.
  3. Toggle individual tools on or off. The allowlist lives in the agent: a new tool discovered on the connection is not enabled by itself in the agents that use it.
  4. Click Save.

Inline server entries, without a connection, keep working for those who already have them. Connecting an inline entry turns it into a connection.

When the provider revokes the token ​

If the provider revokes the credential, the connection becomes Needs re-authentication. During a run the agent never opens a browser: the tool answers with the mcp_auth_required error and the conversation continues. Reconnecting the connection makes it work again.

Sharing between agents ​

One connection can be used by several agents at the same time. Rotating the credential applies to all of them, because they all use the same connection. When the URL or the credentials change, stale sessions are dropped and the platform asks for a reconnect.

Security ​

OAuth credentials are encrypted and never returned by the API. The {{$SECRET_NAME}} references are resolved in memory only, at call time, and the persisted configuration keeps only the placeholder.