Skip to main content
Use Custom MCP when a service exposes a public MCP server. Use Custom API when it gives you an API key and an HTTP API instead. Add a custom connection only when a specific job needs it, then start with the narrowest tool permissions that work. Both options live in Connected Apps.
Looking for Gmail, Calendar, Slack, or another built-in option? Start with Connect your apps.
Never paste passwords, API keys, bearer tokens, or reusable secrets into a session. Enter them only in the matching credential field under Connected Apps.

​
Connect a custom MCP server

Your MCP server needs a public HTTPS endpoint that Runner can reach. Use the full endpoint, including a path such as /mcp or /sse when the server requires one. Plain HTTP, private network addresses, query strings, and URL fragments aren’t supported.
1

Open Custom MCP

In Runner, click Connected Apps in the sidebar. Find Custom MCP, then click Connect.
2

Enter the server details

In Connect an MCP server, fill in Name and HTTPS endpoint.For example: https://mcp.example.com/mcp
3

Choose an authentication method

Open Authentication and choose one:
  • No authentication for a server that doesn’t require credentials.
  • Bearer token to enter a token in the Bearer token field. Runner encrypts the token before storing it and doesn’t show it again.
  • Sign in with the provider for OAuth. Runner opens the provider’s sign-in flow after you connect.
4

Connect the server

Click Connect server. For OAuth, finish signing in with the provider.Runner discovers the tools advertised by the server. The connection then appears under Connected, with each tool listed in its Tools section.
Leave the advanced OAuth settings alone unless the server owner gave you a pre-registered OAuth client. In that case, click Show Advanced and enter its Client ID and optional Client secret. If the provider asks for a callback URL, use Copy beside Callback URL and register it there.

​
Connect a custom API

No MCP server? If the service has an HTTP API and gives you an API key, add a Custom API connection instead.
1

Open Custom API

In Connected Apps, find Custom API, then click Connect.
2

Save the API key

In Connect an API key, fill in:
  • Name
  • API key
  • Docs or API URL (optional), using a public HTTPS documentation page or API base URL
Click Connect API key. Runner encrypts the key before storing it. The key doesn’t appear in your session and isn’t displayed again.
3

Approve the API URL

Runner won’t use the stored key until you approve where it can be sent.If Runner finds a possible destination from public API documentation or the URL you entered, open the connection, review Suggested API URL, then click Approve API URL. Discovery reads only public pages and never sends your key.If there’s no suggestion, find Approved API URL, enter the public HTTPS base URL in API URL, then click Save URL.
Once you approve the URL, the connection gets two tools:
  • read makes GET, HEAD, and OPTIONS requests to the approved API URL.
  • request makes any request to the approved API URL, including writes.

​
What approving an API URL does

Runner approves the exact HTTPS scheme and host, not a path. If you enter https://api.example.com/v1, the approved URL is https://api.example.com. Any path, query string, or fragment is removed. Runner sends the stored key only to that approved scheme and host. A redirect never receives the key. If the suggested API host differs from the documentation host, Runner shows a warning so you can review the destination before approving it.

​
Set tool permissions

Open either custom connection and find Tools. Each tool shows the settings it supports, so you may not see all four on every tool. Start action tools on Ask. Move a tool to Allow only when you want Runner to use it without approval.

​
Manage or remove a custom connection

Open the connection under Connected to manage it:
  • For an MCP server, use Refresh tools, Reconnect for OAuth, or Remove and then Remove server. For bearer authentication, enter a new value under Bearer token, then click Replace token.
  • For a Custom API connection, use Approved API URL and Save URL to change the destination, Replace API key and Replace key to store a new key, or Remove and then Remove connection to delete it.
Removing a connection erases its stored credential from Runner. Revoke the token or key with the provider too.