Create beautiful one-click install badges for your Model Context Protocol (MCP) servers that work with VS Code, VS Code Insiders, Visual Studio, Cursor, Goose, and LM Studio.
- β Easy to Use: Simple form-based interface to generate badges
- π¨ Multiple IDEs: Support for VS Code, VS Code Insiders, Visual Studio, Cursor, Goose, and LM Studio
- π§ Six Configuration Types:
- Remote HTTP Server (HTTP/SSE transport)
- NPX Package (Node.js packages)
- UVX Package (Python packages with uv)
- DNX Package (.NET packages)
- Docker Container
- Local Binary (custom commands)
- π Copy to Clipboard: One-click copy of generated markdown
- π README Export: Generate complete "Getting Started" section for your README with installation instructions for all supported IDEs
- π₯οΈ CLI Commands: Generate cross-platform
code --add-mcpcommands for terminal installation - ποΈ Live Preview: See your badges before copying
- π¨ Beautiful Design: Modern, responsive UI with VS Code Insiders green theme
Visit the live application: MCP Badge Creator
MCP badges provide a seamless way for users to install your Model Context Protocol servers directly into their IDE with a single click. These badges:
- Generate proper install URLs for each IDE
- Handle URL encoding of JSON configurations
- Follow official badge styling guidelines
- Support all MCP server deployment methods
For MCP servers hosted remotely and accessible via HTTP/HTTPS with SSE transport.
{
"servers": {
"server-name": {
"type": "http",
"url": "https://your-server-url.com"
}
}
}For MCP servers distributed as NPM packages, commonly used in the MCP ecosystem.
{
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem"],
"env": {}
}Common Examples:
@modelcontextprotocol/server-filesystem- File system operations@modelcontextprotocol/server-github- GitHub API integration@modelcontextprotocol/server-postgres- PostgreSQL database access
For Python-based MCP servers using uv/uvx for fast, reliable Python package execution.
{
"command": "uvx",
"args": ["--from", "mcp-server-git", "mcp-server-git"],
"env": {}
}Alternative without --from:
{
"command": "uvx",
"args": ["mcp-server-git"],
"env": {}
}For .NET-based MCP servers using DNX package manager.
{
"command": "dnx",
"args": ["[email protected]", "--yes"],
"env": {}
}For MCP servers packaged as Docker images.
{
"command": "docker",
"args": ["run", "-i", "--rm", "your-username/your-image"],
"env": {}
}For MCP servers running as local executables with custom commands.
{
"command": "node",
"args": ["path/to/server.js"],
"env": {}
}Other common commands:
python- For Python scriptsuv- For uv-managed Python projects- Custom binaries in your PATH
- Fill in Server Details: Enter your MCP server name and configuration
- Choose Configuration Type: Select between HTTP, NPX, UVX, DNX, Docker, or Local
- Select Target IDEs: Choose which IDEs to generate badges for
- Copy & Use:
- Copy the generated markdown badges for your README
- Copy the JSON configuration for manual setup
- Copy the CLI commands for terminal installation
- Export a complete "Getting Started" README section with installation instructions for all IDEs
The badge creator supports one-click install badges for the following IDEs:
- VS Code - Visual Studio Code stable release
- VS Code Insiders - Visual Studio Code preview builds
- Visual Studio - Full IDE experience with MCP support
- Cursor - AI-powered code editor with MCP integration
- Goose - AI coding assistant with MCP support
- LM Studio - Local LLM platform with MCP server support
Each IDE has its own deeplink protocol for seamless installation:
- VS Code/Insiders:
vscode.dev/redirect/mcp/install - Visual Studio:
vs-open.link/mcp-install - Cursor:
cursor://anysphere.cursor-deeplink/mcp/install - Goose:
goose://install-mcp - LM Studio:
lmstudio://add_mcp
The "Getting Started README" tab generates a complete, ready-to-use Getting Started section for your project's README that includes:
- All one-click install badges for supported IDEs
- Detailed manual installation instructions for each IDE
- CLI commands for VS Code and VS Code Insiders
- Configuration details and examples
- Help section with links to MCP documentation
Simply click the tab, copy the content, and paste it directly into your README.md file!
The badge creator also generates ready-to-use CLI commands for installing MCP servers:
# For VS Code
code --add-mcp '{\"name\":\"server-name\",\"command\":\"npx\",\"args\":[\"-y\",\"package\"],\"env\":{}}'
# For VS Code Insiders
code-insiders --add-mcp '{\"name\":\"server-name\",\"command\":\"npx\",\"args\":[\"-y\",\"package\"],\"env\":{}}'These commands work cross-platform in:
- β PowerShell (Windows)
- β Bash (Linux/macOS)
- β Zsh (macOS default)
See CLI-COMMANDS.md for detailed documentation and examples.
- Node.js 18+
- npm or yarn
# Clone the repository
git clone https://github.com/YOUR_USERNAME/mcp-badge-creator.git
cd mcp-badge-creator
# Install dependencies
npm install
# Start development server
npm run dev# Build for production
npm run build
# Preview production build
npm run previewThis project is configured to automatically deploy to GitHub Pages using GitHub Actions.
- Push your code to GitHub
- Go to your repository Settings > Pages
- Under "Build and deployment", select "GitHub Actions" as the source
- The site will automatically deploy on every push to the main branch
Alternatively, you can use gh-pages:
# Install gh-pages
npm install --save-dev gh-pages
# Deploy
npm run deployContributions are welcome! Please feel free to submit a Pull Request.
MIT License - feel free to use this tool for your projects!
- Badge documentation based on MonkeyMCP by James Montemagno
- Built with Vite and React
- Badges powered by Shields.io
Made with β€οΈ for the MCP community
The project is undergoing a migration from a monolithic App.css (~1,945 lines) to a modular CSS Modules architecture with a global design system.
- Phase 1: Global design system (
tokens.css,themes.css,utilities.css) - Phase 2: External SVG icons (
chevron-down.svg,hamburger.svg) - Phase 3: Shared component modules (
Button,Card,Form,Badge) - Phase 4: App layout migration (
App.module.css, refactorApp.tsx) - Phase 5: Home page migration (
Home.module.css) - Phase 6: Extensions page migration (
Extensions.module.css) - Phase 7: Complex pages migration (
MCP.module.css,Packages.module.css,Settings.module.css)
- Reduce stylesheet size and improve maintainability
- Eliminate hardcoded colors and duplicated patterns
- Standardize breakpoints (β€768px, 769β1024px, β₯1025px)
- Introduce reusable component styling primitives
- Preserve backward compatibility during migration (legacy class names kept temporarily for tests)
Follow progress or contribute by checking the plan in specs/CSS_MODULES_MIGRATION_PLAN.md.