VerveKit

One config is the whole integration

Grab the ready-made snippet for your tool, drop it in, and every enabled skill is connected. No SDKs, no endpoint plumbing, no per-service auth — just one config and one key you rotate from the dashboard. This is the setup story: from picking your tool to your first live call.

  • Ready-made snippets
  • One key
  • No SDKs
Get your key→Browse integrations
In the box
  • SnippetsCursor · Claude · Bolt
  • PromptsSystem-prompt starters
  • KeyOne · rotatable
  • PlumbingNone
What's in the config

Everything the integration needs, ready to paste

No assembly. Each piece is the finished thing — a snippet, a prompt, a key.

Ready-made snippets

Copy-paste configs for Cursor, Claude Desktop, Bolt, and raw REST. Each one is the complete integration — no assembly, no boilerplate to fill in.

  • Cursor
  • Claude Desktop
  • Bolt
  • cURL

System-prompt starters

Prompt snippets tuned so your agent reaches for the right skill at the right moment — instead of guessing which tool solves the task.

  • tuned prompts
  • right skill

One key connects everything

A single key wires every enabled skill on every plan. Rotate it from the dashboard anytime — nothing downstream needs to change.

  • one key
  • rotate anytime

No SDKs, no plumbing

There are no per-service SDKs to install and no endpoint wiring to maintain. The config is the integration — that's the whole surface area.

  • no SDKs
  • no endpoints
Per-tool guides

Pick your tool

Every tool has its own step-by-step guide with the exact config. Open the Integrations directory and choose yours — we won't duplicate them here.

AI editors & agents

Cursor, Claude Desktop, Windsurf, and Cline each have a per-tool guide with the exact MCP config to drop in. Skills show up as native tools in the editor.

  • Cursor
  • Claude Desktop
  • Windsurf
  • Cline

No-code & AI builders

Bolt, v0, and Lovable have their own walkthroughs. Paste one config into your generated project and it can fetch live data out of the box.

  • Bolt
  • v0
  • Lovable

Your own code

Prefer raw REST? Call any skill with one key and a normal HTTP request from Node, Python, Go, or anything else. The Skill Registry lists every endpoint.

  • REST
  • any language
Setup

Three steps to connected

Pick, copy, paste — and every enabled skill is wired to your tool.

  1. 01

    Pick your tool

    Choose your editor, agent, or no-code builder — Cursor, Claude Desktop, Bolt, v0, and more each have a per-tool guide with the exact config.

  2. 02

    Copy the snippet

    Grab the ready-made config for that tool. It already points at the VerveKit MCP endpoint (or REST base) — nothing to hand-assemble.

  3. 03

    Drop it in

    Paste the config, authorize once, and every enabled skill is connected. Rotate your key from the dashboard whenever you need to.

Setup, answered.

What one config actually covers before you paste it in.

Browse integrations →
How much setup is there really?
One config. You copy the snippet for your tool, paste it in, and every enabled skill is connected — there are no SDKs to install and no endpoints to wire. That's the whole integration.
Which tools have a ready-made snippet?
Cursor, Claude Desktop, Windsurf, Cline, Bolt, v0, and Lovable each have a dedicated per-tool guide, plus a raw REST option for your own code. Browse them all in the Integrations directory.
What is a system-prompt starter?
It's a short prompt snippet, tuned so your agent reaches for the right skill at the right moment. Paste it alongside the config and the model knows which of your enabled skills to call for a given task.
Do I need a separate key per tool?
No. One key connects every enabled skill across every tool you set up. Rotate it from the dashboard anytime — the same key covers dev-time and runtime.
What shows on my bill?
VerveKit runs on APIVerve, our production data engine, so invoices and card statements read APIVERVE. Same account, same key, same rails — nothing else changes.

One config, and every skill is connected.

Get your key→Browse integrations

Not sure which tool?

See how the connection works end to end, from MCP tools to a raw REST call.

How it works