Skip to main content
Glama
Sign In
ArchRepoMCP

ArchRepoMCP

by SkySai1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ArchRepoMCP

No user-submitted related servers found.

    Related Servers

    • kula MCP

      A12N4V
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with a local-first git client that provides a knowledge graph of the repository, including graph analysis, issue and proposal management, and architectural review.
      2
      MIT

    • io.github.Yantrakar/gitpro

      Yantrakar
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to run structured preflight checks and identity-scoped Git operations, committing, pushing and opening GitHub PRs with the correct Git name, email, SSH key and signature for each repository. Persistent changes require exact proposals, human approval by default and recoverable, idempotent apply.
      92 PyPI
      MIT

    • scryer-mcp

      aklos
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to read, modify, and build from architecture models, keeping the model as the source of truth for intent and synchronized with code.
      61 npm
      122
      BSD 3-Clause

    • DIP

      vxu-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to maintain local-first project memory, coordinate task ownership across Git worktrees, and verify completion against project-defined checks with durable evidence stored in the repository.
      1
      Apache 2.0
    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/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.

    Resources