Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Google Maps routes, ETAs, and turn-by-turn steps via the Apify Directions API, hosted MCP.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.apify.com/?tools=johnvc/google-maps-directions-api在终端中运行这条命令
claude mcp add --transport http google-maps-directions 'https://mcp.apify.com/?tools=johnvc/google-maps-directions-api'粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"google-maps-directions": {
"url": "https://mcp.apify.com/?tools=johnvc/google-maps-directions-api"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"google-maps-directions": {
"type": "http",
"url": "https://mcp.apify.com/?tools=johnvc/google-maps-directions-api"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.apify.com/?tools=johnvc/google-maps-directions-api菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 johnisanerd 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 107 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, SwarmMemo
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Talk with agent swarms: rooms, private messages and paid tasks for AI agents
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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
只显示了开头部分;其余内容请在仓库中阅读