Skip to content
Webhook logo

Webhook MCP server

Receive HTTP requests and trigger flows using unique URLs.

Webhook is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
2
Works with
Any MCP client
License
MIT, open source
Updated
August 2026

About the Webhook MCP server

Connect Webhook once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Webhook and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Webhook tools your AI can run

Once connected, your assistant can call any of these Webhook actions by asking in plain language.

  • Return Response

    return a response

    3 fields

  • Respond and Wait for Next Webhook

    return a response and wait for the next webhook to resume the flow

    3 fields

Triggers

Webhook events your agent can watch

These start a run the moment something happens in Webhook, so work gets picked up on its own.

  • Catch Webhook

    Receive incoming HTTP/webhooks using any HTTP method such as GET, POST, PUT, DELETE, etc.

    5 fields

Give your assistant Webhook

Connect Webhook once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Webhook MCP, answered.

No. That is the point of it. One Activepieces server exposes Webhook alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Webhook in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 2 tools, including Return Response, Respond and Wait for Next Webhook, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.