How to Use the Webhook.site MCP in Windsurf

Q: How do I check the payload history in Windsurf using Webhook.site?

You use the getrequests tool on the MCP Server. This pulls every request that hit a specific token URL, letting you inspect the full raw payload. It’s how you verify what your upstream service is actually sending.

Q: Can I manage Webhook.site tokens in Windsurf?

Yep. You can list all available tokens via listtokens or create a new one using createtoken. This ensures that every time Windsurf needs a test endpoint, it's working with the right, active URL.

Q: What if I need to set up Webhook.site for CI/CD in Windsurf?

You use setresponse first. This tool lets you define a static or dynamic body that the MCP Server will send back when your Windsurf agent hits the test URL, making it reliable for testing pipelines.

Q: Do I need to clean up old data logs with Webhook.site and Windsurf?

It's smart to keep things tidy. Use deleterequests after a major debug cycle. This deletes multiple requests associated with a token, keeping your MCP Server records clean.

See complex webhooks flow through your Windsurf agent.

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 Windsurf

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Test Webhook Payloads with the MCP Server

Need to check what a webhook sends? You can get all requests captured by any token using `get_requests`. It dumps the full payload, letting you see exactly how your service is calling this endpoint. You also have `list_tokens` and `get_token`. This lets Windsurf confirm which URLs it's dealing with before trying to execute an action. Perfect for debugging connection issues.

Automate Responses for Testing

Don't just read the data—change it. Use `set_response` to define a dynamic response body for a specific request. This lets your Windsurf agent test how downstream systems react when they get predictable, fake data. If you need to tweak what that response looks like later, you can use `update_global_variable` and `update_action`. It's great for chaining multi-step tests.

Manage Webhook Tokens

The MCP Server gives you full control over the test tokens. You can list all available tokens with `list_tokens`, or create a brand new one using `create_token`. Each token generates a unique URL for your Windsurf agent to hit. If a token gets stale, no sweat. You can delete it outright with `delete_token` or clean up old data logs using `delete_requests`.

Setup guide

Set up Webhook.site MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
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

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my Webhook.site payment history." If connected, Cascade will call the Webhook.site tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.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 Windsurf

You use the `get_requests` tool on the MCP Server. This pulls every request that hit a specific token URL, letting you inspect the full raw payload. It’s how you verify what your upstream service is actually sending.

Yep. You can list all available tokens via `list_tokens` or create a new one using `create_token`. This ensures that every time Windsurf needs a test endpoint, it's working with the right, active URL.

You use `set_response` first. This tool lets you define a static or dynamic body that the MCP Server will send back when your Windsurf agent hits the test URL, making it reliable for testing pipelines.

It's smart to keep things tidy. Use `delete_requests` after a major debug cycle. This deletes multiple requests associated with a token, keeping your MCP Server records clean.

It manages request payloads and global variables. These are typically JSON or form-encoded data that represent the incoming webhooks' body content.

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