Skip to content
Ren Docs
Book a demo

Registry

The Ren registry is the public catalog where organizations publish reusable agents, skills, MCPs, and blueprints for anyone to discover and install. It’s how a capability moves from a single organization to shared infrastructure.

It’s a publishing system, not a marketplace: no ratings or reviews. Organizations publish what they build; others find it by slug and install it.

Publishers

Every published resource is attributed to a publisher: your organization’s namespace on the registry, with a unique slug (e.g. acme-corp) that prefixes everything you publish. There’s one publisher per organization, created automatically the first time you publish.

Publishing

Publishing makes a resource public and discoverable. When you publish an agent, Ren first publishes everything it depends on (the skills and MCPs on its latest version), so a published resource never has a missing dependency. Publishing a blueprint works the same way for the agents, skills, MCPs, and replays it references.

Deprecation, not deletion

Published resources can’t be unpublished. Projects depending on them would break. Instead you deprecate: the resource drops out of registry search but stays reachable by direct slug or ID, so existing installs keep working. A deprecation message can point users to a replacement. Deprecation is reversible.

Discovering

Browse published resources from the CLI, one type at a time:

Terminal window
ren registries agents list   # browse published agents
ren registries skills list   # browse published skills
ren registries mcps list     # browse published MCPs
ren publishers me            # show your organization's publisher

Where to go next

  • Scopes: how publishing changes a resource’s visibility.
  • Blueprints: installable setups that bundle agents, skills, and MCPs.
  • Agents: the main resource type published to the registry.