Feature Request
GitHub Copilot CLI already supports a plugin marketplace specification — a marketplace.json registry format that allows teams and the community to package, distribute, and install custom skills, agents, hooks, and MCP server configs via copilot plugin marketplace add [owner]/[repo].
This format is currently only supported in the Copilot CLI. It would be highly valuable to bring this same plugin marketplace support to the JetBrains IDE plugin, so that users can install and use community plugins directly from their IDE — just as they can from the terminal.
What this would enable
- Install marketplace plugins from JetBrains IDEs — browse and add plugins from a
marketplace.json registry without leaving the IDE
- Full parity with Copilot CLI — skills, agents, hooks, and MCP servers defined in marketplace plugins should work in IntelliJ just as they do in the CLI
- Team/enterprise extensibility — organizations can maintain private plugin marketplaces and have them work across both CLI and IDE
Cross-tool compatibility with Claude Code format
It's worth noting that Claude Code uses a nearly identical plugin format (.claude-plugin/ directory with a plugin.json manifest + skills/, agents/, hooks/ directories and a marketplace.json registry). Several teams are already building plugin marketplaces that target both Copilot CLI and Claude Code.
Supporting this format in the IntelliJ plugin would maximize portability — a single plugin repo could serve users of Copilot CLI, Copilot in JetBrains, and Claude Code without maintaining separate implementations.
Reference
Feature Request
GitHub Copilot CLI already supports a plugin marketplace specification — a
marketplace.jsonregistry format that allows teams and the community to package, distribute, and install custom skills, agents, hooks, and MCP server configs viacopilot plugin marketplace add [owner]/[repo].This format is currently only supported in the Copilot CLI. It would be highly valuable to bring this same plugin marketplace support to the JetBrains IDE plugin, so that users can install and use community plugins directly from their IDE — just as they can from the terminal.
What this would enable
marketplace.jsonregistry without leaving the IDECross-tool compatibility with Claude Code format
It's worth noting that Claude Code uses a nearly identical plugin format (
.claude-plugin/directory with aplugin.jsonmanifest +skills/,agents/,hooks/directories and amarketplace.jsonregistry). Several teams are already building plugin marketplaces that target both Copilot CLI and Claude Code.Supporting this format in the IntelliJ plugin would maximize portability — a single plugin repo could serve users of Copilot CLI, Copilot in JetBrains, and Claude Code without maintaining separate implementations.
Reference