CityBikes MCP for AI. Get live global bike availability data instantly.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
CityBikes provides instant access to real-time bike-sharing data from over 400 global cities. Use this MCP to list entire network topologies and fetch live counts for bikes and empty docks at specific stations worldwide.
What your AI can do
Get network
Retrieves comprehensive details and metadata for one specific bike-sharing network.
List networks
Returns a list of all supported bike-sharing networks, helping you find the IDs needed for deeper queries.
List every supported bike-sharing network worldwide, providing names and unique identifiers for each system.
Fetch live data for a specific network to get the exact count of bikes and empty docking spots at all stations.
Retrieve precise geographic coordinates and names for bike-sharing stations in any supported city.
Ask an AI about this
Waiting for input…
CityBikes (Bike Sharing) with 2 Tools
These tools let you list all available bike networks and retrieve deep, specific data about any single network's infrastructure.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using CityBikes (Bike Sharing) on VinkiusGet Network
Retrieves comprehensive details and metadata for one specific bike-sharing network.
List Networks
Returns a list of all supported bike-sharing networks, helping you find the IDs...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with CityBikes (Bike Sharing), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by CityBikes. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 2 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Finding bike availability used to mean hopping between apps.
Today, checking local commute options means downloading a dozen separate apps. You open Google Maps, then switch to the transit app, then search for local bike-share providers—all with different interfaces and login requirements. You end up wasting ten minutes just figuring out which service exists in your target neighborhood.
With this MCP, you simply ask your agent about bike availability across a region. It handles the messy work of querying dozens of global systems, giving you a clean status report showing available bikes and docks without any manual app switching or headache.
Using `get_network` gives you deep infrastructure details.
Without this tool, if you knew the name of a bike-sharing system, getting its precise coordinates and full station list required multiple API calls just to build a map. You were limited to general area data, not specific points of interest.
Now, calling `get_network` provides all that infrastructure data in one go. You get detailed metadata—the exact latitude and longitude for every hub—which is the critical layer developers need.
What your AI can actually do with this
Need to plan a commute or just figure out how to get around a new city? This connector gives your AI client the real-time status of bike-sharing systems across hundreds of global networks. You don't have to download ten different city apps; you just ask your agent, and it pulls the live data.
It tells you exactly which networks are running in an area and how many bikes or docks are available at any given station right now. Whether you’re writing a travel guide or building a local transit dashboard, this MCP makes sure you have precise micrmobility numbers when you need them.
You can find the CityBikes integration within the Vinkius catalog alongside other global tools to build out your agent's capabilities.
019eb8ad-2fd8-7261-b777-7e71b19cdb5b Here's how it actually works
The bottom line is that your AI client handles the connection and data formatting; you just ask for what you need.
Subscribe to this MCP on Vinkius.
Start querying your agent with a request (e.g., 'List all networks in Italy').
Your agent uses the tool definitions to pull the live data, giving you immediate status reports.
Who is this actually for?
This MCP helps travel planners, urban developers, and logistics teams. If your job involves knowing how people get around in a foreign city or tracking micro-mobility trends, this is the tool for you.
Needs to quickly verify bike availability in different cities before writing an itinerary, ensuring their recommendations are current.
Gathers real-time historical and live urban mobility data for research into city planning or commuter trends.
Integrates live, accurate transport status feeds into custom dashboards or travel recommendation applications.
What Changes When You Connect
Stop guessing if a city has bike sharing. Use list_networks to see every supported system in one query, eliminating the need for manual searches or multiple apps.
Instead of visiting station by station, you can ask your agent for real-time status on an entire network, knowing exactly how many bikes and docks are available right now.
The ability to access metadata means you get precise coordinates for every station. This is critical if you're building a map-based travel tool.
You don't have to write complex API calls yourself. Your agent handles the data retrieval, letting you focus only on the answer: 'How many bikes are here?'
This MCP supports global coverage. Whether your project is in Europe or Asia, it draws from hundreds of different local bike-sharing systems.
It saves time by grouping related actions. You can first run list_networks to find an ID, and then pass that ID to get the specific details you need.
See it in action
Planning a multi-city trip
A travel planner needs to know if bike sharing is viable in five different European cities. They run list_networks via their agent, which provides the IDs and confirms coverage for all five locations instantly.
Building a logistics dashboard
An ops engineer must monitor fleet distribution across several urban zones. They use this MCP to check real-time availability, getting counts of bikes and empty docks at multiple stations in one query.
Researching micro-mobility trends
A data analyst is studying the growth rate of bike sharing. They systematically use list_networks to pull IDs for dozens of global systems, gathering a massive dataset for visualization projects.
Debugging travel tools
A developer needs to ensure their custom app can handle network changes. They run get_network on known high-traffic areas like Manhattan to validate the current station structure and coordinates.
The honest tradeoffs
Assuming one call is enough
Trying to get real-time availability data for a network without first knowing its unique ID, leading to an API error or incomplete results.
First, run list_networks to find the specific network ID. Then, use that ID with get_network to pull detailed status information accurately.
Writing hardcoded city names
Manually entering station coordinates for every single location you want to check into your query, which is slow and prone to human error.
Use list_networks to discover all viable network IDs in a region. Then use the system's functionality to pull data across multiple discovered networks.
When It Fits, When It Doesn't
Use this MCP if your core need is real-time, geo-located information about bike and dock availability from public sharing systems. This tool excels at giving you network topology (via list_networks) and specific status reports (via get_network). Don't use it if you only need general city maps or historical usage patterns—you might need a different type of geospatial data service instead. If your goal is to predict demand, this MCP gives the 'current state'; it doesn't provide predictive modeling.
Questions you might have
How does list_networks work with multiple cities? +
The list_networks tool finds all supported networks globally. You can then filter this list by location or ID to narrow down exactly what you need, saving time.
Do I need an API key for get_network? +
No complex keys are required for public access. Once connected through your agent on Vinkius, querying specific networks is straightforward.
Can list_networks tell me if a network exists in my city? +
Yes, running list_networks pulls the global inventory. If it shows an ID or name related to your location, you know the network is supported and available for querying.
Is get_network better than list_networks for checking status? +
No. Use list_networks first to find all potential services in an area; then, use get_network on the specific ID you want detailed real-time counts from.
What kind of specific data fields does get_network provide for a bike-sharing system? +
It provides detailed metadata, including location coordinates, unique IDs, and operational status. You can use this information to map out the entire infrastructure or verify if a network is still active.
What happens if I run list_networks but don't know which country to look in? +
The system will return all supported networks globally. This lets you discover potential bike-sharing systems across dozens of cities without needing to know the exact location beforehand.
If I use get_network and it returns an error, what should I check first? +
First, verify the network ID or name for typos. If the input is correct but fails, try running list_networks to confirm the system's current supported IDs.
Do I need to write code in my AI client to use get_network? +
No, you don't write code. You simply ask your AI agent to execute the function, and it handles all the underlying API calls for you automatically.
How can I find the specific ID for a bike network in my city? +
Use the list_networks tool. You can ask the agent to filter the results by city or country name to find the correct id (e.g., 'velib' for Paris or 'citibike-nyc' for New York).
Does the server show the exact number of available bikes at a station? +
Yes! By using the get_network tool with a specific network_id, the agent retrieves real-time station data, including the count of free bikes and empty docks.
Is the data updated in real-time? +
The data is fetched directly from the CityBikes API, which aggregates live feeds from various operators. The refresh rate depends on the individual bike-sharing provider's own API updates.
We've already built the connector for CityBikes. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 2 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.