vscode-mcp-manager
Related Servers
Alternatives to vscode-mcp-manager
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA lightweight bridge extension that enables Claude Desktop to connect to VSCode workspaces via Model Context Protocol, allowing Claude to read and write files, create directories, and list contents in your workspace.9MIT
- AlicenseNot gradedqualityCmaintenanceUniversal context, rules & handoff bridge for AI coding tools (Cursor, Claude Code, GitHub Copilot, Cline, Antigravity, Windsurf).3MIT
- AlicenseCqualityFmaintenanceEnables AI agents and assistants like Goose or Claude to interact with VS Code through the Model Context Protocol.768 npm75Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides a unified MCP interface to interact with Codex CLI, Claude Code, and Grok API, allowing seamless switching between AI models in VS Code or Claude Code.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables collaboration with multiple AI providers (Claude, GPT-4, Gemini, Ollama) directly from VS Code with automatic project context injection and persistent conversation history. Provides streamlined tools for getting AI advice, multi-provider research, and enhanced context sharing across sessions.8 npm-
- FlicenseNot gradedqualityDmaintenanceTurns Claude Desktop into a Cursor-like assistant for code browsing, editing, searching, linting, formatting, and version control.-
TDQS
Scored across 4 tools
Each tool targets a distinct artifact or action: generating MCP client configs, auditing extension manifests, syncing workspace settings, and inspecting live gateways. Even the two config-producing tools are clearly separated by output type and intended usage.
All tool names follow the same vscode_<verb>_<object> pattern, using specific verbs and clear nouns. There are no mixed conventions or vague actions.
Four tools form a compact, purposeful set well within the ideal range. Each tool covers a separate facet of the VS Code/MCP configuration workflow without redundancy.
The set covers configuration generation, workspace standardization, extension validation, and gateway health verification, which supports a solid setup workflow. Minor gaps exist—such as no explicit existing-config validation or server removal—but these do not create dead ends for the apparent purpose.