Skip to main content
Glama
sbrejnev988-coder

mcp-code-shrinker

by sbrejnev988-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-code-shrinker

No user-submitted related servers found.

    Related Servers

    • logicstamp-mcp by LogicStamp

      logicstamp-mcpofficial

      LogicStamp
      A
      license
      A
      quality
      C
      maintenance
      MCP server that provides AI assistants with structured access to codebases via LogicStamp Context, enabling component analysis, dependency graphs, drift detection, and token-optimized context delivery.
      7
      12 npm
      4
      MIT

    • Proof Mode

      vikramlaishram-lang
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server implementing a multi-phase backend for structured model interactions, bounded compilation, exact-hash confirmation, and Codex-run provenance, with trust-separation hardening.
      1
      -

    • karst

      Moin105
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for local codebase analysis, enabling semantic code search, impact analysis, and pack-scoped retrieval with cited file:line results.
      Apache 2.0

    • code-graph-rag-mcp

      er77
      A
      license
      Not graded
      quality
      F
      maintenance
      A powerful Model Context Protocol server that creates intelligent graph representations of your codebase with comprehensive semantic analysis capabilities, supporting 11 languages and 26 MCP methods.
      13 npm
      122
      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.8/5.0

    Scored across 29 tools

    Disambiguation5/5

    Each tool targets a distinct domain and action (project, file, symbol, artifact, context, patch, patchset). Descriptions clearly differentiate purposes, e.g., project.scan builds call graphs while symbol.context provides callers/callees. No notable overlap.

    Naming Consistency5/5

    All names follow a consistent two-part dot-separated pattern (domain.action), using snake_case for multi-word actions. No mixing of conventions across tools.

    Tool Count4/5

    At 29 tools, the count is on the higher side but still justified given the server's broad scope (project scanning, symbol analysis, artifact storage, context construction, and patching). Each tool serves a specific function without redundancy.

    Completeness5/5

    The tool surface covers a full workflow from project scan and symbol extraction to context packets, artifact management, and atomic patches with rollback. No obvious gaps for the stated purpose of code shrinking/analysis.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources