Skip to main content
Glama
Park & Keep MCP Server
by tresor4k

Park & Keep MCP server

MCP server (local stdio or remote Streamable HTTP, stateless, read-only, no account) answering questions about the Park & Keep airport parking index: car parks serving European airports, their services and airport-level price ranges for 3, 7 and 14-day stays.

Endpoint once deployed: https://parkandkeep-mcp.vercel.app/mcp (registry name io.github.tresor4k/parkandkeep-mcp).

Local (stdio)

npx -y parkandkeep-mcp

Claude Desktop (claude_desktop_config.json):

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

The stdio server registers the same tools as the remote endpoint and reads the index bundled in the package.

Related MCP server: MCP Parking Server

Remote

Streamable HTTP endpoint: https://parkandkeep-mcp.vercel.app/mcp.

Tool

Returns

airport_parking_options

Car parks of an airport: services (shuttle, valet, covered, 24 h, keys kept, EV charging, online booking), distance, date checked. No price.

airport_price_snapshot

Min / median / max public price per stay length and currency, only from 3 prices, with the dates read. Never a price per operator.

airport_market_snapshot

Number of car parks, shares with shuttle / valet / covered parking, median and shortest distance, number with prices.

Each tool takes airport = IATA code or airport name. The only outbound link is the airport page on parkandkeep.com (utm_source=mcp); no affiliate or partner link.

npm install
npm test            # build + local HTTP smoke test (tools/list and every tool on 3 airports) + stdio smoke test
npm start           # http://127.0.0.1:8787/mcp

Data: src/data/index.json and src/data/hubs.json are written by ../sync.mjs; do not edit them by hand. Licences: code MIT (LICENSE); data CC BY 4.0, credit Park & Keep.

Available Tools

3 tools
airport_market_snapshotAirport parking market snapshotA
Read-onlyIdempotent
Inspect

Use this when a car park operator or analyst asks about the parking market around a European airport: how many car parks compete there, the share offering a shuttle, valet or covered parking, the median and shortest distance to the airport, and how many have published prices. Phrasings: "how many parking competitors at Eindhoven airport", "share of valet parkings at Orly", "concurrence parking aéroport Bordeaux". Data: Park & Keep airport parking index.

Inputs: airport (required).

airport_parking_optionsAirport parking optionsA
Read-onlyIdempotent
Inspect

Use this when the user wants to know which car parks serve a European airport and what they offer: shuttle, valet, covered parking, 24 h access, keys kept, EV charging, online booking, distance to the airport and the date each listing was checked. Phrasings: "parking near Charleroi airport with a shuttle", "valet parking at Brussels airport", "où se garer près d'Orly". Returns no price: for prices use airport_price_snapshot. Data: Park & Keep airport parking index.

Inputs: airport (required).

airport_price_snapshotAirport parking price snapshotA
Read-onlyIdempotent
Inspect

Use this when the user asks how much parking costs at a European airport for a stay of about 3, 7 or 14 days, or whether a parking price is normal there. Phrasings: "how much is a week of parking at Brussels airport", "prix parking Charleroi 7 jours", "is my quote for a week at Amsterdam airport expensive". Returns the lowest, median and highest public price of the airport's car parks per stay length, only when at least 3 prices were read, with the dates read. Never a price per operator. Data: Park & Keep airport parking index.

Inputs: airport (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool answers a different question: what car parks exist at an airport, what a stay costs, and how competitive the local market is. The two 'snapshot' tools share the same underlying index and could be momentarily confused, but the descriptions sharply separate consumer price questions from operator/analyst market questions, and each explicitly cross-references the others.

    Naming Consistency5/5

    All three tools use the same airport_<subject>_<noun> snake_case pattern with no deviations. The suffixes (options, price_snapshot, market_snapshot) are predictable and self-describing.

    Tool Count4/5

    Three tools is on the lean side but appropriate for a narrow, read-only data index where each tool maps to a distinct user intent. Nothing feels padded and no obvious query type is missing from the surface.

    Completeness3/5

    Coverage is reasonable for a read-only price/listing index, but there are dead ends: no way to look up a single named car park's details, no airport/country browse or discovery tool, and no per-operator pricing. Agents asking about one specific lot or an unsupported airport have nowhere to go.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for querying parking management systems using natural language and secure SQL. It enables searching for parking locations, retrieving billing configurations, and understanding database schemas through business context tools.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying current and historical retail petrol, diesel, and LPG prices across European countries, comparing prices by week, and checking data coverage.
      141 npm
      MIT