Custom MCP & Webhooks

Use a Custom MCP Integration when a service offers an MCP endpoint (HTTP or SSE transport) that is not in the catalog. To start an agent from an outside event, use a Loop on one of the Integrations listed under Inbound webhooks.

Custom MCP

Go to Console → Integrations
Click Custom MCP
Enter a name, the server URL (HTTPS), the transport (HTTP or SSE) and the authentication: none, a Bearer token, an API key in a header you name, or OAuth
Click Register integration, then use Test on it to check the connection
Attach the integration to an agent under Integrations

Its abilities appear on the agent like those of any other Integration. Auteryn has not reviewed a Custom MCP endpoint, and the Console says so.

Inbound webhooks (Loops)

A Loop can start when something happens in a connected Integration. Set up the events on the connection:

GitHub, Jira, Confluence, Notion, Google Calendar: open the connection’s menu and choose Configure webhooks (for Google Calendar, Configure calendar watch)
Slack, Telegram, Twilio, the Web Chat Widget, Email: Auteryn sets up the events when you create the connection. If it cannot set your Twilio number’s webhook itself, it shows you the URL to paste instead

Then create the Loop, as Triggers describes. The Console has no general-purpose inbound webhook URL, for a Custom MCP connection or otherwise.

Calling arbitrary REST APIs

If a service has no Integration in the catalog:

Check whether a Featured MCP Integration exists for it in the catalog
Otherwise, point a Custom MCP Integration at an MCP endpoint for the service, yours or the vendor’s
Or use an Internal agent with a sandbox and curl for ad-hoc API calls (not recommended for production)

There is no separate “Custom API” tile in the Console: REST access goes through MCP or the agent’s sandbox.

Credentials

Store API tokens in the connection setup for the integration (encrypted at rest). Do not put secrets in agent instructions. Paste tokens only in the Integrations connection form.