Atomgit MCP Server

MCP server for using AtomGit API

Local serverstdio

What is the Atomgit MCP server?

Atomgit MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for using AtomGit API.

What you get

AtomGit MCP 服务器是专门为 AtomGit 开源协作平台的模型上下文(MCP) 服务的实现。提供了一系列方法,允许 AI 管理 AtomGit 开源协作平台的仓库、issues、pull requests、branch、label等。

What the assistant can call

Once Atomgit is connected, these are the calls the assistant has available:

  • get_user_repository — repo
  • get_user_repositories — repo
  • get_org_repositories — repo
  • create_issue — issue
  • create_issue_comment — issue
  • delete_issue_comment — issue
  • get_issue_comment — issue
  • list_issue_comments — issue
  • list_issues — issue
  • get_issue — issue
  • set_assignees — issue
  • list_issue_assignees — issue

Configuration and credentials

You will need one environment variable: ATOMGIT_PERSONAL_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Atomgit's toolset — get_user_repository, get_user_repositories, get_org_repositories and 11 more — is a fair guide to whether it matches your workflow. It is maintained by kaiyuanxiaobing; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Atomgit.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the atomgit mcp server does with a few real requests.

Available tools

ToolWhat it does
get_user_repositoryrepo
get_user_repositoriesrepo
get_org_repositoriesrepo
create_issueissue
create_issue_commentissue
delete_issue_commentissue
get_issue_commentissue
list_issue_commentsissue
list_issuesissue
get_issueissue
set_assigneesissue
list_issue_assigneesissue
check_if_user_is_assignableissue
create_pull_requestpull

How to install the Atomgit MCP server

#### claude 可执行文件启动
stdio mode:
```json
{
  "mcpServers": {
    "command": "node",
    "args": [
      "/home/user/work/mcp-server-atomgit/dist/index.js"
    ],
    "env": {
      "ATOMGIT_PERSONAL_ACCESS_TOKEN": "<your-atomgit-api-key-here>"
    },
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ATOMGIT_PERSONAL_ACCESS_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Atomgit to get user repository.
  • Use Atomgit to get user repositories.
  • Use Atomgit to get org repositories.

Frequently asked questions

It connects Atomgit to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_user_repository, get_user_repositories, get_org_repositories, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Atomgit directly.