gbfs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gbfs_list_systemsA | Search the MobilityData systems.csv catalog of 1,000+ public bikeshare and micromobility systems worldwide by city name, country, operator, or system_id. |
| gbfs_get_systemA | Fetch system metadata, operator information, and resolved feed endpoints from gbfs.json for a given system_id or auto-discovery URL. |
| gbfs_get_stationsB | Fetch real-time station status (available bikes, e-bikes, and docks) for a bikeshare system. Optionally sort and filter by geographic proximity. |
| gbfs_get_free_bikesB | Fetch real-time dockless/free-floating bikes and scooters (free_bike_status.json) with battery levels and coordinates. |
| gbfs_get_alertsB | Fetch active system alerts, disruption notices, and weather closures from system_alerts.json. |
| gbfs_get_vehicle_typesB | Fetch vehicle fleet specifications (form factors, mechanical vs electric assist, maximum battery range) from vehicle_types.json. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct GBFS resource and action: system discovery, system metadata, stations, free bikes, alerts, and vehicle types. There is no meaningful overlap that would cause an agent to select the wrong tool.
All tools follow a consistent gbfs_<verb>_<noun> pattern, using list_ for catalog discovery and get_ for fetching specific data. The only minor irregularity is singular 'system' vs plural others, but it is intuitive as it returns a single system.
With 6 tools, the server is well-scoped for a GBFS domain, covering the most commonly needed data feeds without bloat. Each tool serves a distinct, high-value purpose.
Core GBFS feeds such as station status, free bikes, alerts, and vehicle types are covered, and system metadata provides feed endpoints for raw access. The absence of a dedicated station_information tool for static station names/coordinates is a minor gap that agents can work around by consulting feed endpoints.