Approved MCPs
Discover and assign reviewed MCP servers, tools and versions. A catalog entry is not blanket action permission.
View in the catalogBring tools, skills and configuration into one approved environment. Know what should be there—and what actually is.
Discuss your use caseDiscover and assign reviewed MCP servers, tools and versions. A catalog entry is not blanket action permission.
View in the catalogReview, release, pin and update skills and client-specific plugins with provenance and compatibility.
View in the catalogManage supported model preferences and observed settings without pooling subscriptions or provider quotas.
View in the catalogApply approved profiles across enrolled contexts while preserving unmanaged settings and independent authorization.
View in the catalogPin artifact and profile revisions. Activate upgrades or rollbacks deliberately, not on every source edit.
View in the catalogReuse reviewed runtime and deployment patterns with explicit prerequisites, ownership and approval.
View in the catalogDistribute managed settings and opaque credential references, never raw secrets in portable profiles.
View in the catalogCompare expected, approved, installed, loaded and observed state. Explain differences and precise unknowns.
View in the catalogBound approved execution by qualified filesystem, network, credential, time and resource controls.
View in the catalogChoose a profile, authorize the intended connections, review the differences, and verify the resulting state. Shared configuration never means shared login sessions.
Client adapters must be qualified. Installed, loaded and observed are different states; unknown stays unknown.