Ryde MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RYDE_TOKEN | No | Overrides the saved token. | |
| RYDE_CONFIG | No | Path to the Ryde config file. Default: ~/.config/ryde-cli/config.json. MCP authentication fails if login and the server use different RYDE_CONFIG paths. | |
| RYDE_BASE_URL | No | Overrides the saved/default API URL. | |
| RYDE_LATITUDE | No | Login latitude. Defaults to 0; used only for login. | |
| RYDE_DEVICE_ID | No | Device ID. Generated if absent. | |
| RYDE_LONGITUDE | No | Login longitude. Defaults to 0; used only for login. | |
| RYDE_PHONE_INFO | No | Android phone string. | |
| RYDE_MOBILE_TYPE | No | Android descriptor. Overrides the saved/default descriptor. | |
| RYDE_COUNTRY_CODE | No | Country code. Default: +47. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| account_profileA | Return the signed-in owner's profile/account record. Read-only. |
| current_rideA | Return current ride status only; this never starts, ends, or alters a ride. |
| list_ridesA | List completed rides. Dates are inclusive YYYY-MM-DD; omit for all available history. |
| ride_detailA | Fetch detail for one completed ride ID. Read-only. |
| ride_orderB | Fetch linked order/charge detail for a completed ride. Read-only. |
| ride_routeC | Fetch stored route GPS only after explicit sensitive-location acknowledgement. |
| pass_catalogueB | Return current RidePass products, prices, allowances and validity for a city. |
| owned_passesA | Return active/current passes owned by the signed-in account. |
| recharge_historyB | Return pass/recharge purchase history. all_pages may make multiple read-only requests. |
| recharge_detailB | Return one recharge/pass receipt by its recharge ID. Read-only. |
| vipps_payment_historyC | Return read-only Vipps payment-order history for the signed-in account. |
| account_month_amountC | Return account amount data for YYYY-MM. Read-only. |
| recharge_monthC | Return recharge data for YYYY-MM. Read-only. |
| city_fee_ruleC | Return fee/fare rules for a city. Read-only. |
| ride_summaryC | Compute local ride totals, distance, duration, discounts, monthly trend and averages. |
| recommend_ridepassC | Compare current city RidePasses against observed rides with stated conservative assumptions. |
| prepare_statsA | Start a resumable background export; poll stats_job_status with the returned job_id. Route GPS requires explicit consent. |
| stats_job_statusA | Poll a background stats job. completed results contain counts and, for open_stats, a local dashboard URL. |
| open_statsA | Start a background fetch-and-open job; poll stats_job_status for its URL. refresh=false opens cached data immediately. Browser opens on the MCP host only. |
| close_statsA | Stop a local dashboard using its exact returned URL; never sends account credentials. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| account_summary_resource | JSON ride summary for all available history of the configured account. |
TDQS
Scored across 20 tools
Most tools have clearly distinct resource+action targets (list_rides vs ride_detail vs ride_order vs ride_route). The main overlap is among aggregate/period tools: ride_summary, account_month_amount, and recharge_month all return computed monetary/statistical data and could be confused, as could recharge_history vs recharge_month. Descriptions mitigate this reasonably well.
All names use snake_case, which is consistent, but the convention mixes verb-first (list_rides, prepare_stats, recommend_ridepass, open_stats) with noun-phrase forms (account_profile, current_ride, ride_summary, pass_catalogue). Readable, but no single predictable pattern.
20 tools is at the high end but justified by the breadth of the domain (account, rides, routes, passes, recharges, payments, stats jobs, city rules). Slightly heavy, with a small cluster of stats-job tools, but each earns its place.
Broad read coverage: list/detail/summary across rides, recharges, passes, payments, account, plus analytics and city rules. The surface is essentially read-only, so action operations (booking a ride, buying a pass, topping up) are absent, but this appears to be an intentional analytics/read scope.