All servers / Developer / LikeC4 MCP server
LikeC4 MCP server
Model Context Protocol server for LikeC4
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-19 on package version 1.61.0. Package: @likec4/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (7.9 seconds including download)
- Tools offered: 22
- Last published: 2026-11-14
- Weekly downloads (npm): 1,179
- License: MIT · Direct dependencies: 19
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list-projectsno parametersList the LikeC4 projects in the workspace. Pass a project's id as the "project" argument of other tools.
read-project-summary1 of 1 parameter describedOverview of a LikeC4 project: its configuration, its specification (element, relationship and deployment kinds, tags, metadata keys), and every element, deployment entity and view with id, kind, title and tags. Use it to orient in a project before reading individual elements or views.
read-element2 of 2 parameters describedRead one element in full: properties, metadata, links, children, the views that include it, its direct and indirect incoming and outgoing relationships, deployed instances and source location. For many elements, use batch-read-elements.
read-deployment2 of 2 parameters describedRead one deployment node or deployed instance: kind, tags, metadata, links, children (empty for an instance), the views that include it, the element a deployed instance instantiates, and source location.
read-view2 of 2 parameters describedRead a view's structure: its nodes (elements, deployment nodes or deployed instances) and the edges between them, with source location. A view without a title returns its id as the title. Use render-view to show the diagram to the user.
search-element1 of 1 parameter describedSearch elements and deployment nodes across all projects by id, title, description, link, kind, shape, tag or metadata key. Returns the total number of matches and the first 20, ranked by relevance for plain-text searches. Pass the ids found to read-element or other tools.
find-relationships3 of 3 parameters describedFind the relationships between two elements: direct ones between them, and indirect ones through their nested elements. Each comes with kind, title, technology, tags, the views it appears in and source location. Result order is not guaranteed. For multi-hop chains, use find-relationship-paths.
find-relationship-paths5 of 5 parameters describedFind chains of relationships from a source element to a target element, shortest first, up to maxDepth hops and at most 100 paths. Follows direct relationships only, unless includeIndirect adds implied relationships through nested elements. Source and target must differ; no connection returns an empty list.
query-graph4 of 4 parameters describedOne-step graph query around an element. Hierarchy: ancestors (up to the root), descendants (recursive), siblings, children, parent (empty for a root element); includeIndirect is ignored for these. Relationships: incomers and outgoers, single hop; includeIndirect (default true) adds relationships of nested children. For recursive traversal, use query-incomers-graph or query-outgoers-graph. At most 100 results.
query-incomers-graph5 of 5 parameters describedRecursive upstream traversal: every element that feeds into the target, directly or transitively, returned as one graph with each node's depth and incomers. Answers "what feeds into this?" in one call instead of repeated query-graph calls. Stops at maxDepth or maxNodes; if truncated is true, raise maxNodes or lower maxDepth.
query-outgoers-graph5 of 5 parameters describedRecursive downstream traversal: every element that consumes output from the target, directly or transitively, returned as one graph with each node's depth and outgoers. Answers "what depends on this?" (blast radius) in one call instead of repeated query-graph calls. Stops at maxDepth or maxNodes; if truncated is true, raise maxNodes or lower maxDepth.
query-by-metadata4 of 4 parameters describedFind elements and deployment nodes by metadata. matchMode "exact" (default) compares the value case-sensitively, "contains" matches a substring case-insensitively, and "exists" matches any element with the key and ignores value. An array value matches if any item matches. At most 50 results.
query-by-tags4 of 4 parameters describedFind elements and deployment nodes by tags with boolean logic: allOf (AND), anyOf (OR) and noneOf (NOT), combined with AND. At least one condition is required, and tags are case-sensitive. At most 50 results. For partial tag names, use query-by-tag-pattern.
query-by-tag-pattern3 of 3 parameters describedFind elements whose tags match a pattern, for structured tag naming such as "team_*". matchMode is "prefix" (default), "contains" or "suffix", case-insensitive. Returns the matching tags per element and every distinct matching tag. At most 50 results. For exact tags with boolean logic, use query-by-tags.
batch-read-elements2 of 2 parameters describedRead summaries of up to 50 elements in one call: properties, metadata, children, relationship counts, the views that include them, links and source location. Ids not found are listed in notFound instead of failing the call. Use read-element only when you also need relationships, deployedInstances, defaultView or project.
element-diff3 of 3 parameters describedCompare two elements of the same project: properties that differ, tags and metadata on each side or shared, and incoming and outgoing relationship counts on each side or shared. Useful for seeing why two similar elements differ.
subgraph-summary4 of 4 parameters describedSummarize all descendants of an element in one call, breadth-first, each with depth (1 = direct child), tags, metadata, and child and relationship counts. At most 200 descendants; truncated and truncatedByDepth say what was cut. Pass metadataKeys to return only those keys. Cheaper than read-element per descendant.
removal-impact2 of 2 parameters describedReport what removing an element from the model takes with it (safe delete dry run, blast radius). Request: - id: string — element id (FQN) - project: string (optional) — project id. Defaults to "default" if omitted. Response (JSON object): - elements: string[] — removed elements: the element and its descendants (FQNs) - relationships: number — relationships with a removed element as source or target - deployedInstances: string[] — deployed instances of removed elements - emptyDeploymentNodes: string[] — deployment nodes left without deployed instances - affectedViews: string[] — views that show a removed element or relationship - scopedViews: string[] — views scoped to a removed element - orphans: string[] — elements left without relationships (suggested for removal, not removed automatically) - references: Array<{ kind, resolution, text, path, line }> — source references to removed elements - kind: where the reference is (relation, extend-element, deployed-instance, view-predicate, view-scope, dynamic-step, diff, ...) - resolution: "removed" (removed together with the element), "optional" (removed only on request), "manual" (fix manually) - text: source text of the node with the reference - path, line: location (line is 1-based) Notes: - Read-only, idempotent, no side effects. Nothing is removed. - Use before refactoring to understand the impact of removing an element.
list-diffs1 of 1 parameter describedList model diffs (named change sets, "diff" blocks) and the views each diff changes. Request: - project: string (optional) — project id. Defaults to "default" if omitted. Response (JSON object): - diffs: Array of - id: string — diff name - title: string|null - description: string|null - added: { elements: number, relations: number } - removed: { elements: number, relations: number } - modified: { elements: number } - views: Array<{ id, title, nodes: { added, removed, modified }, edges: { added, removed, modified } }> — views changed by the diff Notes: - Read-only, idempotent, no side effects. - A diff describes a future state of the model; the model itself stays unchanged until the diff is applied.
apply-semantic-layout2 of 2 parameters describedApply semantic layout to the likec4 view
render-view3 of 4 parameters describedRenders a LikeC4 view as an interactive diagram (pan/zoom/fit) inline in the chat. Use it when the user wants to *see* a view; use "read-view" when only the view's structure (nodes/edges) is needed.
preview-view3 of 3 parameters describedRenders a draft view from DSL against an existing project's real elements, without saving anything. The DSL must be a single element view, `view <id> ... { ... }`, with a new id: an existing id is rejected (use "render-view" for saved views), and a dynamic or deployment view fails with a generic "could not find a `view <id>`" error. Custom theme and style extensions are not applied. Use it to iterate on a view before creating it for real.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.