MCP integration

Give Windsurf a connection to the real world.

Register VerveKit as an MCP server in Windsurf and Cascade can call 350+ live skills as tools — no per-API SDKs, no glue code, just one config.

One config connects Windsurf.

No SDKs, no endpoint plumbing, no per-skill wiring. Add the key, drop in the snippet, and every enabled skill is available.

  1. 1Add VerveKit to Windsurf's mcp_config.json.
  2. 2Refresh MCP servers in settings.
  3. 3Authorize with OAuth — Cascade picks up every skill.
~/.codeium/windsurf/mcp_config.jsonMCP
{  "mcpServers": {    "vervekit": {      "serverUrl": "https://api.vervekit.com/v1/mcp"    }  }}
Refresh MCP servers; Windsurf runs the OAuth flow, then Cascade sees every skill.

Real capabilities, on demand.

A few of the 350+ skills you can reach the moment Windsurf is connected — each one a live call, billed by use.

Windsurf's Cascade agent is built to take action. VerveKit widens what it can reach — one MCP connection turns hundreds of live capabilities into tools it can pick up mid-task.

  • One-click OAuth — no key to paste, no secrets in your config.
  • MCP-native — connects the way Windsurf expects.
  • Usage-based — idle skills cost nothing; pay per call.
  • Powered by APIVerve — a production engine with a 99.9% uptime SLA.

Connect the rest of your stack.

Give Windsurf real-world skills.

Windsurf, connected

Grab a key, enable a few skills, and paste one config. Your first credits are on us — no card.

See how it connects