Weather Skill

What this skill does

Give your agent live weather. Call it as an MCP tool to read current conditions — temperature, humidity and more — for any location. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Weather Skill — exactly what your agent gets back when it makes the call.

vervekit · weatherforecasttool call

{
  "city": "San Francisco"
}

result

tempC: 13.3
tempF: 55.9
windMph: 4.7
windKph: 7.6
windDegree: 273
windDir: W
pressureMb: 1022
pressureIn: 30.17

+8 more fields

Run it with your own input. Live calls happen in your dashboard, on your key.

Sign in to try

Ways to use it

Add weather without a provider

Instead of signing up for a weather API and wiring its SDK, enable the Live Weather skill and your app can pull live conditions through the connection you already have.

A tool your agent calls

Over MCP, the weatherforecast tool shows up to your model automatically — it invokes it when a task (trip planning, logistics, scheduling) needs real conditions, with no code from you.

One GET from any backend

Node, Python, Go — call weatherforecast over REST in a single request to fetch conditions server-side, same key as every other skill.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

weatherforecast

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/weatherforecast

Ask your agent

“Enable Weather and ask your agent to add weather to your app.”
“What's the weather in Tokyo right now?”

Weather Skill, answered

How to connect it over MCP or REST.

How do I add Weather to my app or agent?

Enable the Weather Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the weatherforecast tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add weather to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Weather appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Weather call cost?

Each call costs 5 credits. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Weather is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Weather is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

More Weather skills

Browse all skills

Add weather without a provider

A tool your agent calls

One GET from any backend

Weather Skill, answered

Give your software a way to act on the world.

Scaling in production?