mcp server
roadflow
Create and edit roadmaps with JSON or markup; share edit and view links from AI agents.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-08-03.
What this server can do
13 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
roadflow_apply_json(json, merge)- Replace workspace state with normalized JSON (serializeState shape). In shared edit mode, saves to the cloud automatically.
roadflow_apply_markup(markup)- Replace roads via friendly markup (same as the editor panel). Shared edit mode auto-saves. Required: markup.
roadflow_create_shared(editId, viewId)- Persist the current workspace to the cloud (permanent share). Returns editUrl (play/edit/share further) and viewUrl (visual canvas, read-only). Prefer viewUrl when the user only needs to see the map.
roadflow_discard- Clear the in-memory workspace for this MCP session (does not delete cloud maps).
roadflow_export_csv- Export steps as CSV (road, goal, lane, step, notes, type, status, position, date).
roadflow_export_json- Export the current workspace as JSON (serializeState).
roadflow_export_markup- Export the current workspace as friendly markup.
roadflow_get(format)- Return the current workspace as JSON and/or markup.
roadflow_get_version(rel, load)- Load one shared-map version by relative index (e.g. -1 newest, -2 previous). Returns JSON state. Does not change the live map or workspace unless load=true. Required: rel.
roadflow_list_versions- List shared-map version checkpoints (newest first). Relative indexes: -1 = newest. Requires a shared edit workspace (not view-only).
roadflow_new(json, markup)- Create an ephemeral in-memory roadflow workspace (default). Optional seed JSON and/or markup. No cloud id until create_shared.
roadflow_open_shared(id)- Load a cloud map by edit or view id into this session. View links are read-only. Required: id.
roadflow_status- Return mode, ids, URLs, and road/step counts for the current MCP session workspace.
Last successful function declaration observed on . Source: https://roadflow.io/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://roadflow.io/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-03 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-03 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 13 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | roadflow.io | |
| mcp endpoint status | ok | The server listed 13 functions when asked. | as of probe | roadflow.io |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json