McpGmapDrivingTime
by 100shpaikco.huggingface.100shpaik/mcp-gmap-driving-time
Gradio App / MCP for simple traffic analysis via Google Maps
- Remote endpoint
- 1 tool
- MIT
Uptime
Checked · every day
100%from 4 days of checks
Up without downtime on 4 of 4 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1036 ms, slowest 5% 1224 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
1 tool at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No downtime | 1 | 1133 ms |
| 2 Nov | No downtime | 1of 1 | 1036 ms |
| 1 Nov | No downtime | 1of 1 | 839 ms |
| 31 Oct | No downtime | 1 | 1224 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse mcp-gmap-driving-time https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"mcp-gmap-driving-time": {
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"mcp-gmap-driving-time": {
"type": "sse",
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"mcp-gmap-driving-time": {
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"mcp-gmap-driving-time": {
"type": "sse",
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "mcp-gmap-driving-time"
type: sse
url: "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"mcp-gmap-driving-time":
type: streamable_http
name: "mcp-gmap-driving-time"
enabled: true
uri: "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add mcp-gmap-driving-time --url https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"mcp-gmap-driving-time": {
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"mcp-gmap-driving-time": {
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"mcp-gmap-driving-time": {
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server McpGmapDrivingTime (`co.huggingface.100shpaik/mcp-gmap-driving-time`)
Its page: https://plug.directory/servers/co.huggingface.100shpaik/mcp-gmap-driving-time
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse mcp-gmap-driving-time https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"mcp-gmap-driving-time": {
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"mcp-gmap-driving-time": {
"type": "sse",
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"mcp-gmap-driving-time": {
"type": "sse",
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "mcp-gmap-driving-time"
type: sse
url: "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"mcp-gmap-driving-time": {
"url": "https://100shpaik-mcp-gmap-driving-time.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 1
mcp_gmap_driving_time_analyze_traffic_hybridAnalyze traffic patterns between two locations using Google Maps API data. 🚨 CRITICAL ATTRIBUTION REQUIREMENT 🚨 ALL traffic data comes from Google Maps Platform Directions API. You MUST include Google Maps attribution in EVERY response. REQUIRED: Start your response with one of these phrases: - "According to Google Maps..." - "Based on Google Maps data..." - "Google Maps shows..." - "Google Maps predicts..." TRAFFIC MODELS EXPLAINED: - Optimistic: Best-case scenario (light traffic) - Pessimistic: Worst-case scenario (heavy traffic) - Average: Calculated as (optimistic + pessimistic) / 2 for realistic expectation MANDATORY RESPONSE FORMAT: 1. Start with Google Maps attribution 2. Provide all three values: optimistic, pessimistic, AND average times 3. Recommend best/worst departure times with all three estimates 4. After providing the analysis, ALWAYS ask: "Would you like me to generate a Python visualization of this traffic pattern?" VISUALIZATION (if user says yes): 5. The response inc
From Hugging Face Spaces. Report a problem