Skip to main content
Glama

Related Servers

Alternatives to EIP MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      Connects AI assistants to a local Codex engine for performing deep, project-level code reviews and automated refactoring. It enables context-aware bug fixes and multi-file analysis through a standardized bridge between modern AI clients and local development environments.
      4
      2
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first cross-service code intelligence engine for AI agents, connecting frontend, gateways, backend services, and databases to enable impact analysis and change planning.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables local, permissioned development workflows from compatible AI clients, including filesystem editing, interactive terminals, durable jobs, Git operations, and semantic browser testing.
      306 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables local code intelligence for AI agents and editors by indexing source code, dependencies, Git history, tests, and documentation, and provides change-impact analysis and relevant test selection through MCP.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read, modify, and build from architecture models, keeping the model as the source of truth for intent and synchronized with code.
      25 npm
      115
      BSD 3-Clause

    TDQS

    B3.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tools mostly target distinct artifacts: task plan, implementation plan, test plan, and SSOT synchronization. generate_task_plan and generate_implementation_plan could potentially be confused since both produce planning documents, but their descriptions clarify the output differences.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: generate_*, initialize_*, synchronize_*. This makes the set predictable and easy to navigate.

    Tool Count5/5

    Five tools is well-scoped for a planning-and-sync workflow. Each tool has a clear role and there is no obvious redundancy.

    Completeness4/5

    The core lifecycle is covered: initialize SSOT, generate task/implementation/test plans, and synchronize changes. Minor gaps exist, such as no explicit update/retrieve tool for existing plans, but agents can likely work around this through the local workspace.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues