Skip to main content
Glama
Sunwood-ai-labs

aira-mcp-server

by Sunwood-ai-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aira-mcp-server

No user-submitted related servers found.

    Related Servers

    • Commit Helper MCP

      jolfr
      A
      license
      B
      quality
      Not graded
      maintenance
      A Model Context Protocol server that provides Commitizen functionality, enabling AI assistants to generate, validate, and work with conventional commit messages.
      21
      MIT

    • Git Prompts MCP Server

      ceshine
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that generates prompts based on Git repository content, including a command to generate PR descriptions from diffs.
      3
      2
      MIT
    • git MCP server by modelcontextprotocol

      git MCP serverofficial

      modelcontextprotocol
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models.
      12
      39,753 PyPI
      90,629
      MIT

    • diffsorted

      bhakti0725
      A
      license
      Not graded
      quality
      B
      maintenance
      Splits messy, multi-concern git diffs into focused groups and generates a clear, accurate commit message for each, exposed as an MCP server for use with MCP-compatible clients.
      3 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: create_commit performs a write operation to commit a file, while get_status performs a read operation to retrieve Git status information. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (create_commit, get_status) with clear, descriptive names that indicate their actions and targets. The naming is uniform and predictable.

    Tool Count2/5

    With only 2 tools, the server feels severely under-scoped for Git operations. While the tools cover basic commit creation and status checking, essential operations like cloning, branching, merging, or viewing history are missing, making it inadequate for typical Git workflows.

    Completeness2/5

    The toolset is highly incomplete for a Git server. It lacks fundamental operations such as clone, push, pull, branch, merge, log, or diff, which are critical for agent-driven Git management. Agents will encounter dead ends when trying to perform common Git tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources