Skip to main content
Glama

Related Servers

Alternatives to @exeris/ai-bridge

No user-submitted related servers found.

    Related Servers

    • F
      license
      D
      quality
      B
      maintenance
      Provides read-only, structured access to Yasin ecosystem information (project registry, documentation, GitHub state, diagnostics) through the MCP protocol, enabling AI agents to query without direct repository access.
      22
      3
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and engineers to query evidence-qualified cross-boundary architecture relationships, binding pictures, drift, and supporting evidence from declared and observed architecture data through read-only MCP tools.
      10
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server that exposes the agentic-os governance, SDLC, and Quality Engineering methodology to any MCP host. It never writes to your repository and never executes code — it serves the methodology, plans an install, and verifies it, handing any commands back to the host to run.
      7
      2
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable coding agents to access SkeletIQ architecture releases, including reading designs and build orders, generating and critiquing architectures, and reporting build progress and drift.
      6
      385 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to observe local codebases in real time through a secure, read-only MCP interface, providing workspace snapshots, git history and diffs, cross-project search, and project reality coverage without write access.
      MIT

    TDQS

    A3.7/5.0

    Scored across 34 tools

    Disambiguation4/5

    The seven family prefixes (docs-, lsp-, build-, kernel-, caps-, sdk-, bridge-) draw clean lines between domains, and most tools within a family target a distinct artefact. However, `lsp-list_domains` vs `build-list_domains` and `lsp-describe_domain` vs `build-get_domain_metadata` genuinely overlap — both surface fields, actions and relationships for an @ExerisDomain — and only long descriptions (live LSP session vs emitted target/classes metadata) separate them. `lsp-preview_mutation` and `build-preview_generation` are also adjacent preview concepts, though clearly differentiated.

    Naming Consistency5/5

    Every tool follows a strict `family-verb_noun` pattern in snake_case (docs-get_adr, build-explain_artefacts, sdk-list_annotations, lsp-preview_mutation). The rare exceptions (docs-search, bridge-version, bridge-health) are still readable and consistent with the hyphen-prefix convention, so tool selection by name alone is predictable.

    Tool Count3/5

    34 tools is heavy and sits above the comfortable band, but the surface is unusually broad (docs, live LSP, build/codegen, kernel runtime, capabilities, SDK contract, meta) and each family carries a small, coherent 2-9 tool set that mostly earns its place. It is still at the upper edge where an agent must first pick a family before picking a tool.

    Completeness4/5

    Coverage across inspection domains is strong: docs reading, ADR registry, domain/action introspection, mutation preview, build metadata, artefact and diagnostic explanation, kernel state, capability composition, SDK contract and health checks. The notable gap is that the docs root has `docs-search` and a few named fetchers but no generic `docs-list_docs`/`docs-get_doc` by path, and mutations are preview-only with no post-apply verification tool.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues