Google Maps Directions

io.github.johnisanerd由 GitHub 账号 johnisanerd 发布v1.0.0更新于 Nov 3, 2026

通过 Apify Directions API（托管的 MCP）获取 Google 地图路线、预计到达时间和逐向导航步骤。

AI 翻译由 AI 模型根据下方的原文描述翻译，可能有误。

原文描述

Google Maps routes, ETAs, and turn-by-turn steps via the Apify Directions API, hosted MCP.

已验证Streamable HTTP可网页运行

概览

Google Maps Directions 的托管 MCP 服务（mcp.apify.com）；需要 OAuth 登录；Streamable HTTP。

暂无 AI 概览：以下信息来自注册中心条目和服务本身。

端点
mcp.apify.com
最近检查

安装

在 SourceWeft 中

  1. 打开 控制台中的 Google Maps Directions，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.johnisanerd%2Fgoogle-maps-directions/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "google-maps-directions": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=johnvc/google-maps-directions-api"
    }
  }
}

README

🗺️ Google Maps Directions API: routes, ETA, and turn-by-turn steps as JSON

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.

Video Walkthrough

[Watch the walkthrough]

Quick Start

Prerequisites

  1. Clone the repository

    bash
    git clone https://github.com/johnisanerd/Apify-Google-Maps-Directions-API.gitcd Apify-Google-Maps-Directions-API

  2. Install dependencies with UV

    bash
    # Install UV if you do not have it:curl -LsSf https://astral.sh/uv/install.sh | sh
# Install project dependencies:uv sync

  3. Configure your API key

    bash
    cp .env.example .env# Edit .env and add your Apify API key# Get your free API key at: https://apify.com?fpr=9n7kx3

  4. Run the example

    bash
    uv run python google-maps-directions-api-example.py

Alternative: set the API key directly

bash
export APIFY_API_TOKEN="your_api_key_here"uv run python google-maps-directions-api-example.py

Explore every input

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.

Why Use This Google Maps Directions API?

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).

Features

Core Capabilities

  • Driving, transit, walking, cycling, flight, and two-wheeler routing
  • Distance, ETA, and traffic-aware duration ranges
  • Turn-by-turn steps per leg, with per-step distance and duration
  • Transit stops, lines, operators, and departure/arrival times
  • Resolved origin/destination addresses, place IDs, and GPS coordinates
  • A direct Google Maps link for each route

Data Quality

  • Clean, consistent JSON with one row per lookup
  • Real units, formatted and raw (meters/seconds plus human-readable strings)
  • Country and language targeting for localized place names and instructions

Usage Examples

Basic Example

json
{  "start_addr": "New York, NY",  "end_addr": "Boston, MA"}

Advanced Example

json
{  "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"}

Run every input from Python (cookbook)

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:

bash
uv run python google-maps-directions-api-cookbook.py            # runs 'basic'uv run python google-maps-directions-api-cookbook.py walkinguv run python google-maps-directions-api-cookbook.py all        # runs every example (each is billed)
ExampleWhat it shows
basicBest routes across all modes (the default)
drivingDriving only, distances in miles
walkingWalking directions
cyclingCycling directions
two_wheelerTwo-wheeler (motorcycle/scooter; select regions like India)
transitPublic transit directions
transit_advancedTransit with arrive-by time, preferred mode, and less walking
flightFlight option for a long-haul route
coordinatesOrigin and destination as latitude,longitude
place_idsOrigin and destination as Google Maps place IDs
avoidAvoid tolls, highways, and ferries
depart_atFuture departure time (traffic-aware ETA)
localizedKilometers and French instructions

Input Parameters

Provide an origin (an address, coordinates, or a place ID) and a destination.

ParameterTypeRequiredDefaultDescription
start_addrstrone of origin-Origin address or place name.
end_addrstrone of dest-Destination address or place name.
start_coordsstrno-Origin as latitude,longitude. Overrides start_addr.
end_coordsstrno-Destination as latitude,longitude. Overrides end_addr.
start_data_idstrno-Origin Google Maps place ID. Overrides start_addr.
end_data_idstrno-Destination Google Maps place ID. Overrides end_addr.
travel_modestrnobestbest, driving, cycling, walking, transit, flight, two-wheeler.
distance_unitstrnoautoauto, km, or miles.
avoid_tollsboolnofalsePrefer routes without toll roads.
avoid_highwaysboolnofalsePrefer routes that avoid highways.
avoid_ferriesboolnofalsePrefer routes that avoid ferries.
transit_preferstrnononebus, subway, train, tram, or light_rail (transit only).
transit_routingstrnononefewer_transfers, less_walking, or wheelchair (transit only).
time_typestrnoleave_nowleave_now, depart_at, or arrive_by.
time_valuestrno-ISO 8601 datetime or Unix timestamp, used with depart_at / arrive_by.
hlstrnoenInterface language code (ISO 639-1).
glstrnousCountry code (ISO 3166-1).

Output Format

One row per run. Trimmed example for New York, NY to Boston, MA:

json
{  "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 .

Install in Claude Cowork Desktop

[Install in Claude Cowork Desktop]

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.

  1. Open the Claude desktop app and go to Settings → Connectors (or Settings → Developer → Edit Config to edit claude_desktop_config.json directly).
    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Add the Apify MCP server, preloaded with only this Actor:
json
{  "mcpServers": {    "apify": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api"      ]    }  }}
  1. Restart the app. When Cowork first calls the tool, complete the OAuth prompt in your browser, or add your Apify API token in the connector settings to skip OAuth.
  2. In a Cowork chat, confirm the tool is available and ask it to run the 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

Install in Claude Code

[Install in Claude Code]

Claude Code is the command-line tool. Add the Actor's MCP server with one command:

bash
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:

bash
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 free: https://claude.ai/referral/uIlpa7nPLg Claude Code MCP docs: https://code.claude.com/docs/en/mcp

Install in Claude (website)

[Install in Claude (website)]

On claude.ai you add Apify as a connector, then enable just this Actor's tool.

  1. Go to Settings → Connectors → Browse connectors and search for Apify MCP server. Install it (enable or update if prompted).
  2. When connecting, authenticate with your Apify API token, and enable the tool johnvc/google-maps-directions-api.
  3. In any chat, open + → Connectors and turn on Apify.
  4. Alternatively, choose Add custom connector and paste the full MCP URL https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api, using OAuth when prompted.
  5. Ask Claude to run the Google Maps Directions API.

Open Claude on the web: https://claude.ai/referral/uIlpa7nPLg

Install in Cursor

[Install in Cursor]

Cursor reads MCP servers from a project file at .cursor/mcp.json.

  1. In your project, create .cursor/mcp.json:
json
{  "mcpServers": {    "apify": {      "url": "https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api"    }  }}
  1. If you prefer token auth over browser OAuth, add a header:
json
{  "mcpServers": {    "apify": {      "url": "https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api",      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }    }  }}
  1. Open Cursor → Settings → MCP and confirm the apify server is connected (green dot).
  2. In Composer or Chat, ask Cursor to call the Google Maps Directions API.

New to Cursor? Get it here: https://cursor.com/referral?code=XQP4VBLI3NNX

Install in ChatGPT

[Install in ChatGPT]

ChatGPT connects to the Apify MCP server through Developer mode (available on ChatGPT Pro, Plus, Business, Enterprise, and Education plans).

  1. Click your profile icon, then go to Settings > Apps. If you do not see a Create app button, open Advanced settings and enable Developer mode.
  2. Click Create app and fill out the form:
    • Name: Apify
    • MCP Server URL: https://mcp.apify.com/?tools=actors,docs,johnvc/google-maps-directions-api
    • Authentication: OAuth
  3. Click Create and authorize the connection with Apify.
  4. To use the app in a conversation, click + in the chat, choose Developer mode, and select Apify.

More help: https://docs.apify.com/platform/integrations/mcp

Made with care

Use the Google Maps Directions API to power your routing, logistics, and travel workflows with reliable, structured results.

🤖 Ask an AI assistant about this Actor

Open a ready-to-send prompt about the Google Maps Directions API in the AI of your choice:

Last Updated: 2026.10.27

来源：README.md，提交 711dacd

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Nov 3, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。