Skip to main content
Glama
lexCoder2

lxDIG MCP

by lexCoder2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to lxDIG MCP

No user-submitted related servers found.

    Related Servers

    • TIMPS

      TIMPSs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives AI coding agents persistent memory across sessions, storing architecture decisions, past bugs, and codebase conventions locally.
      3 npm
      MIT

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      202 npm
      5
      MIT

    • myBrAIn

      lilium360
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides persistent memory and contextual awareness to language models, enabling project onboarding, recall of architectural rules, and code consistency across sessions.
      32
      MIT

    • Mono Memory MCP

      potato-castle
      A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that provides AI assistants with a shared, persistent SQLite-backed memory for storing and retrieving project context, decisions, and discoveries. It enables cross-session continuity and team-wide knowledge sharing to keep AI coding tools aligned and informed.
      3
      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

    B3.2/5.0

    Scored across 39 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with detailed descriptions aiding differentiation. There is some overlap among code analysis tools (e.g., find_pattern, semantic_search, code_clusters), but each targets a specific use case, making confusion unlikely for an agent.

    Naming Consistency4/5

    The majority of tools follow a consistent verb_noun snake_case pattern (e.g., agent_claim, arch_suggest). A few tools like 'reflect' and 'semantic_slice' deviate slightly, but overall naming is predictable and readable.

    Tool Count3/5

    With 39 tools, the server is extensive. While each tool seems justified by the breadth of functionality, the count is high and some tools could potentially be consolidated (e.g., multiple search tools). This may overwhelm an agent.

    Completeness5/5

    The tool surface covers a comprehensive range of operations for an agentic coding assistant: project setup, code graph management, agent coordination, testing, documentation, architecture validation, and more. There are no obvious dead ends or missing critical operations for the stated domain.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources