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.

Inferred read-only

get_graph_component

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

Inferred read-only

list_graph_edges

Lists workflow graph edges (relations between components).

Inferred read-only

get_graph_edge

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

Inferred read-only

get_stack_recommendation

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

Inferred read-only

list_known_routes

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

Inferred read-only

get_route

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

Inferred read-only

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.

Inferred read-only

get_playbook

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

Inferred read-only

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.

Inferred read-only

recommend_architecture

The main user-facing architecture recommendation tool.

Inferred read-only

review_workflow_design

Deterministic safety checker for AI workflow designs.

Inferred read-only

plan_workflow

One-call workflow planner.

Inferred read-only

record_session_feedback

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

Inferred read-only

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.

Inferred read-only

validate_playbook_candidate

Deterministic, read-only gate for the playbook factory.

Inferred read-only

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.

Inferred read-only

health_check

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.orchestratemcp-dev]
url = "https://mcp.orchestratemcp.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "orchestratemcp-dev": {
      "type": "http",
      "url": "https://mcp.orchestratemcp.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: orchestratemcp-dev
Remote MCP URL: https://mcp.orchestratemcp.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "orchestratemcp-dev": {
      "url": "https://mcp.orchestratemcp.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "orchestratemcp-dev": {
      "type": "http",
      "url": "https://mcp.orchestratemcp.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "orchestratemcp-dev",
  "transport": "streamable-http",
  "url": "https://mcp.orchestratemcp.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for orchestratemcp.dev was fetched 2026-09-06T09:14:37.333Z.

Trust status Neutral

orchestratemcp.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.