Rijwind
Live · free to try

Maps your AI agent can actually use.

A hosted MCP server that hands Claude, ChatGPT, Cursor and Codex the whole platform as tools: search, routes, reach, matrices, GPS matching, static images and an interactive map in the conversation. Same key, same unit pool, nothing to run.

Get an API keyRead the docs

Included in every plan, free tier too. No credit card.

Real tool results3 units

Plan me a bike route from Utrecht Centraal to Amersfoort station.

  • geocode_forwardUtrecht Centraal1 u
  • geocode_forwardStation Amersfoort Centraal1 u
  • directions2 locations · bicycle1 u

24.3 km, about 1 h 26 min by bike.

Out through the Biltstraat, then the Soestdijkseweg Zuid and the Amersfoortsestraat most of the way.

mapRef r_cswn5saovt · pass to show_map for an interactive map

tools/call · geocode_forward · geocode_forward · directions · 3 units from the same pool

3 tool calls · 3 units · same pool as the API

Where it lands in your product.

Nobody ships a protocol. They ship a support assistant that answers 'how far is the nearest branch', a coding agent that wires a store locator without leaving the editor, a planning chat that hands back the map. This is what the MCP server looks like from the outside.

An assistant with the Rijwind connector

Plan me a bike route from Utrecht Centraal to Amersfoort station and show it on a map.

geocode_forwardgeocode_forwarddirectionsshow_map

24.3 km, about 1 h 26 min by bike, mostly along the Soestdijkseweg and the Amersfoortsestraat. Here it is on the map:

The bike route from Utrecht Centraal to Amersfoort station drawn on a light map, start and finish markedmap card · pan, zoom, click© OpenStreetMap contributors

The agent hands back a map, not a link.

Ask for a route and the reply carries the map: an interactive card in the Claude apps, ChatGPT and VS Code, a rendered image everywhere else. Routes and reach areas go straight from the tools onto it, no geometry through the model.

The routing behind it
terminal
claude mcp add --transport http rijwind https://mcp.rijwind.com \
  --header "Authorization: Bearer rw_live_…"

one URL · API key or OAuth · streamable HTTP

One URL, every client.

Coding agents take the key as a header; the Claude and ChatGPT apps sign in with your account and need no key at all. Same server, same tools, whichever way in.

Connection steps per client

One agent, one task, the calls it made

  1. geocode_forward+1
1units, the same as over REST

no MCP meter
one monthly pool

A tool call costs what the API call costs.

No agent surcharge and no separate meter. Every tool proxies to the same endpoint your code would call, drawn from the same monthly pool, capped by the same spending cap.

See what a month costs
.mcp.json
{
  "mcpServers": {
    "rijwind": {
      "type": "http",
      "url": "https://mcp.rijwind.com",
      "headers": { "Authorization": "Bearer rw_live_…" }
    }
  }
} // commit it, and the whole team's agents have maps

Read-only by design.

The server can search, route and draw; it cannot touch your subscription, your keys or your spending cap. An agent that misreads an instruction can cost you units, never money beyond the cap you set.

Read the MCP guide

Every tool returns the API's own answer.

The server is a thin translation layer, not a second product. A tool result is the REST response, plus one small reference the map tool can pick up. Anything you learned from the API docs is true here too.

Every tool, in the docs ↗
tools/call · directions
  1. {
  2. "trip": {// byte for byte the REST response: the code you wrote for the API reads this
  3. "summary": { "length": 24.315, "time": 5167.354, "hasFerry": false, … },// what the agent quotes back: 24.3 km, about 1 h 26 min
  4. "legs": [{ "maneuvers": [ … ], "shape": "…" }],// 61 turn-by-turn steps and the geometry, which the agent never has to copy around
  5. "locations": [ … ], "status": 0, "units": "kilometers"
  6. },
  7. "mapRef": "r_cswn5saovt"// the one extra field: hand it to show_map and the route appears on an interactive map, no geometry through the model
  8. }

The short version.

Everything a developer scans a product page for, in one place, without the adjectives.

AvailabilityOne hosted URL. Nothing to install or run.
live
ToolsSearch ×3, directions, matrix, isochrone, matching, optimisation, static map, interactive map.
10
Cost per callSame units, same monthly pool, same spending cap. No MCP meter.
= the API call
Included inFree tier included, inside its monthly units. Paid from €5 / month.
every plan
ClientsClaude Code, Cursor, Codex, the Claude and ChatGPT apps, VS Code.
any MCP client
AuthA header for coding agents; OAuth for the consumer apps, no key to copy.
API key or sign-in
Map in the conversationInteractive card where the client supports MCP Apps, an image elsewhere.
yes
Billing or account changesRead-only data tools. Nothing can touch money or keys.
impossible
Management over MCPKeys, usage and projects stay in the dashboard for now.
not yet
Rate limitPer key. Sustained agent work is fine; runaway loops are not.
120 calls / min
ProcessingServer, API and tiles. DPA and sub-processor list published.
EU, end to end

Numbers as of October 2026. The pricing page has the full ladder.

MCP, answered.

What is the MCP server?

A hosted server that speaks the Model Context Protocol, the open standard AI assistants use to call tools. Connect it once and the assistant can search places, plan routes, compute travel-time matrices and reach areas, snap GPS traces, optimise stop orders and draw maps, using your Rijwind account.

Which assistants work with it?

Anything that speaks MCP over HTTP. Coding agents such as Claude Code, Cursor and Codex connect with your API key as a header. The Claude apps and ChatGPT connect as a custom connector with a browser sign-in and need no key at all. VS Code and other MCP clients work the same way.

What does it cost?

Nothing on top of the API. Every tool call is proxied to the same endpoint your code would call and costs the same units, from the same monthly pool, under the same spending cap. Access is included in every plan, the free tier too: there it runs inside the free monthly units and stops at the cap. The Personal plan at five euros a month is the cheapest paid step up.

Is it available now?

Yes. The server is live at one URL. Make an account, then connect your client with a browser sign-in or your API key; the docs walk through every client.

Can the agent show a map, not just numbers?

Yes, two ways. The static image tool returns a real picture that renders inline in any client that shows images. The interactive map tool opens a pannable, zoomable map card in the conversation, in clients that support MCP Apps, with markers, routes and reach areas passed straight from the other tools by reference.

Is it safe to give an agent my account?

The server is read-only and data-plane only. No tool can change your plan, keys, origins or spending cap, or touch payment settings. The worst an agent can do is spend units up to the cap you set. Keys can be scoped, and a scoped key hides the tools it cannot use from the agent entirely.

Where is it weakest?

There is no management plane yet: an agent cannot create keys, read your usage or change project settings over MCP, only use the data tools. The interactive map card needs a client with MCP Apps support; terminal agents get the structured result and the static image instead.

Do I have to run anything?

No. It is a hosted server at one URL. There is no package to install, no process to keep alive and nothing to update; the configuration is a few lines in your client.

Is there a free tier?

Yes. The free tier includes the MCP server, inside the same 10,000 units a month as the API, with a hard cap and no credit card. A paid plan raises the units when the agent needs more.

Where are the requests processed?

In the European Union, end to end: the MCP server, the API behind it and the map tiles. No part of the path touches a US-controlled provider. We publish a DPA and a full sub-processor list.

Also on the same key.

Geocoding

The search the agent calls first.

Routing

Car, bike and foot directions behind the route tool.

Isochrones

The reach areas behind 'can we get there in 20 minutes'.

Static maps

The picture the agent hands back where there is no map card.

Pricing

One unit pool, one table, a cap you set.

Rijwind vs Mapbox

What actually differs, feature by feature.

Give your agent a map.

Included in every plan, the free tier too. The same key covers the API directly.

plan me a bike route from Utrecht Centraal to AmersfoortGet an API key
No credit card for the API. No sales call. A spending cap you set yourself.Read the MCP guide