MCP integration

Give Cline the tools to finish the job.

Cline is an autonomous coding agent in VS Code. Point it at VerveKit over MCP and it can call 350+ live skills as it works — the same key powers every one.

One config connects Cline.

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 Cline's MCP settings.
  2. 2Save the settings file.
  3. 3Authorize with OAuth — the tools are ready.
cline_mcp_settings.jsonMCP
{  "mcpServers": {    "vervekit": {      "url": "https://api.vervekit.com/v1/mcp",      "type": "streamableHttp"    }  }}
Save and Cline authorizes over OAuth, then loads the skills as tools.

Real capabilities, on demand.

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

Cline runs multi-step tasks on its own. The more real tools it has, the more it can actually finish — VerveKit hands it hundreds through a single MCP server, so it isn't stuck simulating what it can't reach.

  • One-click OAuth — no key to paste, no secrets in your config.
  • MCP-native — connects the way Cline 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 Cline real-world skills.

Cline, connected

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

See how it connects