Skip to main content
Glama
marcmendez

Aplomo MCP Server

by marcmendez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Aplomo MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-codebase-intelligence

      g-tiwari
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a semantic understanding of your codebase by parsing with tree-sitter and building a graph of symbols and dependencies. Enables AI assistants to navigate code, analyze changes, and discover architecture using 18 tools with minimal context overhead.
      9 npm
      1
      MIT

    • codebase-rag

      Ar-maan05
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to efficiently understand and navigate a codebase by providing semantic search over symbols and a reference graph, replacing expensive grep/glob calls with structured tools like definition lookup, caller/callee queries, and change-impact analysis.
      3
      MIT

    • lens

      tools-for-agents
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides token-efficient code retrieval for coding agents by indexing repositories and enabling ranked snippet search, symbol outlines, and surgical line reads.
      MIT

    • mcp-intelligence-context

      LeoChimal09
      F
      license
      A
      quality
      C
      maintenance
      Provides codebase indexing and retrieval tools that give AI agents token-efficient, query-relevant context packages (symbols, imports, and dependencies) instead of scanning entire repositories.
      6
      -
    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.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct artifact such as repo overview, existing patterns, plan, architecture, or diff hole, but understand_repo and review_architecture both summarize repository structure and could be confused by an agent picking a general overview tool. Descriptions are specific enough to separate them in most cases.

    Naming Consistency5/5

    All tools use the same aplomo_ prefix followed by a clear verb_noun pattern: understand_repo, find_existing_patterns, review_plan, review_architecture, review_diff. The naming convention is uniform and predictable.

    Tool Count5/5

    Five tools is well-scoped for a repository understanding and review assistant. Each tool covers a necessary step without redundancy or bloat.

    Completeness5/5

    The tool surface supports a complete workflow: understand the repo, search for existing patterns, review a plan, review architecture, and review the diff. No critical gap is evident for the server's apparent purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources