A GitHub template for packaging any MCP server as an installable plugin for GitHub Copilot in VS Code.
Click "Use this template" on GitHub to create your own repo.
Edit server/index.js — add tools and resources to the objects at the top of the file. The included server implements the MCP protocol directly with no dependencies.
If you need npm packages, add them to package.json and see Adding dependencies below.
Search for YOUR_ across the repo and replace:
| Placeholder | Where | What |
|---|---|---|
YOUR_PLUGIN_NAME | plugin.json, .mcp.json, package.json, server/index.js | Your plugin's name (kebab-case) |
YOUR_DESCRIPTION | plugin.json | What your plugin does |
YOUR_NAME | plugin.json | Your name |
YOUR_EMAIL | plugin.json | Your email |
YOUR_USERNAME | plugin.json | Your GitHub username |
YOUR_REPO | plugin.json | Your GitHub repo name |
Share your repo — users install the plugin directly from the GitHub URL.
Important: The plugin is read from the repository's default branch. Make sure your changes are merged to
main/masterbefore distributing.
Want to test your plugin before sharing it? Here's how:
Fill in the placeholders — follow step 3 above to replace all YOUR_ values with your own info.
Push to GitHub — commit your changes and push the repo to GitHub. Make sure it's on your default branch (main or master).
Install your own plugin — open the VS Code command palette (F1 or Ctrl+Shift+P), select "Chat: Install Plugin from Source", and paste your repo URL:
https://github.com/YOUR_USERNAME/YOUR_REPO
Hit enter and the plugin is installed.
Test it — ask GitHub Copilot:
Test the connection with my-plugin-name
Copilot should call the hello tool and return:
"Hello from your MCP plugin!"
Replace my-plugin-name with whatever you set YOUR_PLUGIN_NAME to.
If that works, your plugin is wired up correctly and ready to distribute.
F1 or Ctrl+Shift+P)https://github.com/AUTHOR/REPO) and hit enterThat's it — GitHub Copilot can now access the plugin's tools.
your-plugin/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
├── .mcp.json # MCP server declaration
├── server/
│ └── index.js # Your MCP server (edit this)
├── package.json # Plugin metadata
└── README.md
.mcp.json tells Claude Code to start your server via node server/index.js${CLAUDE_PLUGIN_ROOT} points to the plugin's install directoryIf your server needs npm packages:
package.jsonhooks/hooks.json with a SessionStart hook to auto-install them:{
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "diff -q \"${CLAUDE_PLUGIN_ROOT}/package.json\" \"${CLAUDE_PLUGIN_DATA}/package.json\" >/dev/null 2>&1 || (cd \"${CLAUDE_PLUGIN_DATA}\" && cp \"${CLAUDE_PLUGIN_ROOT}/package.json\" . && npm install --production) || rm -f \"${CLAUDE_PLUGIN_DATA}/package.json\""
}
]
}
]
}
}
NODE_PATH to .mcp.json so your server can find the installed modules:{
"mcpServers": {
"your-plugin": {
"command": "node",
"args": ["${CLAUDE_PLUGIN_ROOT}/server/index.js"],
"env": {
"NODE_PATH": "${CLAUDE_PLUGIN_DATA}/node_modules"
}
}
}
}
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub xanderscannell/mcp-installerContext Degradation Syndrome (CDS) Prevention Framework - Maintain project context across Claude Code sessions using structured .context/ files
Generates and enforces project coding guidelines. Simple mode: flat rule list, direct review. Full mode: categorized guidelines with severity levels and structured reports.
Context management, project guidelines, and code review for AI coding assistants. Prevent context degradation, enforce coding standards, and get structured code reviews — all in one plugin.
MCP server management and integration tools
MCP server development helper with tool and resource scaffolding
Manage MCP servers - discover, analyze, execute tools/prompts/resources. Use for MCP integrations, capability discovery, tool filtering, programmatic execution, or encountering context bloat, server configuration, tool execution errors.
Memory compression system for Claude Code - persist context across sessions
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
Streamline people operations — recruiting, onboarding, performance reviews, compensation analysis, and policy guidance. Maintain compliance and keep your team running smoothly.