VS Code Button Generator
Generates VS Code install buttons and markdown badges for MCP servers and GitHub Copilot extensions. Creates one-click installation experiences with automated redirect URLs.
Generates VS Code install buttons and markdown badges for MCP servers and GitHub Copilot extensions, providing one-click installation experiences through automated redirect URL creation with support for NPX-based servers, environment variables, and chat instructions.
What it does
- Generate VS Code install buttons for NPX-based MCP servers
- Create install badges from MCP configuration objects
- Generate Copilot extension buttons from GitHub files
- Create install buttons from raw URLs for chat instructions
Best for
About VS Code Button Generator
VS Code Button Generator is a community-built MCP server published by burkeholland that provides AI assistants with tools and capabilities via the Model Context Protocol. VS Code Button Generator creates install buttons and badges for MCP servers, enabling one-click setup with automated URL It is categorized under developer tools. This server exposes 4 tools that AI clients can invoke during conversations and coding sessions.
How to install
You can install VS Code Button Generator in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
VS Code Button Generator is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Tools (4)
Generate VS Code Stable and Insiders MCP install button markdown for an NPX-based server.
Generate install buttons from a raw MCP JSON-like config object and a server name.
Generate VS Code install buttons for a raw URL to chat instructions, prompts, or chat modes.
Generate VS Code install buttons for a GitHub file using owner/repo/path and optional branch.
mcp-vsc-button-gen
A tiny MCP server that generates VS Code MCP install buttons (Stable + Insiders) for NPX-based servers.
- Runtime: Node (stdio transport)
- Command: npx mcp-vsc-button-gen
You can run it directly via NPX (no install):
npx mcp-vsc-button-gen
Install in VS Code
Tools
- make_install_buttons
- Input: { name: string, inputs?: MCPInput[], config?: CommandConfig }
- Output: Markdown string with two badges/links.
- from_mcp_config
- Input: { name: string, mcp: { inputs?: MCPInput[], config?: CommandConfig } }
- Output: Markdown string with two badges/links.
- copilot_buttons_from_raw
- Input: { kind: 'chat-instructions' | 'chat-prompt' | 'chat-mode', url: string }
- Output: Markdown with two badges linking to vscode.dev/insiders redirect for Install
- copilot_buttons_from_github
- Input: { kind: 'chat-instructions' | 'chat-prompt' | 'chat-mode', owner: string, repo: string, path: string, branch?: string }
- Output: Markdown with two badges as above
Types:
- MCPInput: { type: 'promptString', id: string, description?: string, password?: boolean }
- CommandConfig: { command: 'npx', args?: string[], env?: Record<string,string> }
Example
Input:
{
"name": "supabase",
"inputs": [
{ "type": "promptString", "id": "supabase-access-token", "description": "Supabase personal access token", "password": true }
],
"config": {
"command": "npx",
"args": ["-y", "@supabase/mcp-server-supabase@latest", "--readonly", "--project-ref=$SUPABASE_MCP_PROJECT_REF"],
"env": {
"SUPABASE_ACCESS_TOKEN": "${input:supabase-access-token}",
"SUPABASE_MCP_PROJECT_REF": "${input:supabase-project-ref}"
}
}
}
Output: two markdown buttons for Stable and Insiders.
Local dev
- Install deps
- Build
- Run via stdio (for manual testing)
Quickstart
npm i
npm run build
node dist/index.js
You can also run in dev:
npm run dev
This server speaks MCP stdio; integrate with an MCP client to call tools.
Alternatives
Related Skills
Browse all skillsGenerate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
AI-powered comprehensive codebase documentation generator. Analyzes project structure, identifies architecture patterns, creates C4 model diagrams, and generates professional technical documentation. Use when users need to document codebases, understand software architecture, create technical specs, or generate developer guides. Supports all programming languages. Alternative to Litho/deepwiki-rs that uses Claude Code subscription without external API costs.
Meta-skill that analyzes the Trail of Bits Testing Handbook (appsec.guide) and generates Claude Code skills for security testing tools and techniques. Use when creating new skills based on handbook content.
Generate code using nx generators. USE WHEN scaffolding code or transforming existing code - for example creating libraries or applications, or anything else that is boilerplate code or automates repetitive tasks. ALWAYS use this first when generating code with Nx instead of calling MCP tools or running nx generate immediately.
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.