Add a custom MCP server
Use this for a remote server outside the integration catalog. Its endpoint must support SSE or Streamable HTTP.
Connect
Section titled “Connect”Open Integrations in the workspace or project that should own the server. Choose Custom MCP server.
The Registration scope notice shows where the server will be available. A project registration is available to that project only.
Paste the Server URL, add an optional Label, then choose Connect. Flow XO checks how the server signs in.
If automatic detection can’t identify its authentication, the form lets you choose it. Use None only when the server doesn’t require authentication. Choose Add server to save the registration.
Check the connection
Section titled “Check the connection”Find the server’s card by its label. Open it and choose Open explorer. Overview shows the URL, authentication, scope and status. Tools lists the discovered tools. Expand Input schema to see the values a tool accepts.
Choose Refresh tool catalog in the server details after its tools change. Check the refreshed list before changing your agent.
Connecting a server and selecting its tools for an agent are separate steps. Review Choose tools before publishing.
Edit the server
Section titled “Edit the server”Open the server’s details and choose Edit MCP server. Review its URL, then change the Label or Authentication and choose Save. The URL is fixed for this registration. Connect a new server to use a different endpoint.
A public server with None selected doesn’t ask for a key. For a server that uses a stored key, leave Secret value blank to keep it, or enter a replacement. A label-only edit keeps an existing OAuth connection.
Disconnect
Section titled “Disconnect”Choose Move to trash in the server details. Read the confirmation before continuing. It names the server and explains that archiving disconnects it from Blueprints. The server can be restored from Settings → Trash.