Pumperly MCP Server

MCP server for Pumperly — query fuel prices, gas stations, route planning, and EV charging via the Model Context Protocol

Local serverstdioGo

What is the Pumperly MCP MCP server?

Connect Pumperly MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Pumperly — query fuel prices, gas stations, route planning, and EV charging via the Model Context Protocol. The pumperly mcp mcp server is what makes that connection.

What the server does

A tiny bridge that exposes any Pumperly instance as an MCP server, enabling LLMs to query real-time fuel prices, find stations, plan routes, and geocode locations.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Type — What for
  • Resources — Browse configuration, statistics, and exchange rates read-only
  • Tools — Find stations, calculate routes, and geocode locations
  • Variable — Default
  • PUMPERLY_URLhttps://pumperly.com
  • LISTEN_ADDR — 127.0.0.1:8080
  • TRANSPORT(empty = HTTP)
  • Project — Description

Credentials and setup notes

Configuration is passed through the environment: PUMPERLY_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as pumperly-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Pumperly MCP's toolset — Type, Resources, Tools and 5 more — is a fair guide to whether it matches your workflow. It is maintained by geiserx; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
TypeWhat for
ResourcesBrowse configuration, statistics, and exchange rates read-only
ToolsFind stations, calculate routes, and geocode locations
VariableDefault
PUMPERLY_URLhttps://pumperly.com
LISTEN_ADDR127.0.0.1:8080
TRANSPORT_(empty = HTTP)_
ProjectDescription

How to install the Pumperly MCP MCP server

{
  "mcpServers": {
    "pumperly": {
      "command": "npx",
      "args": ["-y", "pumperly-mcp"],
      "env": {
        "PUMPERLY_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
PUMPERLY_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Pumperly MCP to Type.
  • Use Pumperly MCP to Resources.
  • Use Pumperly MCP to Tools.

Frequently asked questions

It connects Pumperly MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Type, Resources, Tools, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Pumperly MCP directly.