LoomCycle MCP Server Tool icon

LoomCycle MCP Server Tool

Registers an MCP server in the loomcycle substrate (idempotent), then exposes a tool that delegates to a loomcycle agent using that MCP server

LoomCycle MCP Server Tool

AI-generated

Summary

Registers the configured HTTP or Streamable HTTP MCP server with loomcycle if it is not already registered, then exposes an AI tool that sends the caller’s prompt to the selected loomcycle agent. The agent receives access to tools matching mcp__<MCP Server Name>__*, and the tool returns the agent’s final text.

Inputs

  • Tool Name (required) — Name shown to the parent AI Agent for this tool; defaults to loomcycle_mcp.
  • Tool Description — Description the parent AI Agent uses when deciding whether to call the tool.
  • MCP Server Name (required) — Unique loomcycle registration name used to construct the agent’s allowed tool pattern. A name already registered in static YAML cannot be dynamically registered.
  • Transport (required) — Choose HTTP or Streamable HTTP; defaults to Streamable HTTP. Stdio servers must be declared in loomcycle.yaml.
  • URL (required) — MCP server endpoint URL. The hostname must be permitted by loomcycle’s HTTP host allowlist.
  • Headers — Optional headers attached to MCP calls. Header values support loomcycle environment-variable and per-run substitutions; the node logs any referenced LOOMCYCLE_* variables for configuration on loomcycle.
  • Loomcycle Agent (required) — Agent to spawn when the parent AI Agent invokes the tool.
  • Cleanup On Workflow End — When enabled, attempts to retire the MCP registration when the workflow execution ends. Defaults to false, so the registration persists.
  • prompt (required) — Text task sent to the loomcycle agent when the AI tool is called.

Output shape

An AI tool whose invocation returns the loomcycle agent’s final text. In regular node execution, returns one item per input item, each containing the result as json.result; errors are returned in an json.error field.

The node uses the required loomCycleApi credential. It looks up the MCP registration and creates it only if not found; an existing registration is not updated from the node’s URL, transport, or headers. The prompt is sent as untrusted text. Agent run errors are surfaced as tool errors (or as an error field in regular execution), with bearer-like fragments redacted.

Examples

Example 1: Register an HTTP MCP server and expose its tools to a loomcycle agent

Set the server name, HTTP transport, endpoint URL, optional headers, and loomcycle agent. Connect this node’s AI Tool output to a parent AI Agent; the parent can then call the named tool with a prompt, and the selected agent runs with access to mcp__<server-name>__* tools.

Example 2: Keep a shared MCP registration across workflows

Leave Cleanup On Workflow End disabled (the default) so the registration persists after execution and can be reused.

Links

Discussion