ROOTE — Real-Time Mobility Data MCP

Real-time mobility data MCP for AI agents: geocoding, shared bikes & scooters, public transport, parking, EV charging and urban services.

View on roote.aiTry this MCPSponsored

Documentation

REAL-TIME URBAN CONTEXT

A mobility data MCP server built for location-aware AI.

ROOTE connects MCP-compatible assistants and agentic applications to normalized urban data. One remote Streamable HTTP connection provides geocoding, nearby shared mobility, public transport stops and essential city services.

Freshness and availability remain explicit in every response. Live or near-real-time information is returned when supported by the underlying source, while provenance, partial coverage and source failures stay visible to the agent.

Real-time mobility data

Shared bicycles, scooters, mopeds, cars, stations and available vehicles.

Public transport data

Nearby bus, tram, metro, regional rail, train, ferry and shuttle stops.

Urban services data

Parking, EV charging, toilets, AEDs, Wi-Fi, fountains and lockers.

REAL QUESTIONS. STRUCTURED ANSWERS.

Your AI can understand what’s around.

ROOTE handles the connection between the assistant and the underlying urban data.

“Find bikes near Gare Saint-Jean.”

“What tram stops are close to this address?”

“Find parking and EV charging nearby.”

“What mobility, transit and services are available around République?”

THE TOOLKIT

Seven tools. One urban layer.

GLOBAL

nearby

Search mobility, transit and urban services around a location through one request.

Mobility · Transit · Services

PLACES

geocode

Turn an address into geographic coordinates.

PLACES

place_search

Find cities, stations, airports and points of interest.

PLACES

reverse_geocode

Identify the place corresponding to geographic coordinates.

NEARBY

mobility_nearby

Discover shared bikes, scooters, mopeds, cars, stations and available vehicles.

NEARBY

transit_nearby

Find nearby bus, tram, metro, rail, ferry and other public transport stops.

NEARBY

services_nearby

Find toilets, AEDs, EV chargers, parking, Wi-Fi, drinking fountains and lockers.

BUILT FOR AI AGENTS

From intent to urban context.

ROOTE turns fragmented urban data into tools an assistant can call directly.

  1. 01 User request
  2. 02 AI assistant
  3. 03 ROOTE MCP
  4. 04 ROOTE API
  5. 05 Urban sources

No need to integrate dozens of mobility APIs or normalize individual data providers yourself.

USE CASES

One interface. Multiple possibilities.

01

Travel assistants

Understand mobility, transport and services around hotels, stations, airports and destinations.

02

Mobility assistants

Discover shared vehicles, stations and nearby public transport.

03

Local AI

Give assistants awareness of nearby urban infrastructure and services.

04

Agentic applications

Let AI agents search, combine and reason over geographic and urban context.

CONNECT ROOTE MCP

One prompt.Any compatible AI.

Paste this prompt into any AI assistant or client that supports remote MCP servers. Anonymous Free access works without an account or API key.

  1. 1 Copy the setup prompt No account or credential is required for anonymous Free access.
  2. 2 Paste it into your AI client Your client will configure the Streamable HTTP endpoint and discover the tools.
  3. 3 Verify and start exploring Your client will initialize ROOTE, list all seven tools and perform a real anonymous test. Get an API key (optional)

UNIVERSAL SETUP PROMPTMCP · STREAMABLE HTTP

Configure persistent access to ROOTE MCP in this client.

Configuration:

- Server name: roote
- URL: https://mcp.roote.ai/mcp
- Transport: Streamable HTTP
- Authentication: optional Bearer token

Connect anonymously by default. Do not ask me for an API
key unless I explicitly request authenticated project access.

If I choose authenticated access, follow these security requirements:

- First identify the secure credential mechanisms supported
  by this client and operating system.
- Ask for my API key only once through a native masked secret
  field or the client's secure credential flow.
- Never display it in the conversation, logs, URL,
  terminal, generated code or plain-text configuration.
- Store it persistently using the safest native mechanism
  available, such as the client's credential vault, the
  operating system keychain or an approved secret manager.
- Configure the client to retrieve the credential securely
  and produce the Authorization header automatically.
- Never store a static credential in plain-text HTTP headers,
  source code, shell profiles or global environment settings.
- Do not require me to re-enter or manually export the key
  for each session.
- If this client cannot store credentials securely, explain
  the limitation and ask before using a supported alternative.
- If a roote configuration already exists, update it
  without creating a duplicate.

After configuration:

1. Read the non-sensitive configuration back and confirm
   that the key does not appear in plain text.
2. If a credential was configured, verify its retrieval without
   displaying or logging the sensitive value.
3. Run MCP initialize for real without authentication.
4. Run tools/list for real.
5. Confirm the exact presence of these seven tools:
   - geocode
   - place_search
   - reverse_geocode
   - nearby
   - mobility_nearby
   - transit_nearby
   - services_nearby
6. Perform an anonymous ROOTE test call. If I explicitly chose
   authenticated access, use the stored credential instead.
7. If the client must restart or reconnect to load the tools,
   say so clearly and only once.

Important:

- When I later ask you to use ROOTE, use ROOTE exclusively.
- Never silently replace ROOTE with web search or another API.
- If ROOTE fails, report the error instead of switching sources.
- If I configured a key, do not ask for it again on
  subsequent requests.

BUILT FOR AI AGENTS

Start free.Scale when you’re ready.

Use the same seven ROOTE tools at every stage. Begin anonymously, then add an API key when your agent needs authenticated project access.

FREE Anonymous

Explore without friction.

Connect an MCP-compatible agent and start discovering urban context immediately.

  • No account required
  • No API key required
  • All seven MCP tools
  • Free limits managed by ROOTE API Start for free

DEVELOPER API key

Build beyond the prototype.

Attach a ROOTE API token when you need authenticated access tied to your project.

  • Secure Bearer authentication
  • Project-level access and usage
  • API-managed credits and limits
  • The same stable MCP interface Get your API key

CURRENT SCOPE

What is around this place?

ROOTE MCP currently focuses on place resolution and nearby discovery across mobility, transit and services. Coverage, availability and freshness depend on the sources available in each location.

Not currently exposed through MCP

  • Real-time departures
  • A → B journey planning
  • Service disruptions
  • Vehicle booking or unlocking
  • Direct control of the ROOTE map

FREQUENTLY ASKED QUESTIONS

Real-time mobility data MCP, explained.

What is a real-time mobility data MCP server?

A real-time mobility data MCP server exposes mobility and urban data as standardized tools that an AI agent can discover and call. ROOTE provides geocoding, shared mobility, nearby transit and urban services through the Model Context Protocol.

Does ROOTE MCP provide real-time data?

ROOTE returns live or near-real-time availability when the underlying provider supports it. Responses preserve timestamps, freshness, provenance, warnings and partial coverage so an AI agent can distinguish current, stale, incomplete and unavailable data.

Which mobility and transport modes are supported?

Mobility modes include bicycles, stations, scooters, mopeds, cars and taxis. Transit modes include bus, tram, metro, cable car, regional rail, train, ferry and shuttle. Actual coverage depends on the data sources available at the requested location.

How does an AI assistant connect to ROOTE MCP?

Use the remote endpoint https://mcp.roote.ai/mcp with Streamable HTTP. Initialize, tool discovery and Free tool calls work anonymously. A ROOTE API Bearer token scoped to data:read is optional for authenticated project access.

What can an AI agent find with ROOTE?

An agent can resolve addresses and places, discover nearby shared vehicles and stations, find public transport stops, and search for parking, EV chargers, toilets, AEDs, Wi-Fi, drinking fountains and lockers.

START BUILDING

Connect your AI to the city.

STREAMABLE HTTP https://mcp.roote.ai/mcp