VerveKit
MCP server

The MCP server that gives your agent real-world skills.

One connection, and any MCP agent — Cursor, Claude, or your own — can call 350+ live skills as native tools. Authorize with OAuth, paste no keys, pay one bill.

Connect your agentBrowse skills
agent session · MCP
You

What's the weather in Austin right now?

vervekit · weathertool call
{ "city": "Austin" }
returned in 420 ms · { tempF: 96, condition: "Sunny" }
Agent

It's 96°F and sunny in Austin right now.

How it connects

One URL. OAuth. Done.

VerveKit is a remote MCP server — there's nothing to install and no key to paste. Point your client at it, authorize in the browser, and every enabled skill shows up as a tool.

  • Remote — it's a URL your agent connects to, not a local process.
  • OAuth — authorize in the browser; no API keys living in your config.
  • Streamable HTTP — the standard MCP transport, so it works in every modern client.
mcp.jsonMCP
{  "mcpServers": {    "vervekit": {      "url": "https://api.vervekit.com/v1/mcp"    }  }}
First connect opens OAuth in your browser — nothing to paste.
Every MCP client

Point any agent at it.

Same server, same skills, in the tool you already build with. Pick yours for the exact config.

CurCursorMCP · OAuthClClaude DesktopMCP · OAuthWndWindsurfMCP · OAuthClnClineMCP · OAuth
What your agent can do

Skills it can call the moment it's connected.

A few of the 350+ live skills on the server — each one a real call, billed by use.

WeatherSkill

Ask your agent for live conditions anywhere on Earth.

Open skillDNS LookupSkill

Have it check a domain's records in the middle of a task.

Open skillCurrency ConverterSkill

Let it convert an amount at today's real exchange rate.

Open skillIP LookupSkill

Turn an IP into a location while it reasons.

Open skill
Why it's different

A skill is not an endpoint.

An API waits for a developer who already knows what to call. A skill is built for software that has to decide on its own.

Model-readable

Every skill is named and described for a model, so the agent picks the right one itself — no endpoint hunting, no docs to parse.

Called mid-thought

Skills run while the agent reasons, so its answer comes from what's true right now — not from whatever it last saw in training.

One key, usage-based

Every skill sits on one connection, billed per call. Idle skills cost nothing — turn them on and off freely.

Give your agent a connection to the world.

Connect your agent→See all integrations

One URL, then OAuth

Point your MCP client at one endpoint and authorize — no key to paste. Your first credits are on us.

Browse skills