Skip to main content
Glama
apolosan

Design Patterns MCP Server

by apolosan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Design Patterns MCP Server

No user-submitted related servers found.

    Related Servers

    • Smart Code Search MCP Server

      stevenjjobson
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic code search across projects using AI embeddings to find code by meaning rather than just text matching. Provides fast intelligent search, symbol analysis, and code similarity detection with multi-language support.
      MIT

    • Pattern Intelligence MCP

      mateusdcc
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to make evidence-aware design-pattern decisions by analyzing cases, comparing options, detecting misuse, stress-testing assumptions, planning adoption, writing ADRs, and generating evidence plans with transparent scoring.
      2
      8
      2 npm
      2
      MIT

    • Acemcp

      yeuxuan
      A
      license
      A
      quality
      D
      maintenance
      Provides code repository indexing and semantic search capabilities, allowing natural language queries to find relevant code snippets with automatic incremental indexing and multi-language support.
      1
      4 npm
      359
      ISC
    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

    B3/5.0

    Scored across 4 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes that could cause confusion. 'find_patterns' and 'search_patterns' both appear to search for patterns, with descriptions that are nearly identical ('semantic search' vs 'keyword or semantic similarity'), making them difficult to distinguish. 'count_patterns' and 'get_pattern_details' are clearer, but the overlap between the two search tools significantly reduces disambiguation.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as 'count_patterns', 'find_patterns', 'get_pattern_details', and 'search_patterns'. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.

    Tool Count3/5

    With only 4 tools, the set feels thin for a server focused on design patterns, which typically involve operations like creating, updating, or categorizing patterns. While basic retrieval functions are covered, the low count may limit functionality for more complex agent tasks, placing it in the borderline range for appropriateness.

    Completeness2/5

    The tool set is severely incomplete for a design patterns domain, as it only supports read operations (counting, searching, and getting details) with no ability to create, update, delete, or manage patterns. This lack of CRUD coverage creates significant gaps that will likely cause agent failures when trying to perform full lifecycle tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources