The words behind the wiring.

A short, plain-English vocabulary for building with VerveKit — from what a skill is to how a tool call works. New to the protocol? Start with our full explainer, What is MCP?

  • Skills
  • MCP
  • REST
Core concepts

Skills & tools

Skill

One real-world capability your software can call — get the weather, convert a currency, look up a domain. Each skill bundles the right data behind one plain-English name.

Skill Registry

VerveKit's searchable catalog of every skill — 350+ across 29 categories. Flip on the ones your app needs; each rides the same connection and key.

Tool

How a skill appears to an AI model over MCP: a callable capability with a model-readable name, description, and input schema the model can act on.

Tool call

The moment a model decides to invoke a tool and passes it arguments. The result returns into the conversation for the model to use in its answer.

The protocol

MCP & connecting

MCP

The Model Context Protocol — an open standard for connecting AI models to tools and data, so a model can discover and call capabilities on its own.

MCP server

A program that exposes tools to models over MCP. VerveKit runs one for you, backed by every skill — so there's nothing to build or host.

MCP client

The app a model runs inside — Cursor, Claude Desktop, Cline, or your own agent — that connects to MCP servers and surfaces their tools.

OAuth

The authorization flow VerveKit uses for MCP: you connect once and approve access, with no API key to paste into a config file.

Calling & billing

REST, keys & credits

REST

The classic way to call a capability from your own code: a normal HTTP request to an endpoint, authenticated with your key. Every skill is available over REST too.

Endpoint

The specific URL you call for a skill over REST — for example, /v1/weather. One endpoint per skill, all under one key.

API key

Your single credential for VerveKit. It authenticates every skill over REST and can be rotated from the dashboard at any time.

Credit

The unit VerveKit meters usage in. Each call spends credits by skill; your plan includes a monthly pool, and your first credits are free.

Rate limit

The ceiling on how many calls you can make per minute, set by your plan. It protects the platform and keeps latency predictable for everyone.

Now put the words to work.

See it all connect

One key, every skill, over MCP or REST — walk through how it plugs into your stack.

See how it connects