Servidor MCP de roadflow

• Nome no registroio.roadflow/roadflowverificado no registro MCP

O nome no registro fica sob roadflow.io. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-26
• Ferramentas43
• O servidor se chamaroadflow
• Versão do servidor1.0.0
• Versão do protocolo2025-06-18

Em 2026-10-26 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 180 ms.

• As ferramentas fazem plan roadmap steps across parallel lanes and goals; share view-only roadmap links with stakeholders, mas não sync roadmap items from a Slack list.
• Verificado em 1 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 1 até agora
• O que um agente consegue fazer com ele2 de 3 casos de uso
• Respondeumedindo1 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta761 ms
• Espaço no contexto do agente≈ 4.533 tokensas definições de todas as ferramentas (43), que o agente carrega a cada turno
• Definições das ferramentasC · 73 de 100
• Resultados tipados0 de 43 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem tipo: em 8 de 43
• Parâmetros sem descrição: em 18 de 43
• Sem dizer se só lê ou se pode destruir: 43 de 43

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (30%), se faz o trabalho do produto (25%), definições (20%), contexto (10%) e uso (15%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• roadflow_new

  Create an ephemeral in-memory roadflow workspace (default). Optional seed JSON and/or markup. No cloud id until create_shared.

• roadflow_status

  Return mode, ids, URLs, and road/step counts for the current MCP session workspace.

• roadflow_get

  Return the current workspace as JSON and/or markup.

• roadflow_apply_json

  Replace workspace state with normalized JSON (serializeState shape). In shared edit mode, saves to the cloud automatically.

• roadflow_apply_markup

  Replace roads via friendly markup (same as the editor panel). Shared edit mode auto-saves.

• roadflow_open_shared

  Load a cloud map by edit or view id into this session. View links are read-only.

• roadflow_create_shared

  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_export_json

  Export the current workspace as JSON (serializeState).

• roadflow_export_markup

  Export the current workspace as friendly markup.

• roadflow_export_csv

  Export steps as CSV (road, goal, lane, step, notes, type, status, position, date).

• roadflow_list_versions

  List shared-map version checkpoints (newest first). Relative indexes: -1 = newest. Requires a shared edit workspace (not view-only).

• roadflow_get_version

  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.

• roadflow_discard

  Clear the in-memory workspace for this MCP session (does not delete cloud maps).

• artifacts_new

  Create an ephemeral in-memory Artifacts graph workspace. Optional seed JSON (serializeState shape: nodes + labels). No cloud id until artifacts_create_shared.

• artifacts_status

  Return mode, ids, /artifacts/?id= URLs, and node/label counts.

• artifacts_get

  Return the current Artifacts workspace as JSON.

• artifacts_apply_json

  Replace (or merge) the Artifacts graph with normalized JSON. Shared edit mode auto-saves to the cloud.

• artifacts_open_shared

  Load a cloud Artifacts graph by edit or view id. View links are read-only.

• artifacts_create_shared

  Persist the current Artifacts workspace to the cloud. Returns editUrl and viewUrl under /artifacts/.

• artifacts_export_json

  Export the current Artifacts workspace as JSON (serializeState).

• artifacts_list_versions

  List shared Artifacts version checkpoints (newest first). Requires a shared edit workspace.

• artifacts_get_version

  Load one shared Artifacts version by relative index (-1 newest). Optional load=true replaces the MCP workspace (does not save).

• artifacts_discard

  Clear the in-memory Artifacts workspace for this MCP session (does not delete cloud graphs or the Plans workspace).

• model_new

  Create a Model project in MySQL (parameter register). Allocates a view id (mv-…) when omitted and returns viewUrl. Optional seed: title, calendar, streams, axes, phases, parameterSets, chains, parameters, observations, edges. Does not…

• model_open

  Bind this MCP session to an existing Model project (edit or view id). View ids are read-only.

• model_status

  Counts, rev, and /model/?id= URLs for the bound project (or pass id).

• model_get

  Hydrate records from MySQL. include=summary (default counts), dictionaries, parameters, observations, edges, or all. Prefer model_upsert_observation to change one fact — do not treat this as a blob to rewrite.

• model_discard

  Unbind the Model project from this MCP session. Does not delete MySQL rows.

• model_patch_project

  Update title, calendar, viewId, streams, axes, phases, parameterSets, and/or chains. Send If-Match via rev. Replaces each provided dictionary in full.

• model_list_parameters

  List parameter catalog rows. Optional filters: streamId, role, layer, primaryOwner.

• model_get_parameter

  One catalog row plus its observations (facts).

• model_upsert_parameter

  Create or patch one parameter definition (not observations). Pass rev for If-Match on update.

• model_upsert_parameters

  Create or patch many catalog rows (cap 400). Same body shape as model_upsert_parameter. continueOnError returns per-row errors; otherwise one transaction.

• model_delete_parameter

  Delete a parameter and its observations (cascade).

• model_list_observations

  List facts. Filter by parameterId, setId, evidenceStatus. Sets are a column (Base/Downside/Upside), not an axis.

• model_upsert_observation

  Create or replace one fact (parameterId + scope + setId). Example: Base P2 facility MW. Do not write CALC-computed values; only IN facts or CALC overrides (valueOverride). Pass rev for If-Match.

• model_upsert_observations

  Create or replace many facts (cap 400). Same body shape as model_upsert_observation. Rejects CALC outputs unless valueOverride. continueOnError returns per-row errors; otherwise one transaction.

• model_delete_observation

  Delete one fact by parameterId + scope/scopeKey + setId.

• model_list_edges

  Manual lineage edges only (SOURCE/FLOW/INTERFACE). FORMULA edges are derived from formulas on load — not stored.

• model_upsert_edge

  Create or patch a manual SOURCE, FLOW, or INTERFACE edge. FORMULA is rejected.

• model_delete_edge

  Delete a manual edge by edgeId.

• model_evaluate

  Read-only computeModel. Does not write MySQL. View ids allowed. Default period is calendar start (not today). periodId and range* are mutually exclusive. Cell cap 2000.

• model_list_dictionaries

  Streams, axes (members), phases, parameter sets, chains, and calendar. Period members may be derived from calendar.