Generates VS Code install buttons for MCP servers that can reference GitHub repositories for Copilot extensions
Generates VS Code install buttons for NPX-based MCP servers that can be installed via npm packages
Uses Shields.io badge styling to create VS Code install buttons with consistent visual formatting
Provides example integration for generating install buttons for Supabase MCP server configurations
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@VS Code MCP Button Generator create install buttons for my supabase server with access token input"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: Daniel Rosehill's MCP Installer
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> }
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.
Install deps
Build
Run via stdio (for manual testing)
npm i
npm run build
node dist/index.jsYou can also run in dev:
npm run devThis server speaks MCP stdio; integrate with an MCP client to call tools.
Generate VS Code install buttons for a GitHub file using owner/repo/path and optional branch.
Inputs: kind (required), owner (required), repo (required), path (required), +1 more.
Generate VS Code install buttons for a raw URL to chat instructions, prompts, or chat modes.
Inputs: kind (required), url (required).
Generate install buttons from a raw MCP JSON-like config object and a server name.
Inputs: name (required), mcp.
Generate VS Code Stable and Insiders MCP install button markdown for an NPX-based server.
Inputs: name (required), inputs, config.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
The tools are mostly distinct, each targeting a different source for generating VS Code install buttons: GitHub files, raw URLs, MCP config objects, and NPX-based servers. However, 'copilot_buttons_from_github' and 'copilot_buttons_from_raw' share a similar prefix and purpose (generating buttons from external sources), which could cause minor confusion in selection, but their descriptions clarify the specific input types.
The naming is inconsistent with mixed conventions: 'copilot_buttons_from_github' and 'copilot_buttons_from_raw' use snake_case with a 'from' preposition, while 'from_mcp_config' starts with 'from' and uses snake_case, and 'make_install_buttons' uses snake_case but with a 'make' verb. This lack of a predictable pattern (e.g., all starting with 'generate' or using consistent verb styles) reduces clarity and coherence.
With 4 tools, the count is well-scoped and appropriate for the server's purpose of generating VS Code install buttons from various sources. Each tool earns its place by covering distinct input methods, avoiding bloat while providing comprehensive coverage for the domain.
The tool set is complete for the inferred domain of generating VS Code MCP install buttons, covering all likely input sources: GitHub repositories, raw URLs, MCP config objects, and NPX-based servers. There are no obvious gaps, as this provides full lifecycle coverage for creating buttons from different data origins.
Create, deploy, and operate MCP servers directly from your GitHub repositories.
MCP registry & directory: search, find & install 31k+ MCP servers & tools. Catalog and marketplace.
Market data tools for the MCP ecosystem: server stats, events, search, leaderboards, package trends.
The official Svelte MCP server providing docs and autofixing tools for Svelte development
