Definition

Capability registry

Last updated

A capability registry is a single definition of what an agent can do inside a product (invite a teammate, change a plan, download an invoice), defined once and rendered two ways: as cursor motion for human users and as typed MCP tools for their AI agents. Neither surface is maintained separately.

New to the category? Read what AI customer support is and how it works.

Why define capabilities once?

Because a duplicated definition drifts. If the cursor's version of "change plan" and the agent's tool version live in different places, one updates and the other rots. A single registry means a capability's permissions, confirmation copy and effect string are identical whether a person or an agent invokes it.

How do agents get the same permissions as users?

Each capability carries the scope of the user who invoked it. An agent connected to a user's endpoint inherits exactly that user's permissions, never more, and every call states its effect before it runs. The registry is the enforcement point, so there is no separate agent-permission model to keep in sync.

What does a capability registry look like in practice?

A SaaS product defines one capability, change_plan. A person who asks how to upgrade is walked to the billing screen and confirms the change there, while that person's own AI agent calls the same change_plan tool over a scoped MCP endpoint. Both paths share one definition, one set of permissions and one stated effect.

How does Peeve handle a capability registry?

Peeve keeps one capability registry that renders as cursor motion for people and as typed MCP tools for their agents, each tool stating its effect before it runs. Agents get the same permissions as the user, never more. The agent channel is on every plan: 5 grants per user on Starter, 20 on Growth and unlimited on Scale.

See it in your product. 14 days free. No card. No call.