Skip to main content
Glama

A small bridge that exposes any Pumperly instance as an MCP server, so an AI agent can find the cheapest fuel or charging near a place or along a drive, in about 40 countries, mostly in Europe.

Features

  • Six read-only tools:

    Tool

    What it answers

    cheapest_fuel_on_route

    Where to fill up between two places, in one call

    find_nearest_stations

    Stations near a place name or coordinates, by distance or price

    get_stations_in_area

    Stations inside a bounding box, cheapest first

    calculate_route

    Driving distance and time between places, with up to 5 stops

    find_route_stations

    Stations along a route geometry you already have

    geocode

    Coordinates for a place name

  • Four resources: pumperly://fuel-types, pumperly://config, pumperly://stats, pumperly://exchange-rates.

  • Short answers: station lists are sorted, cut to a limit and summarised (min, median and max price), so a search costs about 1 KB of context.

  • MCP 2026-07-28 and every earlier version back to 2024-11-05, on the same binary: new clients use server/discover, older ones initialize.

  • Two transports: stdio, and streamable HTTP on /mcp with a bearer token and origin checks.

  • Works with the public instance at pumperly.com or your own: set PUMPERLY_URL. No API key.

Every tool only reads, so there is no read-only switch to set.

Related MCP server: Foundry MCP Server

Install

The npm package downloads the release binary for your platform, checks its SHA-256 against the checksums shipped in the package, and runs it over stdio. It needs Node.js 18 or later.

Claude Code:

claude mcp add pumperly -- npx -y pumperly-mcp

Claude Desktop (claude_desktop_config.json) and Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "pumperly": { "command": "npx", "args": ["-y", "pumperly-mcp"] }
  }
}

VS Code (.vscode/mcp.json):

{
  "servers": {
    "pumperly": { "type": "stdio", "command": "npx", "args": ["-y", "pumperly-mcp"] }
  }
}

Codex (~/.codex/config.toml):

[mcp_servers.pumperly]
command = "npx"
args = ["-y", "pumperly-mcp"]

Docker, over stdio:

docker run -i --rm -e TRANSPORT=stdio drumsergio/pumperly-mcp:v0.2.0

To use your own Pumperly instance, add PUMPERLY_URL to the environment ("env": { "PUMPERLY_URL": "https://..." } in the JSON configs). For the HTTP transport, see Getting started.

Documentation

  • Getting started: npm, Docker Compose, building from source, connecting a client

  • Configuration: environment variables

  • Usage: tools, resources, the request flow, testing with the Inspector

  • Related projects: the Pumperly family, other MCP servers, registry listings

License

GPL-3.0-or-later

Available Tools

6 tools
calculate_routeCalculate a driving routeA
Read-onlyIdempotent

Calculate a driving route and return its distance (km), driving time (minutes) and bounding box, with up to 2 alternatives when there are no waypoints. Ends can be place names, "lat,lon" text or coordinates. To find fuel along the way, call cheapest_fuel_on_route instead: it routes and searches in one call. Set include_geometry only to pass the line to find_route_stations; it can be up to 2000 points.

Inputs: origin, dest_lat, dest_lon, waypoints, +4 more. Returns: origin, routes, destination

cheapest_fuel_on_routeCheapest fuel along a tripA
Read-onlyIdempotent

Plan a drive and find where to fill up: routes from origin to destination, then lists the stations within corridor_km of the route, cheapest first, with each one's km from the start. Ends can be place names ("Madrid", "Valencia"), "lat,lon" text or coordinates. Prices are per litre (per kg for CNG, LNG and H2, per kWh for EV) in local currency; cross-border trips mix currencies, see pumperly://exchange-rates. Uses two of the API's 30 route searches per minute.

Inputs: fuel (required), limit, origin, sort_by, +6 more. Returns: origin, stations, destination, distance_km, +1 more

find_nearest_stationsFind nearest fuel or EV stationsA
Read-onlyIdempotent

Find the fuel stations or EV chargers closest to a point, with current prices. Give the point as lat and lon, or as a place name in near (geocoded for you). sort_by=distance (default) returns the nearest; sort_by=price returns the cheapest among the 50 nearest within the radius. Prices are per litre (per kg for CNG, LNG and H2, per kWh for EV) in the station's local currency. Covers about 40 countries, mostly in Europe; pumperly://stats lists them.

Inputs: fuel (required), lat, lon, near, +3 more. Returns: fuel, unit, found, center, +4 more

find_route_stationsFuel or EV stations along a route lineA
Read-onlyIdempotent

List the fuel stations or EV chargers within corridor_km of a route line you already have, cheapest first by default, with each station's km along the route. Most callers want cheapest_fuel_on_route, which takes place names and does the routing too. Prices are per litre (per kg for CNG, LNG and H2, per kWh for EV) in local currency. The API allows 30 route searches per minute.

Inputs: fuel (required), geometry (required), limit, sort_by, +1 more. Returns: fuel, unit, found, center, +4 more

geocodeGeocode a place nameA
Read-onlyIdempotent

Turn a place name or address into coordinates (lat, lon), best match first. The station and route tools already accept place names, so call this only to pick between ambiguous places or to get coordinates for a bbox. Give lat and lon to prefer results near a point.

Inputs: query (required), lat, lon, limit. Returns: query, results

get_stations_in_areaFuel or EV stations in an areaA
Read-onlyIdempotent

List the fuel stations or EV chargers inside a bounding box with current prices, cheapest first by default, plus the min, median and max price per currency. Use it for "cheapest diesel in this town". For a point and radius use find_nearest_stations; along a trip use cheapest_fuel_on_route. Prices are per litre (per kg for CNG, LNG and H2, per kWh for EV) in local currency. Keep the box city-sized: a whole-country box can exceed the 8 MB answer cap.

Inputs: bbox (required), fuel (required), limit, sort_by. Returns: fuel, unit, found, center, +4 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct query shape: route geometry, route+fuel, point-radius, route-corridor, geocoding, or bounding box. The main overlap is between cheapest_fuel_on_route and find_route_stations, but the descriptions explicitly steer callers to the right one.

    Naming Consistency4/5

    All names use snake_case and are mostly verb_noun or find_* patterns. Minor deviations exist: cheapest_fuel_on_route has no leading verb, and the set mixes calculate/find/get/geocode rather than one retrieval verb, but the conventions remain readable.

    Tool Count5/5

    Six tools is well-scoped for a fuel-station and routing server, with each tool covering a meaningful query mode. There is no obvious filler or redundancy that should be removed.

    Completeness4/5

    The surface covers the main workflows: geocoding, route calculation, nearest stations, area search, and route-corridor fuel search. A dedicated station-detail or station-by-ID tool is missing, but most practical agent workflows can be composed from the existing tools.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers