Skip to main content
Glama
block

Code MCP Server

by block
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Code MCP Server

No user-submitted related servers found.

    Related Servers

    • VSC as MCP

      CodingWithCalvin
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to leverage VS Code's language intelligence for code navigation, refactoring, and analysis via the MCP protocol.
      MIT

    • lsp-mcp

      rexl2018
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with VS Code's language server protocol features (definitions, references, diagnostics) and debugger (breakpoints, stepping, variable inspection) via an MCP server.
      6 npm
      1
      MIT

    • LSP-MCP

      blackwell-systems
      A
      license
      Not graded
      quality
      F
      maintenance
      Bridges the Model Context Protocol with Language Server Protocol to provide AI agents with persistent access to code intelligence features including navigation, diagnostics, refactoring, and completion across 7+ programming languages.
      1,077 npm
      MIT
    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

    C2.7/5.0

    Scored across 73 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes, causing ambiguity. For example, 'git_diff' and 'enhanced_git_diff' both show git differences, 'preview_changes' and 'preview_changes_enhanced' both preview changes, and 'get_current_session' and 'get_session_info' appear to retrieve the same information. Tools like 'run_command', 'secure_run_command', and 'secure_run_command_sequence' also have unclear boundaries, making it difficult for an agent to choose the right one without trial and error.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun or verb_adjective_noun pattern (e.g., 'create_directory', 'analyze_code', 'docker_build'), with clear and descriptive names. However, there are minor deviations, such as 'npm_command' and 'pip_install' using different naming styles, and some redundancy in names like 'git_diff' vs. 'enhanced_git_diff', but overall the naming is readable and predictable.

    Tool Count2/5

    With 73 tools, the count is excessive for a code-focused server, leading to bloat and potential confusion. Many tools could be consolidated (e.g., multiple Docker tools, redundant git and preview tools) without losing functionality. This large number suggests poor scoping and makes the toolset overwhelming for agents to navigate effectively.

    Completeness5/5

    The toolset provides comprehensive coverage for code development, including file operations, git management, Docker containerization, dependency installation, and session tracking. It supports full CRUD/lifecycle operations across these domains, with no obvious gaps. Agents can perform end-to-end workflows from project creation to deployment and cleanup.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources