AI & developers

Closer agent integration — MCP, OpenAPI, and booking tools.

Closer publishes a public Model Context Protocol (MCP) server and OpenAPI specification so AI agents and integrators can estimate routes, check availability, calculate prices, and create Stripe checkout sessions — without scraping HTML.

Does Closer have MCP?

Yes. Closer operates an HTTP MCP endpoint at /api/mcp (version 0.2). It exposes five booking tools. Read operations require a bearer token with booking.read; checkout creation requires booking.write.

Why might ChatGPT say there is no MCP?

Standard ChatGPT chat (web browsing) does not automatically connect to third-party MCP servers. It searches and reads HTML pages. Unless an integrator configures MCP or OpenAPI actions, ChatGPT can only describe Closer from public pages — it cannot invoke tools autonomously. To use Closer tools inside ChatGPT, create a Custom GPT with Actions from openapi.json, or connect an MCP-compatible client to /api/mcp with an agent token.

Public discovery URLs

MCP tools

Call via POST /api/mcp with JSON-RPC 2.0 method tools/call and a valid Authorization: Bearer token.

ToolScopeDescription
booking.estimate_distancebooking.readEstimate route distance (km), duration (seconds), ETA, and Zone A eligibility. Mirrors /api/calculate-distance.
booking.check_availabilitybooking.readCheck whether a pickup datetime meets Closer lead-time rules (daytime >= 2h, night bookings from 09:00).
booking.calculate_pricebooking.readCalculate gross EUR price for a trip using Closer tariff tables. Requires distance (km), vehicle class, and booking type.
places.autocompletebooking.readAutocomplete address suggestions for pickup/destination fields. Mirrors /api/places-autocomplete.
booking.create_checkoutbooking.writeCreate a Stripe Checkout session for a confirmed booking. Returns sessionId and checkout URL. Requires booking.write scope.

Authentication

Agent tokens are configured server-side (AGENT_API_TOKENS_JSON). Request a token from Closer for integration testing. Scopes: booking.read (estimate, availability, price, autocomplete) and booking.write (create_checkout). Send x-agent-id and x-agent-system headers for attribution.

Quick start

  1. GET /api/mcp — list tools and input schemas.
  2. GET /openapi.json — full HTTP API documentation.
  3. GET /agent.json — scopes, CORS notes, and protocol links.
  4. POST /api/mcp with {"jsonrpc":"2.0","id":1,"method":"tools/list"} — JSON-RPC tool discovery.
  5. POST /api/mcp with tools/call + booking.read token to run booking.estimate_distance or booking.calculate_price.
curl -s https://www.closerchauffeur.com/api/mcp | jq .tools[].name

Agent FAQ

Does Closer have a public MCP server for AI agents?
Yes. The MCP HTTP endpoint is https://www.closerchauffeur.com/api/mcp. It supports tools/list and tools/call for distance estimation, availability checks, price calculation, address autocomplete, and Stripe checkout creation.
Does Closer have a public booking API?
Yes. OpenAPI 3.1 is published at https://www.closerchauffeur.com/openapi.json. Public routes include /api/calculate-distance, /api/places-autocomplete, /api/create-checkout-session, and /api/get-session-data. Agent-specific access uses bearer tokens with scoped permissions.
Can ChatGPT autonomously book a Closer ride today?
Not in default ChatGPT chat. Autonomous booking requires MCP or OpenAPI integration with a valid agent token (booking.write for checkout). Standard ChatGPT browsing can read this page and llms.txt but cannot invoke MCP tools unless configured as a Custom GPT Action or connected MCP client.
Where is the machine-readable agent documentation?
Start at https://www.closerchauffeur.com/for-agents (this page), https://www.closerchauffeur.com/llms.txt, https://www.closerchauffeur.com/agent.json, and https://www.closerchauffeur.com/openapi.json.
© 2026 Closer