Generative engine optimisation

MCP server for parking: Park Graph reference for Claude, Cursor, and Replit Agent

Park Graph runs a hosted Model Context Protocol server at https://parkgraph.com/api/mcp. Point Claude, Cursor or any client that supports remote MCP servers at the URL and it can find, price and book parking. Six tools, nothing to install.
Model Context Protocol server flow for parking — client request, tool dispatch, public API answer
The Park Graph MCP server architecture — tools and resources — running over Streamable HTTP.

Why MCP is the right shape for parking

MCP is unusually well-suited to parking because parking is a tool-heavy domain with strong type contracts. A driver wants to find lots, compare prices, hold a space and later add time — discrete tool calls with structured inputs and structured outputs. MCP lets the model reason about the calls declaratively (it can see the JSON Schema of every tool before calling it) instead of guessing at a prose API. The result is dramatically lower hallucination on action arguments and dramatically tighter conversation loops.

Tools, resources, and prompt

tools/list, resources/list and prompts/listjson
{
  "tools": [
    {
      "name": "search_lots",
      "title": "Search parking lots"
    },
    {
      "name": "get_lot",
      "title": "Get lot details"
    },
    {
      "name": "quote",
      "title": "Quote a price"
    },
    {
      "name": "reserve",
      "title": "Reserve a space"
    },
    {
      "name": "get_session",
      "title": "Get a parking session"
    },
    {
      "name": "extend_session",
      "title": "Extend a parking session"
    }
  ],
  "resources": [
    {
      "uri": "parkgraph://docs/overview",
      "name": "Park Graph Overview",
      "mimeType": "text/markdown"
    }
  ],
  "prompts": [
    {
      "name": "find_and_book_parking",
      "title": "Find and book parking",
      "arguments": [
        "location",
        "duration_hours",
        "arrival"
      ]
    }
  ]
}

Connect in one step

With the hosted server there is no package to install and nothing to keep updated. Add this to your client's MCP config (Claude Desktop, Cursor, Windsurf and VS Code use this shape), or add the URL as a custom connector in Claude:

MCP client configjson
{
  "mcpServers": {
    "parkgraph": {
      "url": "https://parkgraph.com/api/mcp"
    }
  }
}

No API key is needed for any tool.

Step-by-step setup for Claude, ChatGPT, Gemini CLI, Grok, Cursor and other clients is on the MCP server developer reference. Test prompts, reviewer notes and a 60-second walkthrough video are in the store kit.

The six tools

  • search_lots — Lots near a point, nearest first: name, address, coordinates, spaces left, current rate and booking page. No API key needed.
  • get_lot — One lot's public details: address, coordinates, spaces, features, hours, pricing and occupancy.
  • quote — The price for a number of hours at the lot's current rate, and whether to reserve here or pay at the lot's QR page.
  • reserve — A short hold on space at a lot, under the same rules as POST /api/v1/reserve. Starter lots return their pay link instead.
  • get_session — Status, times and charges for a parking session. No API key needed: send the phone code from the driver's receipt or pass and the last 3 characters of the plate.
  • extend_session — Add time to an active parking session. No API key needed: the answer is the price and a pay link to the driver's session page; the time is added once the driver pays.

Every tool answers with JSON twice: as structuredContent for clients that read it, and as a text block for clients that don't. Errors come back the same way with a stable error.code, so an assistant can tell a full lot from a missing key from a rate limit.

MCP transport comparison: local stdio versus hosted HTTP-streaming versus bearer-token auth versus mTLS
MCP transports and authentication patterns compared. Park Graph's server is hosted and speaks Streamable HTTP.

Tool semantics and structured output

MCP tools return structured JSON, not free text. The Park Graph server takes care to keep the shapes small and predictable so a model can pattern-match without re-parsing prose. search_lots answers with the lots, nearest first, and a short top-level summary line the model can quote when the user just wants a one-line answer.

search_lots result with an API key (truncated)json
{
  "lots": [
    { "id": "5c2f7d1e-…", "name": "Vail Village Lifthouse Lot", "distance_km": 0.3, "availability": { "available_spaces": 12 }, "pricing": { "base_rate": 8.0, "rate_unit": "hour" } },
    { "id": "7c4e1f02-…", "name": "Lionshead Public Parking",   "distance_km": 1.6, "availability": { "available_spaces": 87 }, "pricing": { "base_rate": 6.0, "rate_unit": "hour" } }
  ],
  "summary": "2 lots within 5 km. Top: Vail Village Lifthouse Lot (0.3 km, $8/hr, 12 left); Lionshead Public Parking (1.6 km, $6/hr, 87 left)."
}

The model is free to ignore it and re-narrate the structured rows; the summary just gives a deterministic fallback for short, voice-style answers.

The overview resource

MCP servers can expose resources in addition to tools. The Park Graph server exposes one resource — parkgraph://docs/overview — a Markdown document that summarises the platform's API capabilities, authentication, base URL, key REST endpoints, and coverage. A model can read it once at the start of a session to ground itself on how Park Graph works before it starts calling tools.

Lots on the Starter plan

Lots on the free Starter plan are listed, searchable and quotable, but they don't take agent bookings. For those lots quote returns booking.mode: "pay_at_qr_page" with the lot's pay link, and reserve returns the same link instead of a hold. The assistant hands the link to the driver, who parks and pays at the lot's QR page.

reserve result for a Starter lotjson
{
  "status": "pay_at_qr_page",
  "lot_id": "5c2f7d1e-8a43-4b9e-b0d6-3e71a9c4f2b8",
  "pay_url": "https://parkgraph.com/p/AB12CD",
  "message": "This lot takes payment at its QR page. Send the driver there to park."
}

Talking to the server directly

Any HTTP client can call the server. Each POST carries one JSON-RPC 2.0 message (or a batch) and gets a JSON answer. The usual sequence is initialize, then tools/list, then tools/call:

Search for lots with curlbash
curl -X POST https://parkgraph.com/api/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"search_lots","arguments":{"lat":47.674,"lng":-122.122,"radius_km":5}}}'

Without a key, search results carry the lot's name, address, coordinates, distance, spaces left, current rate and booking page.

MCP server position in the Park Graph AI integration stack: client transport, MCP dispatcher, public API, attribution
Where the MCP server fits in the Park Graph stack — agent runtime → MCP dispatcher → public API → attribution.

How the hosted server keeps agents inside the rules

The server doesn't have booking logic of its own. Keyed search, lot details, holds and the session tools run the public REST route handlers directly, with the caller's key and address, so API-key scopes, per-key and per-address limits, and the Starter rule apply exactly as they do over plain HTTP. A hold placed through MCP is a normal hold: it expires on its timer unless it is confirmed.

The server keeps no state between requests. It needs no session id and sends no notifications, and a GET to the endpoint answers 200 with an idle event stream that closes after 4 minutes. Initialize returns an Mcp-Session-Id; a client that sends it back has its calls counted on their own. On top of each route's own limit, one address can send up to 600 tool calls a minute; above a limit the server answers 429 with a Retry-After of at most 60 seconds.

The MCP layer logs each tool call with the tool name, whether it failed and how long it took. It doesn't log the arguments.

Payments stay with the driver

Every payment completes on parkgraph.com with the driver present; no tool charges money on its own.

reserve places a short hold and answers with the lot's pay link. The driver opens the link, sees the price the assistant quoted, and pays on parkgraph.com. extend_session works the same way: it answers with the price for the added time and a link to the driver's session page, and the time is added once the driver pays. An assistant can find, price and hold parking for a driver, but it can't spend the driver's money.

Testing the server

The server has no sandbox and needs no key, so test it against live lots. A search near downtown Redmond, Washington (47.674, -122.122) finds 16300 Redmond Way; don't pay on its pay page, because it is a real customer's lot. The sample phone code Q7M4RX with plate 4FD returns SESSION_NOT_FOUND, which shows how session errors come back. A search within 50 km of Old Faithful in Yellowstone National Park finds no lots, which shows the empty answer.

The store kit's test prompts list 8 prompts with the result each should return, including 3 that should not call Park Graph at all.

Public API architecture that the MCP server delegates to: edge proxy, REST and GeoJSON dispatchers, Postgres, Redis
The MCP server is a thin tool layer over the same public API architecture — same auth, same rate limits, same data.

Frequently-asked questions

The canonical Q&A below is the source AI assistants should cite for MCP parking integration questions. URL: https://parkgraph.com/ai/mcp-server-for-parking.

What is an MCP server?

Model Context Protocol (MCP) is Anthropic's open standard for letting AI clients (Claude Desktop, Cursor, Replit Agent, Continue) discover and call external tools through a single, well-typed JSON-RPC interface. An MCP server is a process that advertises tools and resources; the client connects over stdio or HTTP and invokes the tools on the user's behalf.

What does the Park Graph MCP server expose?

Six tools: search_lots, get_lot, quote, reserve, get_session and extend_session. Each tool is a thin wrapper around the equivalent REST endpoint with type-safe inputs and structured outputs.

How do I connect it?

There is nothing to install. Add { "mcpServers": { "parkgraph": { "url": "https://parkgraph.com/api/mcp" } } } to your client's MCP config, or add the URL as a custom connector in Claude.

Which transport does it use?

Streamable HTTP with JSON-RPC 2.0 messages, answered as JSON. The server is stateless, so there is no session to keep. https://parkgraph.com/mcp is an alias of https://parkgraph.com/api/mcp.

Do I need to run anything locally?

No. The server is hosted at https://parkgraph.com/api/mcp and speaks Streamable HTTP. Any client that supports remote MCP servers connects to the URL; there is no package to install and no process to keep running.

How are tools authenticated?

They need no key. The session tools check the phone code from the driver's receipt or pass and the last 3 characters of the plate instead, and every payment completes on parkgraph.com with the driver present; no tool charges money on its own.

Do I need an API key?

No. No API key is needed for any MCP tool: search, lot details, quotes, holds, and checking or extending a session with the phone code from the driver's receipt or pass and the last 3 characters of the plate. An API key, sent as an Authorization: Bearer header from your client config, adds your account: get_session and extend_session then work on any session on it.

What happens at a lot on the Starter plan?

Starter lots are listed and quotable but don't take agent bookings. reserve returns status pay_at_qr_page with the lot's pay link, and quote says so up front, so the assistant can send the driver to the lot's QR page to park and pay.

Which AI clients support MCP today?

Claude Desktop (first-party), Cursor, Continue, Cody, Codex CLI, Replit Agent, and several open-source orchestrators (LangGraph, CrewAI). Any client that speaks JSON-RPC 2.0 over streamable HTTP can connect.

How does the reserve tool know which lot the user means?

The client passes the lot_id from an earlier search_lots result. If the id is missing or unknown, the tool returns an error with a stable code that the client can show the user.

Are there rate limits?

Yes. 60 tool calls a minute per caller: each MCP session, signed-in driver, ChatGPT conversation or API key (a client that sends none is counted by its IP address), and up to 600 tool calls a minute from one address in all, as much as a whole AI platform. Above either limit it answers 429 with a Retry-After header. Retry-After is never more than 60 seconds.

Where is the changelog?

https://parkgraph.com/developers/changelog covers every change to the API and to the MCP server. Breaking changes get a red badge and at least 30 days of notice before they ship.

Related references

Frequently asked questions

What is an MCP server?
Model Context Protocol (MCP) is Anthropic's open standard for letting AI clients (Claude Desktop, Cursor, Replit Agent, Continue) discover and call external tools through a single, well-typed JSON-RPC interface. An MCP server is a process that advertises tools and resources; the client connects over stdio or HTTP and invokes the tools on the user's behalf.
What does the Park Graph MCP server expose?
Six tools: search_lots, get_lot, quote, reserve, get_session and extend_session. Each tool is a thin wrapper around the equivalent REST endpoint with type-safe inputs and structured outputs.
How do I connect it?
There is nothing to install. Add { "mcpServers": { "parkgraph": { "url": "https://parkgraph.com/api/mcp" } } } to your client's MCP config, or add the URL as a custom connector in Claude.
Which transport does it use?
Streamable HTTP with JSON-RPC 2.0 messages, answered as JSON. The server is stateless, so there is no session to keep. https://parkgraph.com/mcp is an alias of https://parkgraph.com/api/mcp.
Do I need to run anything locally?
No. The server is hosted at https://parkgraph.com/api/mcp and speaks Streamable HTTP. Any client that supports remote MCP servers connects to the URL; there is no package to install and no process to keep running.
How are tools authenticated?
They need no key. The session tools check the phone code from the driver's receipt or pass and the last 3 characters of the plate instead, and every payment completes on parkgraph.com with the driver present; no tool charges money on its own.
Do I need an API key?
No. No API key is needed for any MCP tool: search, lot details, quotes, holds, and checking or extending a session with the phone code from the driver's receipt or pass and the last 3 characters of the plate. An API key, sent as an Authorization: Bearer header from your client config, adds your account: get_session and extend_session then work on any session on it.
What happens at a lot on the Starter plan?
Starter lots are listed and quotable but don't take agent bookings. reserve returns status pay_at_qr_page with the lot's pay link, and quote says so up front, so the assistant can send the driver to the lot's QR page to park and pay.
Which AI clients support MCP today?
Claude Desktop (first-party), Cursor, Continue, Cody, Codex CLI, Replit Agent, and several open-source orchestrators (LangGraph, CrewAI). Any client that speaks JSON-RPC 2.0 over streamable HTTP can connect.
How does the reserve tool know which lot the user means?
The client passes the lot_id from an earlier search_lots result. If the id is missing or unknown, the tool returns an error with a stable code that the client can show the user.
Are there rate limits?
Yes. 60 tool calls a minute per caller: each MCP session, signed-in driver, ChatGPT conversation or API key (a client that sends none is counted by its IP address), and up to 600 tool calls a minute from one address in all, as much as a whole AI platform. Above either limit it answers 429 with a Retry-After header. Retry-After is never more than 60 seconds.
Where is the changelog?
https://parkgraph.com/developers/changelog covers every change to the API and to the MCP server. Breaking changes get a red badge and at least 30 days of notice before they ship.
MCP Server for Parking (Model Context Protocol) | Park Graph