LoomCycle MCP Server icon

LoomCycle MCP Server

Register and manage dynamic loomcycle MCP servers over HTTP

LoomCycle MCP Server

AI-generated

Summary

Register and manage LoomCycle MCP server definitions over HTTP. Create or fork registrations, inspect versions, promote or retire a version, refresh discovered tools, or compare a supplied content hash with the active definition.

Inputs

  • Operation (required) — Choose Register, Fork, Get, List Versions, Promote, Rediscover, Retire, or Verify.
  • Name (required) — For Register, the new server name. Agents can reference its tools as mcp__<name>__<tool> in allowed_tools.
  • Name or ID (required) — For Get, List Versions, Rediscover, and Verify, select or enter the server name. For Retire, select or enter the server name; an optional Def ID can target a specific version.
  • Def ID (required) — For Promote, the version ID to make active. For Fork, the required Parent Def ID identifies the version to branch from.
  • Transport (required) — For Register, choose HTTP or Streamable HTTP; stdio servers must be declared in loomcycle.yaml.
  • URL (required) — For Register, the MCP endpoint URL. Its hostname must be in LoomCycle's HTTP host allowlist.
  • Headers — For Register, optional headers sent on MCP calls. Values can use LoomCycle environment-variable tokens or per-run substitutions such as ${run.user_bearer:-FALLBACK}.
  • Description — Optional operator-visible description for a new registration or fork.
  • Overlay (JSON) — For Fork, a JSON diff applied to the parent definition, such as changing its URL.
  • Promote to Active — For Register or Fork, whether to make the new version active immediately; defaults to true.
  • Content SHA256 (required) — For Verify, the local content hash to compare with the deployed active row.

Output shape

A single item containing a result field with the LoomCycle MCPServerDef response.

The response structure varies by operation: create, fork, get, and list return definition data; verify returns a verification result. Operations requiring bearer authentication use the LoomCycle API credential. Retire may identify a version by optional Def ID or retire the active version for the selected name.

Links

Discussion