Log inSubmit server
Pumperly MCP logo

Pumperly MCP

by GeiserX

Compare fuel prices, locate stations, geocode places, and plan routes through any Pumperly instance.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pumperly MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "geiserx-pumperly-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pumperly-mcp"
      ],
      "env": {
        "PUMPERLY_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

GeiserX/pumperly-mcp connects MCP-compatible agents to the Pumperly fuel-price comparison service. Its five tools cover station searches, route calculation, route-based station finding, and place geocoding, while three read-only resources expose configuration, statistics, and exchange rates. It supports stdio and HTTP transport, with an npm launcher for local use and a Docker image for HTTP deployments. Reach for it when an agent needs fuel or charging information from Pumperly’s public instance or a self-hosted Pumperly deployment.

Use cases

  • Compare fuel stations near a destination
  • Plan routes with station stops
  • Find nearby EV charging stations
  • Geocode places for location searches

Key features

  • Five fuel and routing tools
  • Three read-only Pumperly resources
  • Stdio and HTTP transports
  • Configurable Pumperly instance URL
  • npm package with platform binary downloads
  • Docker images for amd64 and arm64

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · pumperly-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads256Package downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Pumperly MCP works

What GeiserX/pumperly-mcp does

GeiserX/pumperly-mcp acts as an MCP bridge for Pumperly. It lets an MCP-compatible agent query fuel information without integrating with Pumperly directly. The server can search for nearby stations, list stations within an area, calculate routes, identify stations along a route, and convert place names into geographic coordinates.

It can connect to the public Pumperly service at pumperly.com or to another Pumperly deployment. Pumperly’s API is accessed anonymously, so the setup does not require an API key.

How it works

The server offers five callable tools:

  • find_nearest_stations searches for nearby fuel stations.
  • get_stations_in_area returns stations for a specified area.
  • calculate_route plans a route.
  • find_route_stations locates stations associated with a route.
  • geocode resolves places into geographic data.

Three read-only MCP resources provide access to pumperly://config, pumperly://stats, and pumperly://exchange-rates. These resources are useful for retrieving service configuration, usage or service statistics, and currency exchange-rate data without mutating the connected Pumperly instance.

Two transport modes are available. Stdio is suited to desktop and local agent configurations. HTTP exposes the MCP service through a single /mcp endpoint; the Docker usage example runs that endpoint on port 8080.

Setup and configuration

For a local stdio setup, configure an MCP client to launch the npm package with npx:

config.json
{
  "mcpServers": {
    "pumperly": {
      "command": "npx",
      "args": ["-y", "pumperly-mcp"],
      "env": { "PUMPERLY_URL": "https://pumperly.com" }
    }
  }
}

Set PUMPERLY_URL to the Pumperly instance the server should use. The npm package downloads and runs a release binary for the local platform. Docker images are available for amd64 and arm64 and provide the HTTP deployment path. The project also documents Docker Compose and building from source as setup options.

Tools and capabilities

The server is intended for travel and transportation workflows involving fuel prices and station discovery. Agents can compare station availability near a location, inspect stations within an area, plan fuel-related routes, and use geocoding as part of location-based requests. The connected Pumperly data can also support finding nearby EV charging stations.

Limitations and notes

The server reads Pumperly anonymously and does not use an API key. Its data depends on the selected Pumperly instance, whether that is the public service or a custom deployment. Resource access is read-only, and the HTTP transport uses the /mcp path rather than multiple service endpoints. Client configuration must support the MCP mcpServers format for the stdio example.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pumperly MCP

GeiserX/pumperly-mcp is an MCP server that connects AI agents to Pumperly fuel-price services. Its main tools find nearby or area-based stations, calculate routes, find stations along routes, and geocode places. It also exposes read-only configuration, statistics, and exchange-rate resources.

Install it for stdio by adding an MCP configuration that runs `npx -y pumperly-mcp` and sets `PUMPERLY_URL`. The npm package retrieves the appropriate release binary for the platform. Docker, Docker Compose, and source-build setup paths are also available.

Set `PUMPERLY_URL` to the address of the Pumperly instance you want to query. The same configuration pattern can target the public service at `https://pumperly.com` or an independently hosted Pumperly deployment.

Yes, GeiserX/pumperly-mcp works with Cursor through the standard `mcpServers` configuration format. Use the stdio setup with `npx`, provide `PUMPERLY_URL`, and add the server to Cursor’s MCP configuration.

Run the Docker image and connect to its `/mcp` endpoint, which the documented setup uses on port 8080. The server also supports stdio when an MCP client should launch it locally.

Related MCP servers

All in Travel & Transportation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPumperly MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/geiserx-pumperly-mcp?style=directory)](https://allmcps.com/mcp/geiserx-pumperly-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/geiserx-pumperly-mcp"><img src="https://allmcps.com/api/badge/geiserx-pumperly-mcp?style=directory" alt="Pumperly MCP on AllMCPs" /></a>