Skip to main content
Glama
eyalev

vscode-helper

by eyalev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to vscode-helper

No user-submitted related servers found.

    Related Servers

    • VSCode Automation MCP

      Sukarth
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to programmatically control and automate VSCode by interacting with its UI, executing commands, and inspecting the DOM structure. It supports advanced workflows like UI testing, extension development, and debugging through a standalone VSCode instance.
      8 npm
      8
      MIT

    • vscode-playwright-mcp

      mykhlv
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives LLMs full control over VS Code — click UI elements, type code, run commands, take screenshots, read editor state, and record GIFs.
      4 npm
      MIT

    • HumanCode MCP

      Ryanabcraft
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as OpenCode, Claude Code, and Codex to control a real VS Code editor by opening files, visibly typing code, running terminal commands, reading diagnostics, and fixing errors through the VS Code API. It makes AI programming observable by applying real progressive edits and actions that are visible on screen.
      MIT

    • vscode-mcp

      prog76
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes VS Code terminals as MCP tools, allowing AI agents to create, execute commands, read output, list, and kill terminals across multiple workspaces.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but reveal_in_explorer and select_file_in_explorer overlap significantly since both involve highlighting/selecting a file in the explorer. focus_explorer is distinct enough, but the explorer-related trio creates minor ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (open_file, run_terminal_command, create_file, search_workspace). The explorer-related tools use a consistent verb_in_explorer style, making the naming predictable and coherent.

    Tool Count5/5

    Seven tools is well-scoped for a VSCode helper covering file operations, terminal execution, workspace search, and explorer interaction. Each tool earns its place without unnecessary redundancy or bloat.

    Completeness4/5

    The core VSCode helper workflows are covered: opening/creating files, running terminal commands, searching the workspace, and navigating the explorer. Minor gaps exist such as editing existing files or managing open editors, but these can be worked around and the toolset is coherent for its stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources