Skip to main content
Glama
Sign In
mcp-agent-to-vsc

mcp-agent-to-vsc

by relr-prog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-agent-to-vsc

No user-submitted related servers found.

    Related Servers

    • Code MCP Server

      agentics-ai
      A
      license
      C
      quality
      D
      maintenance
      An experimental MCP server that enables AI assistants to interact with VS Code workspaces through file operations, code execution, and Git management. It also provides tools for Docker integration, project scaffolding, and secure command execution using project-specific configurations.
      76
      23 npm
      3
      MIT

    • mcp-coding

      cdemeo92
      A
      license
      Not graded
      quality
      D
      maintenance
      Experimental MCP server for local LLM orchestration with filesystem tools (read, write, list, delete files) and a CLI agent that communicates via Ollama.
      2 npm
      ISC

    • codex-mcp

      meesii
      A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight local coding MCP server that exposes a single project directory to ChatGPT via Streamable HTTP, enabling file operations, command execution, search, and web fetching without authentication.
      29 npm
      25
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct function: AI query, file read, file write, file listing, and workspace configuration. There is no functional overlap, so an agent can reliably select the correct tool.

    Naming Consistency4/5

    Most names follow a verb_noun pattern (ask_ai, read_file, write_file, list_files), but workspace_info breaks the pattern as a noun phrase. Overall the naming is clear and predictable.

    Tool Count5/5

    Five tools is a well-scoped set for an agent-to-VS Code integration covering the essential file operations, AI interaction, and workspace context. Each tool earns its place without redundancy.

    Completeness4/5

    The set covers core file read/write/list and AI query, which covers common agent workflows. Minor gaps include delete or rename file operations, but these are not critical for the apparent purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources