MCP Server

Uncontrolled node

Overview

The MCP Server node creates a Model Context Protocol (MCP) server configuration that defines available tools, server metadata, and capabilities. This configuration object is used by other MCP nodes in your workflow to expose tools to AI models and MCP clients. The node outputs a structured configuration containing the server name, version, and tool definitions with their input schemas.

Inputs

Input	Type	Description	Default
Server Name	Text	The name identifier for the MCP server.	Intellectible MCP Server
Server Version	Text	The version string for the MCP server (semantic versioning recommended).	1.0.0
Tools	Data	An array of tool definition objects. Each tool should include name, title, description, and inputSchema (JSON Schema format).	-

Outputs

Output	Type	Description
Output	Data	A configuration object containing serverName, serverVersion, and tools array. This object is consumed by MCP client nodes and server event handlers.

Runtime Behavior

As an uncontrolled node, the MCP Server node executes immediately when the workflow initializes, constructing the server configuration object from the provided inputs. The node validates that serverName and serverVersion default to sensible values if not provided, and packages the tools array into a structured configuration. This configuration is then available immediately to downstream nodes without waiting for an event trigger.

The output configuration is typically consumed by:

• MCP Server Start nodes to initialize the server
• MCP Server Tool Call Event nodes to handle incoming tool execution requests
• Set MCP Output nodes to return tool execution results

Example Usage

Configure the MCP Server node with your tool definitions, then connect the output to an MCP Server Start event node to begin accepting connections:

// Example Tools Input
[
  {
    "name": "search_database",
    "title": "Search Database",
    "description": "Query the project database for records",
    "inputSchema": {
      "type": "object",
      "properties": {
        "query": {"type": "string"},
        "limit": {"type": "number"}
      },
      "required": ["query"]
    }
  }
]

Connect the Output to downstream MCP event nodes (MCPServerStart, MCPServerToolCallEvent) to handle server lifecycle and tool execution. Use the Set MCP Output node to return results from tool calls back to the client.