MCP · Bay Area ride estimates

A clear fare estimate, wherever you plan.

Connect a remote Model Context Protocol client to request current website pricing for a private SUV ride around the San Francisco Bay Area, including airport trips at SFO, OAK and SJC, point-to-point rides and hourly service.

Remote MCP endpoint
https://www.blackcarservice.co/api/mcp
Streamable HTTP · POST · no authentication
01 — What it does

Plan your ride, then review it.

The fare tool, quote_ride, estimates SUV pricing using current website rates and returns the fare in USD cents, with the pickup time normalized to UTC in the response and a booking_url that prefills supported trip details on our booking page.

Use check_ride_availability with the same inputs to check tentative availability. It returns available, unavailable, or unknown; a calendar connection problem returns unknown. Neither tool holds a vehicle, makes a reservation, or takes payment. Quote attempts increment aggregate counters. Review your trip, final price, and availability on the website before booking.

Continue to booking
02 — Connect a client

Connect a compatible MCP client.

  1. 01

    Add a remote server using the endpoint above and the Streamable HTTP transport. No API key or sign-in is required.

  2. 02

    Initialize the MCP connection, list available tools, then call quote_ride with one of the input shapes below.

  3. 03

    Ask for an estimate for a future pickup. Use a full street address or airport and include the city and state.

View public MCP server manifest

Hermes and Grok setup

Hermes Agent

Merge this entry into the existing mcp_servers section of ~/.hermes/config.yaml, then start a new Hermes chat.

Hermes configuration
mcp_servers:
  bcs_quotes:
    url: "https://www.blackcarservice.co/api/mcp"
    tools:
      include: ["quote_ride", "check_ride_availability"]
Official Hermes instructions

Grok custom connector

In Grok’s Connectors page, choose New Connector, then Custom. Enter the endpoint above; BCS requires no authentication. Business accounts may need their administrator to add the connector first.

Developers can also use the xAI Responses API with an MCP tool whose server_url is our endpoint and allowed_tools is ["quote_ride", "check_ride_availability"]. xAI API usage is billed by xAI.

Official Grok connector instructions

The public endpoint has passed an MCP SDK connection and fare-estimate test. These product-specific setup steps follow their official documentation; Hermes and Grok application sessions have not been tested by BCS. Our server is listed in the official MCP Registry; individual clients decide which servers they offer or recommend.

03 — Request formats

Keep the request simple.

The dates below illustrate the format; replace them with the customer’s future pickup date. Every request needs a trip type, pickup and dropoff, an ISO 8601 pickup timestamp with its UTC offset, and 1–7 passengers. Clarify the intended local pickup time in California; daylight saving time changes the offset. Pickup dates must begin tomorrow in America/Los_Angeles.

Point-to-point · one-way
{
  "trip_type": "one-way",
  "pickup_address": "1 Ferry Building, San Francisco, CA",
  "dropoff_address": "1 Market Street, San Francisco, CA",
  "pickup_at": "2026-10-14T09:00:00-07:00",
  "passengers": 2
}
Airport · SFO, OAK or SJC
{
  "trip_type": "airport",
  "pickup_address": "Oakland San Francisco Bay Airport (OAK), Oakland, CA",
  "dropoff_address": "1 Market Street, San Francisco, CA",
  "pickup_at": "2026-10-14T09:00:00-07:00",
  "passengers": 2
}
Hourly · hours required
{
  "trip_type": "hourly",
  "pickup_address": "1 Market Street, San Francisco, CA",
  "dropoff_address": "1 Market Street, San Francisco, CA",
  "pickup_at": "2026-10-14T09:00:00-07:00",
  "passengers": 3,
  "hours": 4
}

For hourly service, repeat the pickup address as the destination when the ride returns there and provide hours from 1 to 24. Omit hours for one-way and airport trips. Stops, return legs, extras, promo codes and customer details are not supported.

04 — Fair use

Shared request limits.

Per IP address
30 requests / 5 min
All callers combined
300 requests / 5 min

When a limit is reached, the endpoint returns HTTP 429 with a Retry-After header. Respect that delay before trying again. Use a server-side MCP client runtime. Direct requests from other websites are not supported.