Skip to content
Auteryn

Custom MCP & Webhooks

Use Custom MCP integrations when a service exposes an MCP server (HTTP or SSE transport). Use custom webhook connections when an external system should trigger a Flow via HTTP POST.

Custom MCP server

Section titled “Custom MCP server”
  1. Go to Console → Integrations
  2. Click + Custom MCP
  3. Enter the MCP server URL and authentication (Bearer token, headers, etc.)
  4. Test the connection
  5. Attach the integration to an agent under Integrations

Custom MCP tools appear in the agent runtime like other integration tools. You can also enable inbound webhooks on a Custom MCP connection for event-driven flows.

Inbound webhooks (Flows)

Section titled “Inbound webhooks (Flows)”

For verified integrations (GitHub, Slack, etc.), Auteryn provisions webhook URLs automatically when you create connections and flows.

For custom webhook integrations:

POST https://api.auteryn.ai/webhook/in/c/{token}

Use Standard Webhooks signing when configured. See Triggers → for event flow setup.

Calling arbitrary REST APIs

Section titled “Calling arbitrary REST APIs”

If a service has no native integration:

  1. Check whether a Featured MCP or vendor-hosted MCP exists in the catalog
  2. Otherwise, self-host or point a Custom MCP wrapper at the REST API
  3. Or use an Internal agent with sandbox + 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 agent sandbox tools.

Credentials

Section titled “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.

Section titled “Related”