An MCP server is a program that makes tools and information accessible to an artificial intelligence application compatible with the Model Context Protocol. An assistant can thus search for an address, query mobility data, or read an external resource during a conversation.
For ROOTE, the benefit is concrete: to answer "Where can I find a bike near this address?" based on a geographic search and the returned information, rather than relying solely on the model's memory.
Assistant, client and server: who does what?
| Element | Role | Mobility example |
|---|---|---|
| Host application | Manages the conversation and connections | The application where you ask your question |
| MCP client | Communicates with a server according to the protocol | Discovers ROOTE tools and transmits their arguments |
| MCP server | Exposes tools and returns their results | ROOTE searches for places or services |
| AI model | Interprets the request and formulates the response | Explains the results and their limits |
The server does not replace the model. It provides access to a defined operation, with structured inputs and output. The host application decides how to use these capabilities and may ask the user for validation.
Official architecture of the Model Context Protocol
MCP tools make a request executable
A tool has a name, a description, and an argument schema. The assistant must respect this schema: a proximity search needs valid coordinates and filters, not arbitrary text sent to any tool.
The protocol also distinguishes resources, which provide context, and prompts, which offer interaction templates. Each server publishes the capabilities it actually supports; the presence of MCP does not mean all are available.
Example: finding a bike near an address
The process starts with resolving the address. If multiple cities or places match, the assistant asks for clarification. It then uses the chosen coordinates to search for bike stations or vehicles and summarizes useful results.
A station located 250 meters away may be presented as geographically close. This distance does not automatically imply a walking time. Likewise, the number of observed bikes does not reserve a vehicle for the user.
What ROOTE MCP offers
The MCP ROOTE server exposes the tools geocode, place_search, reverse_geocode, nearby, mobility_nearby, transit_nearby, transit_disruptions, and services_nearby. They cover geographic searches, shared mobility, transport locations, disruptions, and some urban services. The server's tools/list is the reference for the available capabilities.
Journey and Departures are not part of this MCP V1. Finding a stop alone does not allow announcing the next bus. Another documented capability is required to obtain departures.
Official inventory of ROOTE MCP tools
What MCP does not guarantee
The protocol does not guarantee complete global coverage, always fresh data, nor an exact assistant response. These properties depend on sources, each tool’s contract, and how the application uses the results.
Names, descriptions, and links coming from a provider remain external data. They must not become instructions for the assistant. It keeps warnings, attributions, and unknown values instead of transforming them into certainties.
Choosing the right suite for your project
Connecting an assistant to the ROOTE MCP
Comparing API and MCP for mobility integration
Building a reliable mobility assistant
Coming soon: next departures and route calculation
ROOTE plans to extend its MCP to include upcoming departures and route calculation. These features are forthcoming and are not yet part of the tools currently exposed by the MCP server. When they become available, check the tools announced by the server, their arguments, and the information actually returned before announcing a passage or journey.
Frequently asked questions
Is MCP an artificial intelligence model?
No. It is a protocol allowing an AI application to communicate with servers that expose tools or context.
Does an MCP server replace an API?
It can use an API to perform its operations. API and MCP can thus be two complementary interfaces of the same service.
Does the ROOTE MCP server allow bike reservations?
The Data MCP ROOTE tools are read-only. A returned availability is not a reservation.