Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-08-25 18:25:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: publish from main

Browse Source
This commit is contained in:
github-actions[bot]
2026-07-31 00:26:48 +00:00
parent 6212c7a01b
commit 6dc78056b5
2 changed files with 33 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/src/content/docs/learning-hub/installing-and-using-plugins.md
+21 -1
View File
@@ -3,7 +3,7 @@ title: 'Installing and Using Plugins'
description: 'Learn how to find, install, and manage plugins that extend GitHub Copilot CLI with reusable agents, skills, hooks, and integrations.'
authors:
- GitHub Copilot Learning Hub Team
lastUpdated: 2026-07-13
lastUpdated: 2026-07-28
estimatedReadingTime: '8 minutes'
tags:
- plugins
@@ -274,6 +274,26 @@ If you only need a single agent or skill (rather than a full plugin), you can st
See [Using the Copilot Coding Agent](../using-copilot-coding-agent/) for details on this approach.
## Open Plugin Spec v1 Compatibility
*(v1.0.74+)* GitHub Copilot CLI supports **Open Plugin Spec v1** plugin manifests, in addition to its own `plugin.json` format. This means plugins authored for other AI tools or platforms using the Open Plugin Spec standard can be installed and used in Copilot CLI without any modification.
### What This Means for You
If you encounter a plugin from the broader AI ecosystem (outside GitHub's own marketplace) that ships with an Open Plugin Spec v1 manifest, you can install it directly:
```bash
copilot plugin install /path/to/openspec-plugin
```
The CLI reads the manifest, discovers the bundled agents, skills, and MCP server configuration, and integrates them the same way it handles native Copilot plugins.
### `mcp.json` Configuration
Open Plugin Spec v1 also standardizes how MCP server configuration is bundled in plugins. A plugin can now include an `mcp.json` file at its root to declare MCP servers it requires — using the same format as `.mcp.json` or `.github/mcp.json` in your repository. When you install such a plugin, its MCP server configuration is automatically merged into your active server list.
This is useful for plugins that bundle dedicated tooling (for example, a database plugin that ships its own MCP server) — users get both the agent/skill and the required MCP server in a single install step.
## Best Practices
- **Start with a marketplace plugin** before building your own — there may already be one that fits your needs