How to Use the Webhook.site MCP in Claude Code

Q: How do I use Webhook.site within Claude Code for testing payloads?

You run the getrequests tool from your terminal script. This fetches all captured requests associated with a specific token, letting you pipe that payload data to other tools or variables.

Q: Can I manage Webhook.site tokens using Claude Code?

Yes. You can list them with listtokens and create new ones using createtoken. This makes your MCP Server fully controllable from a headless environment like GitHub Actions.

Q: What if I need to mock data for my CI/CD workflow in Claude Code?

Use the setresponse tool. Your script can call this function to define the exact response body needed, ensuring your pipeline tests run reliably regardless of external service status.

Q: Is it safe to delete tokens with Webhook.site and Claude Code?

Yes. The deletetoken operation cleans up the URL endpoint on the MCP Server entirely, which is perfect for post-deployment cleanup scripts.

Inject webhook testing logic into your CI/CD pipelines with Claude Code's MCP Server support.

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 Code

Create your Vinkius account to connect Webhook.site to Claude Code 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 Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Verify Webhook Data Flow for CI/CD

When running automated jobs, you need proof the data arrived correctly. Use `get_requests` to pull all captured payloads from a token URL. This allows your Claude Code script to verify that the webhook delivered the expected structure. It’s critical for verifying integrations without needing a manual step.

Automate Test Responses in Scripts

Don't let CI tests fail because of external service downtime. Use `set_response` to mock the required HTTP response data directly within your deployment script. This keeps your build pipelines stable. Need complex logic? You can write scripts that use `execute_action` based on a specific request.

Manage Test Infrastructure Tokens

Every pipeline needs clean, dedicated test URLs. Use `list_tokens` to check the status of your MCP Server endpoints. You can also programmatically create fresh tokens with `create_token` at the start of a job. When done, running `delete_token` prevents clutter in your deployment logs.

Setup guide

Set up Webhook.site MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see webhooksite-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Webhook.site transactions." It will automatically discover and invoke the available Webhook.site tools.

Terminal

claude mcp add --transport http webhooksite-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Webhook.site MCP

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

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "webhooksite-mcp": {
      "type": "url",
      "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 Code

You run the `get_requests` tool from your terminal script. This fetches all captured requests associated with a specific token, letting you pipe that payload data to other tools or variables.

Yes. You can list them with `list_tokens` and create new ones using `create_token`. This makes your MCP Server fully controllable from a headless environment like GitHub Actions.

Use the `set_response` tool. Your script can call this function to define the exact response body needed, ensuring your pipeline tests run reliably regardless of external service status.

Yes. The `delete_token` operation cleans up the URL endpoint on the MCP Server entirely, which is perfect for post-deployment cleanup scripts.

The server handles request payloads and global variables. These are typically JSON or raw HTTP body strings that your CI/CD environment processes and inspects for validation.

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