Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Google Maps routes, ETAs, and turn-by-turn steps via the Apify Directions API, hosted MCP.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://mcp.apify.com/?tools=johnvc/google-maps-directions-apiEjecuta esto en tu terminal
claude mcp add --transport http google-maps-directions 'https://mcp.apify.com/?tools=johnvc/google-maps-directions-api'Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"google-maps-directions": {
"url": "https://mcp.apify.com/?tools=johnvc/google-maps-directions-api"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"google-maps-directions": {
"type": "http",
"url": "https://mcp.apify.com/?tools=johnvc/google-maps-directions-api"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://mcp.apify.com/?tools=johnvc/google-maps-directions-apiLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
El servidor pide iniciar sesión antes de mostrar sus herramientas.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub johnisanerd, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 107 ms (HTTP 401)
Declara inicio de sesión con OAuth, así que tu app de IA puede llevarte a iniciar sesión
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (1.0.0) llegó al registro hace 4 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
The most efficient, reliable, and developer-friendly way to use the Google Maps Directions API.
Actor page: apify.com/johnvc/google-maps-directions-api Input schema: apify.com/johnvc/google-maps-directions-api/input-schema
Call the Google Maps Directions API from Python or from any MCP client and get directions between an origin and a destination as clean, structured JSON: route options for driving, transit, walking, cycling, and flight, with distance, ETA, traffic-aware duration ranges, resolved place coordinates, turn-by-turn steps, and a direct Google Maps link. Provide addresses, GPS coordinates, or place IDs.
git clone https://github.com/johnisanerd/Apify-Google-Maps-Directions-API.git
cd Apify-Google-Maps-Directions-API
# Install UV if you do not have it:
curl -LsSf https://astral.sh/uv/install.sh | sh
uv sync
cp .env.example .env
uv run python google-maps-directions-api-example.py
export APIFY_API_TOKEN="your_api_key_here"
uv run python google-maps-directions-api-example.py
Once the basic run works, google-maps-directions-api-cookbook.py is a runnable catalog of every feature (all travel modes, coordinates and place-ID inputs, avoidance, units, localization, and transit time and routing). See the cookbook table under "Usage Examples" below.
Every travel mode in one call. Ask for the best options across modes, or pin a single mode: driving, transit, walking, cycling, flight, or two-wheeler. One request returns every route option Google offers for your origin and destination.
Turn-by-turn detail, structured. Each route option carries distance, duration, a traffic-aware typical duration range, a route summary, route notes (tolls, conditions), and trips broken down into individual turn-by-turn steps. Transit options include stops, lines, operators, and times.
Flexible inputs. Set your origin and destination as an address or place name, exact GPS coordinates, or a Google Maps place ID. Choose units, avoid tolls, highways, or ferries, tune transit routing, and set a departure or arrival time.
Predictable pricing. A single route lookup is one flat charge. No surprise per-step or per-byte billing.
Built for agents. The Actor is MCP-ready, so you can load it as a tool in Claude or Cursor and ask for directions in plain language (see the install sections below).
{
"start_addr": "New York, NY", "end_addr": "Boston, MA" }
{
"start_addr": "Brooklyn, NY", "end_addr": "Times Square, New York, NY", "travel_mode": "transit", "transit_routing": "less_walking", "time_type": "arrive_by", "time_value": "2026-06-01T09:00:00", "distance_unit": "miles", "hl": "en", "gl": "us" }
google-maps-directions-api-cookbook.py is a runnable catalog that exercises every input the API supports, with a clean printed summary per route. Run one example by name, or all:
uv run python google-maps-directions-api-cookbook.py # runs 'basic'
uv run python google-maps-directions-api-cookbook.py walking uv run python google-maps-directions-api-cookbook.py all # runs every example (each is billed)
| Example | What it shows |
|---|---|
basic | Best routes across all modes (the default) |
driving | Driving only, distances in miles |
walking | Walking directions |
cycling | Cycling directions |
two_wheeler | Two-wheeler (motorcycle/scooter; select regions like India) |
transit | Public transit directions |
transit_advanced | Transit with arrive-by time, preferred mode, and less walking |
flight | Flight option for a long-haul route |
coordinates | Origin and destination as latitude,longitude |
place_ids | Origin and destination as Google Maps place IDs |
avoid | Avoid tolls, highways, and ferries |
depart_at | Future departure time (traffic-aware ETA) |
localized | Kilometers and French instructions |
Provide an origin (an address, coordinates, or a place ID) and a destination.
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
start_addr | str | one of origin | - | Origin address or place name. |
end_addr | str | one of dest | - | Destination address or place name. |
start_coords | str | no | - | Origin as latitude,longitude. Overrides start_addr. |
end_coords | str | no | - | Destination as latitude,longitude. Overrides end_addr. |
start_data_id | str | no | - | Origin Google Maps place ID. Overrides start_addr. |
end_data_id | str | no | - | Destination Google Maps place ID. Overrides end_addr. |
travel_mode | str | no | best | best, driving, cycling, walking, transit, flight, two-wheeler. |
distance_unit | str | no | auto | auto, km, or miles. |
avoid_tolls | bool | no | false | Prefer routes without toll roads. |
avoid_highways | bool | no | false | Prefer routes that avoid highways. |
avoid_ferries | bool | no | false | Prefer routes that avoid ferries. |
transit_prefer | str | no | none | bus, subway, train, tram, or light_rail (transit only). |
transit_routing | str | no | none | fewer_transfers, less_walking, or wheelchair (transit only). |
time_type | str | no | leave_now | leave_now, depart_at, or arrive_by. |
time_value | str | no | - | ISO 8601 datetime or Unix timestamp, used with depart_at / arrive_by. |
hl | str | no | en | Interface language code (ISO 639-1). |
gl | str | no | us | Country code (ISO 3166-1). |
One row per run. Trimmed example for New York, NY to Boston, MA:
{
"result_type": "directions", "start": "New York, NY", "end": "Boston, MA", "travel_mode": "best", "directions_found": true, "directions_count": 3, "best_duration": "3 hr 38 min", "best_distance": "215 miles", "places_info": [ { "address": "New York", "data_id": "0x89c24fa5d33f083b:0xc80b8f06e177fe62", "gps_coordinates": { "latitude": 40.7127753, "longitude": -74.0059728 } }, { "address": "Boston, Massachusetts", "data_id": "0x89e3652d0d3d311b:0x787cbf240162e8a0", "gps_coordinates": { "latitude": 42.3555076, "longitude": -71.0565364 } } ], "directions": [ { "travel_mode": "Driving", "via": "CT-15 N and I-90 E", "distance": 346243, "duration": 13082, "formatted_distance": "215 miles", "formatted_duration": "3 hr 38 min", "typical_duration_range": "3 hr 21 min to 4 hr 10 min", "extensions": ["Fastest route now due to traffic conditions", "This route has tolls."], "trips": [ { "travel_mode": "Driving", "title": "Get on FDR Dr", "formatted_distance": "0.9 mi", "formatted_duration": "5 min", "details": [ { "title": "Head toward Park Row", "action": "straight", "formatted_distance": "200 ft", "formatted_duration": "21 sec" } ] } ] } ], "durations": [ { "travel_mode": "Driving", "formatted_duration": "3 hr 38 min" }, { "travel_mode": "Transit", "formatted_duration": "4 hr 25 min" }, { "travel_mode": "Flight", "formatted_duration": "1 hr 15 min" } ], "google_maps_directions_url": "https://www.google.com/maps/dir/...", "gl": "us", "hl": "en", "fetched_at": "2026-05-29T12:00:00+00:00" }
This Actor is MCP-server-compatible, so AI assistants can call the Google Maps Directions API as a tool through Apify's hosted MCP server.
The Actor's MCP server URL is always built with the actors and docs helper tools plus this one Actor:
https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api
The actors and docs tools let the assistant discover and read Apify docs, while preloading just this one Actor keeps the tool list small. Auth is either OAuth in the browser when offered, or your Apify API token (the same APIFY_API_TOKEN secret used by the Python example). Get a token at https://console.apify.com/settings/integrations and a free Apify account at https://apify.com?fpr=9n7kx3 .
Cowork is the desktop app's automation mode. To give it the Google Maps Directions API as a tool, add the Apify MCP server as a connector.
claude_desktop_config.json directly).~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": { "apify": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api" ] } } }
Download the desktop app and start a free trial: https://claude.ai/referral/uIlpa7nPLg More help: https://docs.apify.com/platform/integrations/claude-desktop
Claude Code is the command-line tool. Add the Actor's MCP server with one command:
claude mcp add --transport http apify \
"https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api"
To use a token instead of browser OAuth:
claude mcp add --transport http apify \
"https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api" \ --header "Authorization: Bearer YOUR_APIFY_TOKEN"
Then verify with claude mcp list, or run /mcp inside a session. Ask Claude Code to call the Google Maps Directions API.
Try Claude Code fr
Solo se muestra el principio; lee el resto en el repo