Give employees and agents one place to find approved connectors, skills, and plugins instead of hunting through local configs, docs, and one-off links.
Distribute
Package connectors, skills, and plugins with instructions, required tools, owner, access state, and supporting context so agents across the company can use them.
Use adoption to decide what to support
See what each connector, skill, or plugin can touch, how often it gets used, where it fails, who owns it, and which local patterns should become supported infrastructure.
Frequently asked questions
Runlayer Catalog can include approved MCP connectors, skills, and plugins. It is the registry for reusable agent capabilities the company wants people and agents to find and use.
MCP Gateway governs tool access at runtime. Runlayer Catalog makes approved connectors, skills, and plugins discoverable, reusable, and tied to ownership, dependencies, and usage.
Teams can package useful connectors, skills, and plugins for reuse, while platform owners control review, ownership, dependencies, sharing, and lifecycle.
Runlayer Catalog items can be shared with approved users, groups, roles, teams, agents, or clients. Runtime access still depends on policy and credentials.
Yes. A connector, skill, or plugin can depend on approved internal MCPs and custom capabilities that platform teams publish through Runlayer.
Usage, failures, access decisions, findings, owners, versions, and audit history show which capabilities are worth improving, retiring, or promoting.
