ArchRepoMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCH_REPO_MCP_ENV_FILE | No | Path to an additional env file from which configuration values are read. | |
| ARCH_REPO_MCP_WORKSPACE | No | Local directory where the government and all working repositories are stored. Can also be passed via the stdio argument 'workspace_path'. | |
| ARCH_REPO_MCP_GOVERNMENT_REPOSITORY | No | Name or path to the government repository inside the workspace. Defaults to 'government'. | government |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| government_repository_initializeC | Open or create the government repository from the built-in DSL and templates. |
| repository_describeC | Return the authoritative DSL model, templates, and entity-management workflow. |
| repository_listA | List working repositories so an agent can explicitly select a repository_path. |
| repository_createC | Create a validated local Git repository without creating a commit. |
| repository_openB | Open and fully validate a local architecture Git repository without network access. |
| repository_validateC | Validate the DSL, templates, paths, matching rules, and local entity files. |
| repository_statusA | Return local Git status without fetch, pull, or other network operations. |
| repository_diffA | Return working-tree, staged, or revision-to-revision local Git diff. |
| repository_branchesA | List local branches without contacting a remote. |
| branch_createA | Create a local branch without switching the repository to it. |
| branch_switchA | Switch to a valid local branch only when the worktree and index are clean. |
| repository_commitA | Validate and commit only changed DSL-controlled paths without push. |
| repository_historyA | Return bounded local commit history without contacting a remote. |
| repository_remotesA | List local Git remotes while redacting credential-bearing URL components. |
| remote_configureB | Add or explicitly replace local remote configuration without network access. |
| repository_cloneC | Explicitly clone and validate a remote Git architecture repository. |
| repository_fetchA | Explicitly fetch a configured remote without changing the working tree. |
| repository_pullA | Fetch and integrate only a validated fast-forward into a clean local branch. |
| repository_publishA | Validate and explicitly push current HEAD without force or implicit upstream. |
| entity_listB | List instances of a DSL-declared entity type from the local repository. |
| entity_createA | Create a local entity from its DSL template without commit or publication. |
| entity_readC | Read one local entity selected by type and repository-relative path. |
| entity_read_relatedC | Read files referenced by an entity's DSL-governed front matter relations. |
| entity_updateB | Replace a local entity and roll back when validation fails. |
| entity_deleteC | Delete one local entity without commit or publication. |
| entity_searchB | Search text in all or one type of local DSL-resolved entity. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
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.
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.
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.
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.