Skip to main content
Glama
aferreiraguido

javascript-mcp-server

by aferreiraguido
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to javascript-mcp-server

No user-submitted related servers found.

    Related Servers

    • symbolpeek-mcp

      pioner92
      A
      license
      Not graded
      quality
      A
      maintenance
      Semantic code intelligence MCP server for TypeScript/JavaScript codebases, enabling AI agents to retrieve specific symbols, types, and relationships without reading entire files.
      20
      MIT

    • lsp-intelligence

      perilevy
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing 29 tools across 5 layers for semantic TypeScript/JavaScript code intelligence, enabling AI agents to find references, trace impacts, guard APIs, and explain errors without text-search false positives.
      16 npm
      1
      MIT

    • ast-impact-mapper-mcp

      vola-trebla
      A
      license
      A
      quality
      D
      maintenance
      MCP server that analyzes TypeScript/JavaScript codebases via AST parsing and dependency graph tracing to identify affected tests, detect dead code, circular dependencies, and trace import chains, enabling AI agents to run only relevant tests.
      15
      37 npm
      MIT

    • agent-workspace-mcp

      c0sc0s
      A
      license
      A
      quality
      D
      maintenance
      A TypeScript-aware MCP server that provides coding agents with repository discovery, code intelligence, and web project context for local codebases. It enables deep symbol navigation, diagnostic reporting, and structural analysis of monorepos without requiring full IDE integration.
      7
      4 npm
      1
      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 103 tools

    Disambiguation2/5

    Many tools have overlapping boundaries: find_any_usages and find_unsafe_type_casts both flag `as any`, find_event_emitter_leaks and find_event_listener_leaks sound nearly identical, and find_unused_varibles vs. find_dead_code cover adjacent territory. With 103 tools, an agent is likely to mis-select among the numerous find_* detectors despite their individual descriptions.

    Naming Consistency4/5

    The dominant verb_noun pattern (list_*, find_*, analyze_*, inspect_*) is clear and predictable. A notable minority of noun-first tool names (program_summary, nuxt_config, module_dependency_graph, node_process_env) and framework-specific naming variants prevent a perfect score, but the overall convention is still readable and mostly consistent.

    Tool Count1/5

    At 103 tools, this server is extremely over-scoped, far beyond the 50+ extreme-mismatch threshold. Even for a broad JS/TS analysis domain, a single MCP server of this size creates impractical selection overhead and should be split into multiple focused servers.

    Completeness4/5

    The server covers an unusually wide range of read-only static analysis needs: project lifecycle, symbols, types, call graphs, type-checking, framework-specific analysis, API detection, security heuristics, and technical-debt finders. Minor gaps exist (e.g., no general package.json/tsconfig reader, no direct import-list tool), but nothing critical blocks understanding a loaded project.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources