How MCP and A2A registries make governance discoverable to agents
Put MCP servers and A2A agents into the same control-plane model as services and rules.
For agents to use service governance, do not maintain a second prompt-time catalog. Register MCP servers, tools, A2A agent cards, and skills as first-class control-plane resources.
Why the control plane
- Shared Namespace environment boundaries.
- Reuse of API, store, CacheManager, and authorization.
- Revisioned catalogs so clients know when to refresh.
- Auditable History instead of local agent config drift.
Boundaries
| Capability | Does | Does not |
|---|---|---|
| MCP Registry | Register servers/tools for discovery and allowlists | Replace backend execution semantics |
| A2A Registry | Register cards, skills, protocol metadata | Act as a task proxy or runtime |
| Pole Agent | Read queries + human-confirmed config drafts | Auto-publish or delete |