MCP tool

    exo_get_node_types

    The step types a flow can use, with their settings, outputs and plan.

    For tools and AI agents: this page as Markdown · the public OpenAPI file

    Description

    Without nodeType, it lists every step type. Each entry has its label, description, category, the settings it reads (configKeys), the fields it outputs for {{nodeId.field}} references (outputFields), the plan that includes it (requiredPlan) and whether your workspace's plan includes it (includedInPlan).

    Permission

    Needs an API key or OAuth connection with the build permission.

    Input

    NameTypeRequiredDescription
    nodeTypestringNoReturn detail for this single node type.

    Returns

    A list returns count, nodeTypes and planTier (your workspace's plan). One step type returns its entry and a note.

    Plan check

    Each step type belongs to a plan. A create or update that adds a step your workspace's plan does not include is refused before anything is saved, with code: "PLAN_REQUIRED", the plan it needs (requiredPlan), the steps involved (steps) and the message in English, Arabic and Chinese (messages). exo_get_node_types marks which steps your plan includes, and exo_validate_flow reports them as warnings.

    {
      "saved": false,
      "code": "PLAN_REQUIRED",
      "upgradeRequired": true,
      "currentPlan": "starter",
      "requiredPlan": "pro",
      "steps": [
        {
          "nodeId": "sftp_1",
          "type": "sftp",
          "label": "SFTP / FTP Files",
          "family": "advanced_integrations",
          "requiredPlan": "pro"
        }
      ],
      "messages": {
        "en": "Your Starter plan doesn't include these steps: SFTP / FTP Files. They are part of the Professional plan. Nothing was created. Upgrade to Professional, or use steps your plan includes.",
        "ar": "…",
        "zh": "…"
      }
    }

    Errors

    Returned as a normal result with isError: true:

    • Unknown node type "<nodeType>".

    Returned as a JSON-RPC error:

    CodeHTTPMessage
    -32001403API key lacks the 'build' permission required for flow authoring tools

    Messages are shown exactly as the server sends them, in English. A value in angle brackets is filled in at run time.

    Examples

    Example call

    {
      "jsonrpc": "2.0",
      "id": 1,
      "method": "tools/call",
      "params": {
        "name": "exo_get_node_types",
        "arguments": {
          "nodeType": "http_request"
        }
      }
    }

    Example result

    {
      "jsonrpc": "2.0",
      "id": 1,
      "result": {
        "content": [
          {
            "type": "text",
            "text": "Node type \"http_request\".\n{ ... }"
          }
        ],
        "structuredContent": {
          "type": "http_request",
          "label": "HTTP Request",
          "description": "Make a basic HTTP request",
          "category": "action",
          "requiredPlan": "starter",
          "includedInPlan": true,
          "configKeys": [
            "..."
          ],
          "outputFields": [
            "..."
          ],
          "note": "..."
        },
        "isError": false
      }
    }

    Example values. In content, the text after the summary line is the same data as structuredContent.