Skip to main content
Glama
JALAL591

compose-bridge

Related Servers

Alternatives to compose-bridge

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides AI coding agents real Android development tools—Gradle, adb, logcat, lint, crash triage—through a local, permissioned interface. Enables agents to inspect projects, run safe Gradle tasks, capture logs/screenshots, and triage crashes.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Local MCP server providing project cognition capabilities for AI coding agents, including context packs, impact analysis, and git diff review through stdio communication.
      10
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that builds a dependency graph of your codebase, giving AI agents structural understanding to analyze impact, find context, and make safe modifications across languages and infrastructure.
      MIT

    TDQS

    A3.9/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, helped by explicit 'When NOT to use' clauses (e.g. set_token vs set_text vs add_token, approve vs reject variants). Minor overlap exists between list_orphans and list_tokens (orphans are a subset of the latter) and among the rollback variants, but boundaries are generally clear.

    Naming Consistency5/5

    All 27 tools use snake_case with a consistent verb_noun structure (get_*, list_*, set_*, reject_*, approve_*, rollback_*). Patterns like *_all_files vs *_file_changes vs *_pattern clearly signal scope, giving a highly predictable naming scheme.

    Tool Count3/5

    27 tools is heavy and pushes past the comfortable 3-15 band; the approval cluster (approve_file_changes, approve_all_files, reject_file_changes, reject_all_files, reject_all_files_force) is especially granular. The breadth is partly justified by distinct token-editing, pattern, build, and sync subdomains, but consolidation is possible.

    Completeness4/5

    Strong lifecycle coverage: create/edit tokens and text, analyze impact/orphans/siblings/groups, detect and replace patterns with rollback, approve/reject changes, build, and sync. The main gap is the absence of a delete/remove_token tool despite list_orphans identifying removable tokens, and no explicit way to create token groups.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues