aira

aira is a TypeScript-based MCP server that implements a simple notes system and demonstrates core MCP concepts. It provides tools to interact with a Git repository by reporting status, generating conventional commit messages, initializing and managing Gitflow, and performing common branch operations. To use it, configure the MCP server in your settings to point to the built server entry point as shown in the usage example. The server exposes a set of tools including get_status for repository status, create_commit to commit staged changes with a conventional message, init_gitflow to initialize Gitflow, create_branch to create new branches, merge_branch to merge branches according to Gitflow, and list_branches to view current Gitflow branches. These tools enable streamlined Git workflows integrated with MCP capabilities.

To activate it, add an entry under mcpServers with the server name aira and specify the node command and the path to the built entry file, for example: { "mcpServers": { "aira": { "command": "node", "args": ["path/to/aira-mcp-server/build/index.js"] } } }.

Prerequisites:

• Node.js (and npm) installed on your machine
• A working Git repository to interact with

Step-by-step installation:

1. Clone or download the MCP server repository that contains the aira server.
2. Navigate into the project directory:
   • cd path/to/aira-mcp-server
3. Install dependencies:
   • npm install
4. Build the TypeScript code (if applicable):
   • npm run build
5. Run or deploy the server using your preferred MCP runner configuration (as shown in the usage example):
   • Ensure the built entry exists at build/index.js, or adjust the path accordingly.
6. Add the server to your MCP settings, for example: { "mcpServers": { "aira": { "command": "node", "args": ["path/to/aira-mcp-server/build/index.js"] } } }

Notes and tips:

• Ensure the build output path matches the path specified in your MCP configuration (build/index.js in the example).
• The server exposes several tools (get_status, create_commit, init_gitflow, create_branch, merge_branch, list_branches); make sure you pass the required parameters to each tool according to your MCP framework's conventions.
• If you modify TypeScript sources, remember to re-run npm run build to update the entry file.
• Typical environment considerations include ensuring Git is available in the runtime environment and that the server has access to the repository you intend to manage.
• If you encounter issues with path resolution, use an absolute path to the built entry file in the args.