atomgit

AtomGit MCP Server provides a set of MCP endpoints that integrate with the AtomGit open-source collaboration platform. It exposes a suite of tools to manage repositories, issues, pull requests, branches, and labels on AtomGit, enabling an AI agent to perform common repository management tasks programmatically. You can authenticate with your AtomGit access token and invoke tools such as listing user-owned repositories, creating issues, commenting on issues, managing pull requests, and handling branches and labels. The server is designed to be invoked via a Node.js runtime and expects the MCP server entry point to be at dist/index.js, with the AtomGit API token supplied through the ATOMGIT_PERSONAL_ACCESS_TOKEN environment variable. After starting, clients can send MCP requests to the server to perform operations within the AtomGit ecosystem. The available tools cover typical repository workflows, including creating and updating issues, listing issues, managing pull requests, and manipulating branch information and labels.

Prerequisites:

• Node.js v18.0+ (recommended by the project)
• pnpm v6+ (for building from source)
• An AtomGit account with a Personal Access Token (PAT)

Installation steps (from source):

1. Clone the repository

• git clone https://atomgit.com/atomgit-open-source-ecosystem/atomgit-mcp-server.git
• cd mcp-server-atomgit

2. Install dependencies

• pnpm install

3. Build the project

• pnpm build

4. Run the MCP server (example using Node.js runtime)

• node dist/index.js

5. Provide required environment variable (PAT) when starting the server

• ATOMGIT_PERSONAL_ACCESS_TOKEN=<your-atomgit-api-key-here> node dist/index.js

Notes:

• If you are using npx to start the server for claude or VSCode integration, you can follow the examples in the README that show starting via npx atomgit-mcp-server@latest with the appropriate PAT environment variable.

Tips and common considerations:

• Always supply ATOMGIT_PERSONAL_ACCESS_TOKEN with a valid AtomGit PAT to authorize API calls.
• When running in containers or CI, ensure the environment variable is securely provided and not logged.
• The server exposes a range of tools for repos, issues, PRs, branches, and labels. If a tool is missing a capability you need, check for updates or contribute to extend tooling.
• For NPX-based startup, use the package name atomgit-mcp-server and the -y flag as shown in the README examples to install and run quickly.
• If encountering connectivity or authentication errors, verify the PAT scopes on AtomGit and that the server process has network access.
• The mcp-config structure expects a top-level mcpServers map with a unique server key. You can host multiple MCP servers by adding additional entries.