LoomCycle MCP ServerInstall

Summary

Manages dynamic MCP server registrations on a LoomCycle deployment via its MCPServerDef substrate tool. Supports create, fork, get, list, promote, retire, rediscover and verify; the listed properties are filtered by operation.

Inputs

• name (required) — For create: free-text registration name, referenced by agents as mcp__<name>__<tool> in allowed_tools. For get/list/retire/rediscover/verify: a dropdown of MCP servers (yaml + registry), or an expression.
• transport (required) — Create only. streamable-http (default, recommended) or http. Stdio is not supported; register stdio MCPs in loomcycle.yaml.
• url (required) — Create only. MCP endpoint URL. Its host must be in loomcycle's HTTP host allowlist, or the private host allowlist for loopback/RFC1918 hosts. Checked at registration.
• headers — Create only. Name/value HTTP headers sent on every MCP call. Values support ${LOOMCYCLE_*} env substitution, expanded at registration, and ${run.*} per-run placeholders. The env vars must already exist on the deployment.
• discover — Create/fork. Default true. Runs the MCP tools/list handshake at registration; the node output returns a discovered count. Best-effort: an unreachable server still registers.
• defDescription — Create/fork. Operator-visible description of the registration.
• promote — Create/fork. Default true. Auto-promotes the new registration to active.
• parentDefId (required) — Fork only. def_id of the row to fork.
• overlay — Fork only. JSON diff applied over the parent row, e.g. {"URL":"https://staging.example.com"}.
• defId (required) — Required for promote (the def_id to activate). Optional for retire: leave empty to retire the active version of the name.
• contentSha256 (required) — Verify only. Local content hash to compare against the deployed active row.

Output shape

One output item per input item, containing the LoomCycle MCPServerDef response for the chosen op. Create/fork/get/list return registration rows, verify returns a match result, and create/fork include a discovered tool count when discovery ran.

The source is truncated, so the exact output shape is inferred from the client docs. Tool-level refusals (disallowed transport or host, a name colliding with a yaml server) and HTTP errors are raised as errors, with bearer fragments redacted. Registering identical content is content-addressed and idempotent, so it doesn't create a new version. This is an operator-admin endpoint and requires the bearer token.

Examples

Example 1: Register a new MCP server and make it usable by agents immediately

Operation create; name=crm-tools; transport=streamable-http; url=https://mcp.example.com/v1; header Authorization=Bearer ${LOOMCYCLE_CRM_TOKEN}; discover=true; promote=true.

Example 2: Stage a URL change without touching the active version

Operation fork; parentDefId=; overlay={"URL":"https://staging.example.com"}; promote=false. Later run promote with the new defId.

Example 3: Check whether the deployed config matches a local hash before re-registering

Operation verify; name=crm-tools; contentSha256=.

Links

• n8n community nodes installation guide