Skip to main content
Glama
Sign In
C4 Architect

C4 Architect

by zrack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to C4 Architect

No user-submitted related servers found.

    Related Servers

    • DependencyMCP Server

      mkearl
      A
      license
      A
      quality
      D
      maintenance
      Analyzes codebases to generate dependency graphs and architectural insights across multiple programming languages, helping developers understand code structure and validate against architectural rules.
      6
      49 npm
      20
      MIT

    • knocoph

      jagonzalr
      A
      license
      Not graded
      quality
      D
      maintenance
      Transforms TypeScript and JavaScript codebases into a persistent code knowledge graph in SQLite, enabling structural codebase navigation via deterministic graph queries without reading source files.
      26 npm
      MIT

    • codegraph

      attnstack
      A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to query a static AST-based call graph for TypeScript/JavaScript repositories, including who-calls, impact analysis, entry-to-dependency traces, hotspots, symbol search, and git-blame archaeology, with every result backed by source evidence chains.
      9
      1
      MIT

    • ts-graph-tools

      KimHG1995
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying a TypeScript codebase's graph for call flows, type relationships, and symbol locations without reading file bodies.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation3/5

    Four tools (analyze, get_summary, query, compare) have clearly distinct verbs on the same graph resource, which is fine. However, render_architecture_graph and render_c4_mermaid both produce a compact C4 image plus Mermaid source plus optional Markdown/SVG/PNG/HTML files, making their boundaries nearly indistinguishable and forcing the agent to guess which to call.

    Naming Consistency4/5

    All six tools follow a consistent snake_case verb_noun pattern (analyze_*, get_*, render_*, query_*, compare_*). Minor deviation: two of them use 'architecture' as the noun while render_c4_mermaid uses the 'c4_mermaid' domain phrasing, which also breaks the resource-naming symmetry.

    Tool Count5/5

    Six tools is well-scoped for an architecture-analysis pipeline: analysis, summary, query, compare, and rendering. Every tool maps to a real stage in the workflow, with only the duplicate renderer arguably removable.

    Completeness4/5

    The lifecycle is well covered: parse dependencies, persist a graph, read a summary, explore a bounded neighborhood, diff two graphs, and render. Minor gap: no tool to list, delete, or explicitly re-validate/refresh saved graphs, so agents lack discovery and cleanup operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources