Fuel MCP Server

Gas and fuel prices by station and area, as structured data via a hosted MCP server. The fuel mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

The Fuel Prices API returns live, crowd-reported gas station prices and station metadata for any US location (with some Canadian coverage) as clean, structured JSON. Search by ZIP code, city name, or GPS coordinates and get one record per station: name, full address, distance from your search point, cash and credit prices with posting timestamps, price unit, and ratings. Choose the fuel type (regular, midgrade, premium, diesel, E85, or unleaded 88) and filter by data freshness.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — 1. Clone the repository bash git clone https://github.com/johnisanerd/Apify-Fuel-Prices-Scraper.git cd Apify-Fuel-Prices-Scraper

Configuration

You will need 2 environment variables: APIFY_API_TOKEN, YOUR_APIFY_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.11 or higher - An Apify account and API key (get a free key here) 1. Clone the repository 2. Install dependencies with UV 3. Configure your API key 4. Run the example

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the fuel mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Fuel's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by johnisanerd; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Fuel's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.