Hub/AI Plugins/Org admin controls
Which ecosystems support Org admin controls?
Organization admins can allow, block, require or scope plugins.
7 Yes0 Partial
Verified Yes: ChatGPT plugins, Codex plugins, Claude plugins (apps), Claude Code plugins, GitHub Copilot / VS Code plugins, Gemini app & Gemini Enterprise, Microsoft 365 Copilot plugins.
| Ecosystem | Status | Notes | Source |
|---|---|---|---|
| ChatGPT pluginsOpenAI | Yes | Admin console: install policy (Available/Installed), RBAC, bulk edit up to 25 plugins. | Source |
| Claude Code pluginsAnthropic | Yes | Managed settings allowlist or block marketplaces and force-install plugins. | Source |
| Claude plugins (apps)Anthropic | Yes | Owners set each plugin to Not available, Available, Installed by default or Required. | Source |
| Codex pluginsOpenAI | Yes | Admin-managed config and requirements.toml (features.plugin_sharing). | Source |
| Gemini app & Gemini EnterpriseGoogle | Yes | Gemini Enterprise: OAuth workforce sign-in; admins enable actions, which are off by default. | Source |
| GitHub Copilot / VS Code pluginsGitHub / Microsoft | Yes | Enterprise managed settings require or block plugins; repo defaults in .github/copilot/settings.json. | Source |
| Microsoft 365 Copilot pluginsMicrosoft | Yes | Availability by publisher category and user/group, block, access requests, per-tool control on MCP servers. | Source |
| Cursor pluginsAnysphere | Unknown | — | |
| Gemini CLI extensionsGoogle | Unknown | No admin controls for extensions found in the docs. | — |
| Goose extensionsBlock / AAIF | Unknown | — |
Other AI Plugins features
Weekly, free
What changed in AI integrations
One short email when MCP clients, plugin ecosystems, IDE integrations, AI plan prices or security advisories change. Every item is sourced.