Why list webhooks before creating one?

To avoid duplicates. An agent that registers a webhook without checking can add a second for the same events, which doubles every delivery. Listing first shows whether a callback already covers what you need, so the agent creates one only if nothing does.

What does the list tell an agent?

The configured webhooks and usually their target URLs and subscribed events. That lets an agent audit an integration, spot a stale or broken endpoint, or confirm a callback exists, before it relies on events arriving or adds another.

MCP servers that can list webhooks

4 verified servers expose a tool that can list configured webhooks

Webhooks are easy to create and easy to forget, so before an agent adds another or audits an integration, it lists the ones already registered. Listing webhooks returns what is configured and where it points, so the agent can see the wiring rather than guess at it.

These verified servers let an agent list the webhooks configured on an account.

Top pick

SonarQube

Sonar

Official

Sonar's official MCP server brings SonarQube code quality, security, and coverage analysis into your AI agent.

devops-ci563

Tool:

list_webhooks

SonarQube's list_webhooks returns the webhooks on an organization or project, the read behind auditing what a scan result notifies.

Pick 2

Resend

Official

Resend's official MCP server lets agents send, schedule, and manage email plus contacts, broadcasts, and domains.

email522

Tool:

list-webhooks

On Resend, list-webhooks returns the email-event webhooks registered, so an agent can see what is subscribed to bounces, opens, and deliveries.

Pick 3

Pipedrive

Samuel Fraga

Community

A comprehensive community Pipedrive MCP server: search, read, and update deals, contacts, organizations, activities, and pipelines from your agent.

crm9

Tool:

webhooks_list

webhooks_list returns the webhooks configured for a Pipedrive company, the wiring behind its real-time CRM notifications.

Pick 4

Adyen

Official

Adyen's official MCP server lets agents create payment sessions and links, refund and cancel payments, and manage merchant accounts, terminals, and webhooks.

payments22

Tool:

list_all_merchant_webhooks

Adyen's list_all_merchant_webhooks returns the webhooks at the merchant level, the integration points for payment events.

What to know

A webhook list is the read behind managing event integrations. To avoid a duplicate registration, confirm a callback exists, or audit what is pushing where, an agent reads the configured webhooks: their target URLs and the events they fire on. The services here return the account's webhooks, SonarQube the org or project's, Resend the email ones, Pipedrive the company's CRM webhooks, Adyen the merchant's. From the list an agent can spot a stale endpoint, a missing one, or the duplicate it was about to create.

This pairs directly with creating webhooks: list first, create only if nothing already covers the events. An agent that registers without checking accumulates duplicates that double-deliver, so holding which webhooks exist, or re-reading the list, is what keeps an integration from quietly fanning out.

Questions

Why list webhooks before creating one?: To avoid duplicates. An agent that registers a webhook without checking can add a second for the same events, which doubles every delivery. Listing first shows whether a callback already covers what you need, so the agent creates one only if nothing does.
What does the list tell an agent?: The configured webhooks and usually their target URLs and subscribed events. That lets an agent audit an integration, spot a stale or broken endpoint, or confirm a callback exists, before it relies on events arriving or adds another.