UluOps Registry MCP

What UluOps Registry MCP does

UluOps Registry MCP exposes the UluOps Registry API through MCP over stdio. The package is intended for AI workflow definitions such as agents, commands, workflows, and pipelines, and provides 44 tools and 4 resources according to its project description. It acts as a protocol adapter: registry-side processing, validation, storage, and rendering remain in the API.

Read operations include filtered catalog listing, keyword or pattern search, single-definition retrieval, version listing, dependency and dependent graphs, fork lineage, execution statistics, and model or provider lookup. Model tools can resolve aliases such as sonnet to a provider and model ID.

Write operations cover the definition lifecycle. Agents can create drafts, update them, publish them, deprecate them with a reason, archive deprecated versions, and delete versions when registry dependency and fork rules permit. A combined update-and-publish operation, batch publishing for up to 20 versions, and fork creation are also available.

How it works

The server translates MCP JSON-RPC requests into calls to the Registry REST API. Definitions can be supplied as inline YAML or, for applicable operations, through a file path. Validation does not store the definition. Rendering returns Markdown inline or writes it to a host-side file. Version comparison supports section summaries, structural field changes with a suggested bump, and unified output; an optional combined contract can include an exact YAML patch.

Updating has smart version behavior: when the target is already published or absent and YAML is supplied, the operation can create a new draft instead. Translation tools retranslate definitions with the latest translator version, while upgrade tools convert legacy-format definitions.

Setup and configuration

Node.js 20.3 or newer is required. Install or run the package with npx -y @uluops/registry-mcp, then add it as an MCP server using the command value npx and the package name as its argument. Supply an API key in the MCP environment; keys are obtained from the UluOps API-key settings and use the ulr_ prefix.

ULUOPS_ORG_SLUG scopes definition writes. ULUOPS_REGISTRY_URL selects the API endpoint, while ULUOPS_REGISTRY_TIMEOUT and ULUOPS_REGISTRY_RETRIES control request behavior. Logging, file containment, and rendered-output locations can be configured with the logging, WORKSPACE_DIR, and OUTPUT_BASE_DIR variables. No .env file is required.

Tools and capabilities

• Browse and search definitions using type, status, domain, visibility, name, tags, relevance, pagination, sorting, and match modes.
• Retrieve, validate, render, create, update, publish, deprecate, archive, delete, and batch-publish definitions.
• Compare versions, list versions, inspect dependencies, view dependents, and query execution statistics.
• Fork definitions, check fork eligibility, inspect lineage, retranslate content, and upgrade legacy definitions.
• List models and providers, retrieve model details, list aliases, and resolve aliases.

Limitations and notes

The API key is sent to the configured registry URL on every request. By default, registry hosts are restricted to *.uluops.ai and loopback addresses. ULUOPS_ALLOW_ANY_REGISTRY_HOST=1 enables other hosts, and private-network or cloud-metadata addresses additionally require ULUOPS_ALLOW_PRIVATE_REGISTRY=1.

File inputs and rendered outputs are constrained to configured base directories to reduce path traversal risk. output_path writes on the MCP server host, so remote clients should request inline Markdown instead. Existing output files require explicit overwrite permission, and unsafe traversal or symlink paths are refused.

Organization context applies to definition writes, while reads remain broadly accessible according to registry membership and visibility. Deletion can be blocked when dependents or forks prevent removal; the API returns a recovery action for such cases.