Skip to content
Vinkius

Webhook.site Connector for AI agents.

17 live capabilities

Debug and simulate HTTP webhooks for API integrations.

Live agent request Webhook.site / Connector

Waiting for input…

AI Agent

Why people use Webhook.site

Webhook.site for Debugging API Callbacks

This Connector changes that by bringing the dashboard into your chat. You tell your agent to create a token, and it gives you the URL. When the hit comes in, you ask the agent to show you the payload. No tabs, no hunting for logs, just direct answers.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a way to debug and simulate webhooks using only natural language.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Debugging a Stripe payment callback

    A developer asks the agent to create a token for 'stripe-test' and wait for a webhook.

  2. Real-world use case 02

    Simulating a 500 error from a third party

    A QA engineer needs to see how the app handles a crash.

  3. Real-world use case 03

    Managing environment-wide variables

    A dev uses create_global_variable to store a shared secret across multiple webhook tests, ensuring the agent can use the same value in different scenarios without re-typing it.

Complete set · 17capabilities

The complete Webhook.site capability set.

These are the exact actions your AI can choose when you ask it to work with Webhook.site.

Capability set01 / 05

01—04

4 capabilities in this set.

Part of 17 available through Webhook.site.

  1. 01 Capability

    Create token

    Create a new Webhook.site token with a custom URL. It allows you to generate unique endpoints for different services.

  2. 02 Capability

    Get token

    Get details for a specific token. Use this to check the current configuration and status of a webhook.

  3. 03 Capability

    List actions

    List custom actions for a token. This shows all the automated responses currently configured for your URL.

  4. 04 Capability

    List global variables

    List global variables. This lets you see all the environment-wide data your agent is currently tracking.

Capability set02 / 05

05—08

4 capabilities in this set.

Part of 17 available through Webhook.site.

  1. 05 Capability

    List tokens

    List Webhook.site tokens. Use this to see all your active URLs in one view.

  2. 06 Capability

    Update global variable

    Update a global variable. This lets you change shared state values on the fly during a test.

  3. 07 Capability

    Update token

    Update an existing token. Use this to change the alias or default behavior of a webhook URL.

  4. 08 Capability

    Create global variable

    Create a global variable to store state across different webhook tests. This helps maintain context during complex debugging.

Capability set03 / 05

09—11

3 capabilities in this set.

Part of 17 available through Webhook.site.

  1. 09 Capability

    Delete action

    Delete a custom action from a token. Use this to clean up your automated responses when they are no longer needed.

  2. 10 Capability

    Delete global variable

    Delete a global variable from your environment. This keeps your workspace clean of old test data.

  3. 11 Capability

    Delete requests

    Delete multiple requests for a specific token. It's the fastest way to clear your history during heavy testing sessions.

Capability set04 / 05

12—14

3 capabilities in this set.

Part of 17 available through Webhook.site.

  1. 12 Capability

    Delete token

    Delete a token from your account. Use this to remove old webhook URLs you no longer use.

  2. 13 Capability

    Execute action

    Execute actions for a specific request. This allows you to trigger automated logic on incoming hits.

  3. 14 Capability

    Get requests

    Get requests captured by a token. This lets you see every header and payload that hits your endpoint.

Capability set05 / 05

15—17

3 capabilities in this set.

Part of 17 available through Webhook.site.

  1. 15 Capability

    Set response

    Set dynamic response for a specific request. This is how you simulate custom API behaviors and error codes.

  2. 16 Capability

    Update action

    Update a custom action. Use this to modify existing automated responses without creating new tokens.

  3. 17 Capability

    Create action

    Create a custom action for a token. This lets you define new automated responses for incoming requests.

Set up in minutes

One URL. Then ask Webhook.site to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Webhook.site from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_4UGcdultUkkqhC6PeYxs6JG990XLacW5YNGNQO5y/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Webhook.site, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Webhook.site for the conversation.

Where the request belongs

Work Webhook.site can move forward.

Built around the request

This is for the backend engineer tired of manual payload checking, the QA tester who needs to simulate edge cases, and the DevOps person monitoring webhooks.

01

Backend Developer

Debugging third-party integrations like Stripe or Twilio webhooks without needing to set up local tunnels.

02

QA Engineer

Validating that callbacks trigger the correct logic on the backend by simulating various API response scenarios.

03

DevOps Specialist

Monitoring incoming alerts and automating response triggers via AI-driven actions.

Bring your own AI

Change the model, client or framework. Keep Webhook.site connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Webhook.site.

The practical details behind the request, access and result.

Can I use Webhook.site MCP to see what data my app is sending?

Yes. You can use it to capture and inspect any outgoing HTTP request. Your agent can pull the headers and the raw JSON payload so you can see exactly what your app is doing.

How do I use Webhook.site MCP to test a failed API call?

You can use it to simulate failures easily. Just tell your agent to set a dynamic response with a specific error code, like a 404 or 500, and a custom message.

Is Webhook.site MCP good for debugging Stripe or Twilio webhooks?

It's perfect for that. You can create a unique URL for each integration, watch the incoming data in real-time, and verify that the payloads match what you're expecting from those providers.

Can Webhook.site MCP help me manage multiple test URLs at once?

Yes, it can. Your agent can list all your active tokens, create new ones with specific aliases, and even delete old ones to keep your workspace organized.

Does Webhook.site MCP support global variables for my tests?

Yes, it does. You can create and update global variables to store state or configuration data that your agent can access across different webhook test runs.

Can I use Webhook.site MCP to clear out my request history?

You can. If your logs get too cluttered during a long debugging session, just ask your agent to delete the requests for a specific token to start with a clean slate.

How can I create a temporary webhook URL that expires after one hour?

Use the create_token capability and set the expiry parameter to 3600 seconds. You can also add an alias to make the URL easier to identify.

Can I see the headers and body of the requests sent to my webhook?

Yes! Use the get_requests capability with your Token ID. It will return a list of captured requests including full headers, query strings, and the raw payload content.

Is it possible to make the webhook return a specific JSON response?

Absolutely. Use the set_response capability to define a custom content (base64 encoded), status code, and JSON headers for any specific request received by your token.

One connection away

Give your agent a direct line to Webhook.site.

Connect Webhook.site once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available