A governed home for everything agents can use

A simple way for companies to version, approve, and distribute skills, plugins, and MCP servers across their agent ecosystem.

The idea

A direction we believe is worth exploring

Agent extensions are starting to look like a new software supply chain, but most companies still manage them across repositories, local configuration, and individual agent clients. We imagine Registry as the trusted layer between the people building extensions and the agents using them.

What it could become

Publish from Git

Keep code and review where teams already work, while turning approved versions into trusted releases.

Set policy once

Decide which extensions are required, recommended, allowed, or forbidden across the company.

Distribute anywhere

Translate one approved package into the configuration expected by each supported agent client.

Part of Nimbase

Context remains the foundation

Nimbase governs what agents can know. Registry would extend that same philosophy to what agents can use—without making either product dependent on the other.

Tell us what you would need