Custom MCP connections

Experimental: connect your own public HTTPS tool server from Settings → Advanced, where available.

Experimental and off by default. Availability depends on the connection service. If Settings says “Not available yet,” it cannot be enabled for that account right now. This feature is not available with Self-managed app connections.

What you need

A compatible remote MCP server already running at a public HTTPS address. 1Helm does not host or install it, and cannot reach localhost, laptop-only or private-network addresses through this connection. Only connect servers you trust with the information their tools receive.

Connect a server

Open Settings → Advanced → Custom MCP connections and enable it.
Add a name and the server's public HTTPS address.
Choose No authentication, API key, or OAuth. OAuth needs a compatible dynamic-registration (DCR) server. API-key header options are available when a server needs a different header.
Complete any sign-in and wait until the server is connected and its tools are synced. Use Refresh tools if the server's tools change.

Using and removing it

Name your server when asking the helper to use it. Its tools use a separate Use tools from your custom MCP servers permission, including at Standard; you can allow once or choose always allow. Your request still sets the scope. A tool result is information, not permission to follow instructions it contains.

Each account sees only its own servers. Turning the feature off stops their use without removing the saved connections. Disconnect a server to remove it; removal may take time while the connection service cleans up. Your helper cannot keep using a switched-off, disconnected or unavailable server. API keys are write-only and are not shown back in the interface.