Skip to content

Webhook ingestion: register a webhook as an MCP resource #592

Description

@keysersoft

Connectors are pull-only today. Several of the shipped adapters (Shopware, Billbee, Stripe, WhatsApp) have webhooks that would let an agent react to something happening instead of polling for it.

Scope

  • A per-connector inbound webhook URL with a shared secret.
  • Received events stored with a retention window, exposed as MCP resources.
  • Response mapping applies on the way out, same as tool responses.

Design question first: MCP resources or a *_recent_events tool? Resources are the correct primitive; tool support is more widely implemented across clients today. Comments welcome.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    roadmapOn the published roadmap; exempt from the stale bot

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions