Developer Tools
orchestratemcp.dev
Manages AI workflow graph components and provides technology stack recommendations.
ENDPOINT 1
https://mcp.orchestratemcp.dev/mcp
Known tools 18
list_graph_componentsLists published workflow graph components.
get_graph_componentReturns full details for a single workflow graph component by id.
list_graph_edgesLists workflow graph edges (relations between components).
get_graph_edgeReturns full details for a single workflow graph edge by id.
get_stack_recommendationReturns the recommended technology stack for an AI workflow, with opinionated defaults and when-to-upgrade guidance.
list_known_routesLists all known golden-path workflow routes in the registry.
get_routeReturns full details for a single golden-path workflow route by id.
compose_workflow_routeProposes 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_playbookReturns a golden-path playbook from the workflow graph registry by id or workflow type.
get_relevant_docsReturns 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_architectureThe main user-facing architecture recommendation tool.
review_workflow_designDeterministic safety checker for AI workflow designs.
plan_workflowOne-call workflow planner.
record_session_feedbackThe 'ship' step after plan_workflow: capture an evaluation of a COMPLETED workflow setup.
explain_componentReturns 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_candidateDeterministic, read-only gate for the playbook factory.
export_build_briefTakes 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_checkReturns the server name, version, a summary of loaded registry entities (components, edges, stacks, routes, playbooks), and a build fingerprint.