← Registry

Developer Tools

orchestratemcp.dev

Manages AI workflow graph components and provides technology stack recommendations.

1 endpoint18 known toolsFirst detected July 10, 2026Last detected July 10, 2026

ENDPOINT 1

https://mcp.orchestratemcp.dev/mcp

No auth detected

Known tools 18

list_graph_components

Lists published workflow graph components.

get_graph_component

Returns full details for a single workflow graph component by id.

list_graph_edges

Lists workflow graph edges (relations between components).

get_graph_edge

Returns full details for a single workflow graph edge by id.

get_stack_recommendation

Returns the recommended technology stack for an AI workflow, with opinionated defaults and when-to-upgrade guidance.

list_known_routes

Lists all known golden-path workflow routes in the registry.

get_route

Returns full details for a single golden-path workflow route by id.

compose_workflow_route

Proposes a candidate AI workflow route by matching your goal to graph components, adding required dependencies and safety gates, ordering steps, and scoring the result.

get_playbook

Returns a golden-path playbook from the workflow graph registry by id or workflow type.

get_relevant_docs

Returns documentation and source references relevant to a playbook, route, set of components, or framework/topic from the workflow graph registry and the internal docs-index.

recommend_architecture

The main user-facing architecture recommendation tool.

review_workflow_design

Deterministic safety checker for AI workflow designs.

plan_workflow

One-call workflow planner.

record_session_feedback

The 'ship' step after plan_workflow: capture an evaluation of a COMPLETED workflow setup.

explain_component

Returns a plain-language, operator-friendly explanation of a single workflow component — what it does, what it needs, what it produces, which other steps it connects to, and what can go wrong.

validate_playbook_candidate

Deterministic, read-only gate for the playbook factory.

export_build_brief

Takes a plan_workflow result and emits a provenance-tagged Build Brief — a self-contained handoff document (§0 Constraints → §9 Observability wiring) ready to paste into an IDE agent prompt, a Linear issue, or an Obsidian note.

health_check

Returns the server name, version, a summary of loaded registry entities (components, edges, stacks, routes, playbooks), and a build fingerprint.