universal-plugins-for-ai-agents

Universal plugin catalog for AI agents.

This repository holds portable, production-ready plugin directories plus a small number of honest agent-specific hosted connector entries where the vendor only documents one supported lane today.

The catalog currently covers install paths across these agent ecosystems:

• Claude
• Codex
• Gemini
• OpenCode
• Cursor

Current plugins:

slack intentionally remains Claude and Cursor only. Slack's current MCP docs list Claude.ai, Claude Code, Cursor, and Perplexity as supported partner clients, but this catalog only ships targets that overlap with the current plugin-kit-ai target model and official connection flows. Perplexity is not a target in this catalog, and Slack does not currently document hosted MCP connection flows here for Codex, Gemini, or OpenCode.

figma intentionally remains Claude, Codex, and Cursor only. Figma's current remote MCP docs explicitly limit hosted access to clients listed in the Figma MCP Catalog, and the published install guides in this area are for Claude Code, Codex, Cursor, and VS Code, not Gemini or OpenCode.

gmail, google-calendar, and microsoft365 intentionally remain Claude only. Anthropic documents these as Claude-hosted connectors, and its official open-source Claude plugin examples wire them only inside Claude plugin .mcp.json configs, not as general hosted connection flows for Codex, Gemini, OpenCode, or Cursor.

Coverage notes for the screenshot-aligned app set:

• Teams, SharePoint, Outlook Email, and Outlook Calendar are represented by the single canonical microsoft365 plugin because Anthropic documents one Microsoft 365 connector spanning all four surfaces, not four separate hosted MCP servers.
• Google Drive is intentionally documented as a native Claude integration gap here, not shipped as a catalog plugin. Anthropic's current official plugin examples publish hosted MCP URLs for gmail, google-calendar, and microsoft365, but do not publish a standalone Google Drive MCP endpoint in the same packageable form.

Discovery And Marketplace Use

This repository now ships the root discovery artifacts each ecosystem actually supports:

• Claude Code marketplace catalog: .claude-plugin/marketplace.json
• Codex repo marketplace catalog: .agents/plugins/marketplace.json
• Cursor marketplace catalog: .cursor-plugin/marketplace.json
• Gemini bundled root extension: gemini-extension.json

Claude Code can add this repository directly as a marketplace:

/plugin marketplace add 777genius/universal-plugins-for-ai-agents

Then install any listed plugin:

/plugin install context7@universal-plugins-for-ai-agents

For the skills-first code navigation plugin, use the one-command installer. It installs the plugin first, then offers optional setup for Semble, CGC, and Serena. It requires Bash, curl, and git; it does not require preinstalling plugin-kit-ai, npm, or Node. If an older plugin-kit-ai is found, it bootstraps 1.2.4+ for Cursor support:

curl -fsSL https://raw.githubusercontent.com/777genius/universal-plugins-for-ai-agents/main/plugins/agent-code-navigator/scripts/install.sh | bash

The agent CLIs you want to configure still need to be installed and working in PATH. On Windows, use WSL or Git Bash rather than native PowerShell.

For plugin-only install when plugin-kit-ai is already installed:

plugin-kit-ai add github:777genius/universal-plugins-for-ai-agents//plugins/agent-code-navigator

To install plugin-kit-ai globally first:

brew install 777genius/homebrew-plugin-kit-ai/plugin-kit-ai
# or
npm install -g plugin-kit-ai@latest

If you use an already installed plugin-kit-ai, make sure it is 1.2.4 or newer. Cursor local plugin packages require the stable Cursor package lane released in 1.2.4.

Codex reads repo-local marketplaces from .agents/plugins/marketplace.json. Clone this repository, open it as the working repo in Codex, and the marketplace will be available from the local repo catalog.

Cursor now follows the official repo-level marketplace layout used by Cursor plugin repositories and team marketplaces: .cursor-plugin/marketplace.json in the root, plus generated plugins/*/.cursor-plugin/plugin.json manifests for every installable plugin.

Gemini is different. Official Gemini gallery indexing is repository-rooted and expects a public repository with gemini-extension.json at the repository root or archive root plus the gemini-cli-extension GitHub topic. This repository now publishes a bundled root Gemini extension for gallery and scanner visibility, while keeping the authored per-plugin gemini-extension.json files under plugins/*/. The bundled root extension mirrors the MCP-backed Gemini-compatible plugins from this catalog; skills-first plugins such as agent-code-navigator install through their own plugin package. Prebuilt Gemini archives are published on the GitHub Releases page for tagged versions.

OpenCode still relies on the native opencode.json artifacts committed inside each plugin directory.

Marketplace drift is also gated in CI:

• python3 scripts/validate_marketplaces.py verifies that the Claude, Codex, Cursor, and Gemini root discovery artifacts stay aligned with the checked-in plugin manifests under plugins/*, and also fails on duplicate MCP transport signatures across different plugins
• python3 scripts/sync_cursor_marketplace.py regenerates .cursor-plugin/marketplace.json and plugins/*/.cursor-plugin/plugin.json
• python3 scripts/sync_gemini_marketplace.py regenerates the bundled root gemini-extension.json
• python3 scripts/package_gemini_extensions.py builds release-ready Gemini archives for the bundled root extension plus every MCP-backed Gemini-compatible plugin
• .github/workflows/marketplace-visibility.yml runs codex-plugin-scanner==2.0.12 across the Claude, Codex, Gemini, and OpenCode ecosystems and uploads JSON scan artifacts for review, while the validate step separately gates Cursor marketplace drift
• .github/workflows/gemini-gallery-release.yml packages Gemini archives on version tags and uploads them to GitHub Releases

Layout

Each plugin lives inside plugins/.

Example:

• plugins/context7/plugin/plugin.yaml
• plugins/context7/plugin/mcp/servers.yaml
• optional plugins/context7/plugin/targets/...
• plugins/context7/plugin/README.md
• plugins/context7/CLAUDE.md and plugins/context7/AGENTS.md mark the boundary between authored and generated files
• plugins/context7/README.md is a short generated entrypoint that points to plugins/context7/plugin/README.md
• generated native artifacts are committed at the plugin root

Authoring Flow

Each plugin should keep its authored source of truth in:

• plugin/plugin.yaml
• optional plugin/mcp/servers.yaml
• optional plugin/targets/<platform>/...
• edit only plugin/; treat plugin-root manifests as generated outputs

Then generate and validate with plugin-kit-ai.