A
licenseNot graded
qualityD
maintenanceEnables AI agents to read and write a local-first knowledge base of plain markdown files in git, with governance gates for safe, hash-anchored edits.
1
Apache 2.0
ArchRepoMCP
by SkySai1
Related Servers
Alternatives to ArchRepoMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to read, modify, and build from architecture models, keeping the model as the source of truth for intent and synchronized with code.25 npm115BSD 3-Clause
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to manage GitHub repositories and automate workflows through natural language.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to work with administrator-approved Git repositories on a self-hosted VPS, supporting cloning, file edits, and full Git operations within persistent workspaces.European Union Public 1.2
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to store and retrieve design decisions as Markdown in git repositories, and check new proposals against historical decisions via MCP.MIT
- FlicenseBqualityBmaintenanceBridges local development environments with the Engineering Intelligence Platform (EIP), enabling AI coding agents to manage SSOT, generate implementation/test/security plans, and synchronize architectural knowledge.5-
TDQS
B3/5.0
Scored across 26 tools
Disambiguation4/5
Most tools target clearly distinct resources and actions, and entity CRUD is well separated from Git repository operations. However, repository_create, repository_open, repository_validate, and government_repository_initialize have overlapping lifecycle responsibilities that could cause an agent to mis-select.
Naming Consistency3/5
Tool names are uniformly snake_case and mostly follow a <domain>_<operation> pattern, but operations are inconsistently verbs or nouns (repository_branches vs branch_create), and branch/remote tools break the repository_ prefix. The style is readable but not a single predictable convention.
Tool Count2/5
With 26 tools, the surface is above the clearly heavy threshold and includes several closely related lifecycle operations that could be consolidated, such as validate/open, commit/publish, and status/list. The broad Git-plus-entity scope explains some size, but the count still feels excessive for an MCP server.
Completeness4/5
The tool set covers repository creation/open/validation, local Git workflows, remotes, and full entity CRUD plus search, so core workflows have no obvious dead ends. Missing branch deletion/merge, remote removal, and tag operations are minor gaps agents can generally work around.
Maintenance
ActivityMaintained
ResponsivenessNo issues