Park Graph

What Park Graph does

Park Graph MCP server gives an agent access to parking discovery and session workflows for Park Graph QR-pay lots. It can locate lots near a destination, return each lot’s current availability and rate, provide detailed lot information, calculate a parking price, and help a driver proceed with payment or reservation.

The service supports both pre-parking and in-progress parking tasks. Before arrival, an agent can find a suitable lot, inspect its address, features, hours, pricing, and remaining spaces, then request a quote. During an active stay, the agent can look up the session and request an extension.

How it works

Location search uses latitude and longitude. The agent should first determine the coordinates for the place the driver is visiting, then pass them to search_lots. Results are ordered from nearest to farthest and include spaces left and the current rate. An empty result means no Park Graph lot was found near those coordinates.

A lot ID returned by the search is used with quote, get_lot, and reserve. A quote applies the lot’s current rate and daily maximum for the requested number of hours. Its booking mode indicates the next step: some lots support a temporary hold through reserve, while others require payment at a QR page. For QR-payment lots, the response includes a URL to give the driver.

Reservations require driver confirmation before the reserve call. Where a hold is available, it lasts only a few minutes and must be confirmed before it expires. A hold confirmation is performed through the reservation workflow.

Tools and capabilities

• search_lots finds nearby lots and reports proximity, spaces remaining, and current rates.
• get_lot returns public lot details, including location, features, operating hours, pricing, and current availability.
• quote calculates the cost for a selected duration and identifies whether the driver should reserve or pay at a QR page.
• reserve places a short-lived hold when the lot supports holds. QR-payment lots return a payment-page result instead.
• get_session retrieves a session’s lot, status, times, rate, amount so far, extensions, and session-page link.
• extend_session requests between 0.5 and 8 additional hours in half-hour increments for an active hourly session.

Public lot search, detail, quoting, and the driver-verification forms of reservation and session access do not require an API key. Account-based session access can use an API key with sessions:read or sessions:write as appropriate.

Limitations and notes

The agent must obtain usable latitude and longitude before searching. It should not invent a lot when the search returns no results. Reservation support depends on the lot’s booking mode, and a QR-payment lot does not place a hold.

For unauthenticated session lookup or extension, the driver needs the six-character phone code from the receipt or pass and the last three characters of the vehicle plate. A mismatch returns SESSION_NOT_FOUND; the driver should verify both values. With an account API key, a session ID can be used for reading, and session ID plus session code can be used for extension.

An extension response supplies the price, new intended end time, and a payment URL. Payment is not charged and the session end time does not change until the driver pays through that page.