Server facts
likec4 mcp
Project
- Author
- likec4
- License
- Not specified
- Category
- Developer Tools
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- Not recordedPart of the likec4/likec4 monorepo
- Last commit
- Data as of
Tags
- Diagrams
- architecture
- c4
Overview
Architecture exploration in LikeC4 MCP starts with discovering workspace projects and reading their model summaries, including configuration, element kinds, deployments, tags, and available views. Developers using an LLM can then inspect individual elements, deployment entities, or view contents, with source locations returned where available. Search spans projects and supports filters for kinds, shapes, metadata keys, and tags. Separate queries offer metadata value matching, Boolean tag conditions, and tag patterns, allowing exploration to follow the classifications already recorded in a model rather than relying only on element names.
Relationship tools distinguish direct connections from those implied by nested elements, find paths between endpoints, and traverse upstream producers or downstream consumers. Hierarchy queries expose parents, children, siblings, ancestors, and descendants. For broader inspections, batch reads collect element summaries, subgraph summaries organize descendants with depth and relationship counts, and element comparisons identify differences in properties, tags, metadata, and relationships. These inspection tools are read-only; a separate tool applies semantic layout to a LikeC4 view. The server uses stdio transport to expose this model context to LLM clients.
likec4 mcp setup notes
- likec4 mcp records stdio only; confirm a network transport upstream before planning remote access.
- likec4 mcp: Part of the likec4/likec4 monorepo
- likec4 mcp has no recorded license; confirm reuse terms in its repository.