aira-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusC | Gitのステータス情報を取得します |
| create_commitB | 指定したファイルに対してコミットを作成・実行します。※1度に1ファイルのみコミット可能です |
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 2 tools
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.
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.
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.
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.