VS Code MCP Button Generator
Related Servers
Alternatives to VS Code MCP Button Generator
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA CLI tool to scaffold and manage new MCP-compatible server projects with uv, including virtual environment setup, dependency management, and VS Code integration.-
- AlicenseNot gradedqualityBmaintenanceEnables developers to build, test, debug, and operate MCP servers from VS Code or CI, while also exposing trusted MCP capabilities to AI agents.MIT
- FlicenseNot gradedqualityCmaintenanceConverts VSCode into an MCP server that enables external clients to remotely execute VSCode internal commands, query workspace information, and interact with the editor through HTTP streaming. Built on the FastMCP framework with security controls and real-time monitoring.63-
- AlicenseAqualityDmaintenanceManages installation and configuration of MCP servers across multiple clients (Claude Code, Cursor, VS Code) from a personal GitHub registry, with support for API key management and bulk installations.72 npmMIT
- FlicenseAqualityDmaintenanceA portable MCP server enabling AI assistants to operate VS Code, including file management, extension control, and workspace automation.6-
- AlicenseNot gradedqualityCmaintenanceGenerates production-ready MCP server projects from a single command, providing project structure, tool examples, and optional advanced templates.MIT
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.