How to Use the Webhook.site MCP in Claude

Q: Can I delete old data using Webhook.site with Claude Desktop?

Yep. If a token has too much history, the deleterequests tool cleans up multiple requests at once. This keeps your logs clean and focused on what matters for development.

Use Webhook.site to test and debug webhooks directly within your Claude Desktop environment.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Webhook.site MCP to Claude Desktop

Create your Vinkius account to connect Webhook.site to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Webhook.site with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Test API Endpoints with Webhook.site

The `get_requests` tool lets you pull every payload that hit a specific token. You can see exactly what data was sent to your webhook, making debugging simple. Need to change how the system responds? Use `set_response` to define custom output for any captured request, letting your agent act on controlled mock data.

Manage Webhook Tokens and Variables

Don't lose track of keys. The `list_tokens` tool gives you a full rundown of all active webhook tokens. Plus, the `create_global_variable` function lets your agent store persistent context across different sessions. If things change, update them easily. You can use `update_token` or modify existing variables using `update_global_variable` right from your Claude Desktop session.

Automate Webhook Actions

Use the `create_action` tool to build custom, multi-step workflows for specific tokens. This lets you pre-program what happens when data hits the webhook. You can then execute these steps instantly with `execute_action`, proving that your agent can run complex logic without leaving the chat interface.

Setup guide

Set up Webhook.site MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Webhook.site MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Webhook.site MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under webhooksite-mcp.

json

{
  "mcpServers": {
    "webhooksite-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Webhook.site. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Webhook.site now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Webhook.site MCP in Claude Desktop

Just connect the MCP Server in your Claude Desktop settings. Once connected, you can call tools like `get_requests` to pull payloads from a token's history. It’s great for seeing what data actually hits your endpoint.

You set up the public webhook URL in Webhook.site, then use Claude Desktop's tools to send simulated requests against it. This lets you verify your logic before exposing endpoints that handle sensitive data.

Yep. If a token has too much history, the `delete_requests` tool cleans up multiple requests at once. This keeps your logs clean and focused on what matters for development.

This server primarily handles HTTP request payloads, token credentials, and global variable strings. Always remember that the data you send to a webhook is visible within its records.

No, because this MCP Server handles external webhooks, it must be publicly reachable for your agent to test the flow correctly. You won't work with local files here.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript