Seat Sherpa

Find carpool rides in California and Nevada: live seats, times and all-in seat prices. Read-only.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
96%
Integridad del esquema
86%
Calidad de los nombres
92%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,454Tokens (definiciones de herramientas)
~1.4 KBTamaño de respuesta típico
Impacto moderado en la atención (1.14% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "rides": {
      "url": "https://seatsherpa.app/mcp"
    }
  }
}

Puntos de conexión remotos

https://seatsherpa.app/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (5)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢search_rides(from, to, date, days_flexible, limit)

Find upcoming long-distance carpool rides on Seat Sherpa (California and Nevada) where everyday drivers sell the empty seats on a trip they are already taking, and riders split the cost of gas. Give a starting place and a destination as city or place names (for example "San Francisco" and "Los Angeles"), and optionally a travel date. Returns rides with open seats: route, departure date and time (Pacific), seats left, the all-in price per seat in USD (what the rider pays, fees included), the driver's first name, and a link where the person books. Rides that stop in a city count for that city, so a San Jose to San Diego ride with a Los Angeles stop is found for Los Angeles to San Diego. Booking happens on the link; this tool cannot book. Rides on a nearby route (for example a San Francisco ride for a San Jose search) are listed separately as nearby_rides; say they are nearby, not exact. When no ride fits exactly, the answer includes a link to post a ride request for that route (the same link request_ride_link gives).

Esquema de entrada

{
  "type": "object",
  "properties": {
    "from": {
      "type": "string",
      "description": "Where the rider starts: a city or place in California or Nevada, e.g. \"San Francisco\", \"UC Davis\", \"Irvine\"."
    },
    "to": {
      "type": "string",
      "description": "Where the rider is going, e.g. \"Los Angeles\", \"Las Vegas\"."
    },
    "date": {
      "type": "string",
      "description": "Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-10 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
    },
    "days_flexible": {
      "type": "integer",
      "minimum": 0,
      "maximum": 7,
      "description": "With a date: also include rides this many days before and after it. Default 1."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 25,
      "description": "Most rides to return. Default 10."
    }
  },
  "required": [
    "from",
    "to"
  ],
  "additionalProperties": false
}
🟢get_ride(ride_id)

Public details of one Seat Sherpa ride by its id (from search_rides or a seatsherpa.app/ride link): route and stops with estimated times, departure (Pacific), seats left, all-in price per seat in USD, the driver's first name, rating and trips, the driver's note to riders, flexibility, the cancellation policy, and the booking link. Read-only.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "ride_id": {
      "type": "integer",
      "minimum": 1,
      "description": "The ride id."
    }
  },
  "required": [
    "ride_id"
  ],
  "additionalProperties": false
}
🟢list_service_areas

The California and Nevada areas Seat Sherpa carpools run between. Use it to check whether a trip is covered before searching.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢request_ride_link(from, to, date, seats)

For a rider when no ride fits: a link where the person posts a ride request on Seat Sherpa, the carpool marketplace, so drivers on that route see it and get notified, and the person hears back when a matching ride is posted. Use it after search_rides finds nothing that works (that answer already includes this link), or when the person asks to be told about a trip nobody has posted. Takes the same places and optional date as search_rides. The person signs in and posts the request on the page; this tool only builds the link, posts nothing, and never needs names, phone numbers or emails.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "from": {
      "type": "string",
      "description": "Where the rider starts: a city or place in California or Nevada, e.g. \"San Francisco\", \"UC Davis\", \"Irvine\"."
    },
    "to": {
      "type": "string",
      "description": "Where the rider is going, e.g. \"Los Angeles\", \"Las Vegas\"."
    },
    "date": {
      "type": "string",
      "description": "Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-10 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit and the person picks the date on the page."
    },
    "seats": {
      "type": "integer",
      "minimum": 1,
      "maximum": 4,
      "description": "Optional: seats the rider needs, 1 to 4. Only mentioned in the answer; the person picks it on the page."
    }
  },
  "required": [
    "from",
    "to"
  ],
  "additionalProperties": false
}
🟢post_ride_link(from, to, date)

For a driver: a link where the person posts a drive they are already taking on Seat Sherpa, the carpool marketplace. Drivers set their own seat price, riders share costs like gas and tolls, and riders searching that route get notified. Use it when the person is the one driving (for example "I'm driving to LA on Friday, can I take people?"), not to find a ride. Takes the starting place, the destination and an optional date. The driver signs in and posts on the page; this tool only builds the link and posts nothing.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "from": {
      "type": "string",
      "description": "Where the driver starts: a city or place in California or Nevada, e.g. \"San Francisco\", \"Irvine\"."
    },
    "to": {
      "type": "string",
      "description": "Where the driver is going, e.g. \"Los Angeles\", \"Las Vegas\"."
    },
    "date": {
      "type": "string",
      "description": "Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-10 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit and the driver picks the date on the page."
    }
  },
  "required": [
    "from",
    "to"
  ],
  "additionalProperties": false
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada5 herramientas