Connecting MCP servers

Named servers

The Connectors page lists these servers by name. UFO already has their server addresses, so you only need to enter an API key.

Server	Token to enter
Neon	Neon API key
Render	Render API key

Servers that use OAuth are not listed here. If the provider has a connector on the Connectors page, use that connector.

Prepare another server

For a server that is not listed, you need:

• A short name for the server.
• Its HTTP or HTTPS Streamable HTTP endpoint.
• An optional bearer token.

The endpoint must be reachable from UFO. Local stdio servers are not supported by a hosted workspace.

Connect an MCP server

• Streamable HTTP
• Workspace
• Admin only

Ask in chat

Send this message to the agent.

Copy

Connect an MCP server named docs at https://mcp.example.com/mcp.

or

Use Connectors

Find MCP on the Connectors page.

Open Connectors →

Your UFO returns a private credential form. Enter the endpoint and token there. Never put the token in chat.

What UFO can do

UFO reads the server’s tool catalog and each tool’s input schema before it calls the tool. The server defines the available operations.

Use the docs MCP server to find the current authentication policy. Cite the page it came from. Do not change anything.

Results from an MCP server are external content. Your UFO treats them as data, not as instructions that can change your request.

Manage a server

Ask your UFO to update the URL or token, or to remove the named server. Removing it stops future tool calls. If a call fails, confirm the endpoint, token, server availability, and tool name.