VS Code MCP Button Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| make_install_buttonsC | Generate VS Code Stable and Insiders MCP install button markdown for an NPX-based server. |
| from_mcp_configC | Generate install buttons from a raw MCP JSON-like config object and a server name. |
| copilot_buttons_from_rawC | Generate VS Code install buttons for a raw URL to chat instructions, prompts, or chat modes. |
| copilot_buttons_from_githubC | Generate VS Code install buttons for a GitHub file using owner/repo/path and optional branch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.