Loading...

AtomGit MCP server enables AI agents to manage AtomGit repositories, issues, pull requests, branches, and labels using an API key for authentication.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
AtomGit MCP server enables AI agents to manage AtomGit repositories, issues, pull requests, branches, and labels using an API key for authentication.
This server offers a mix of read and write operations on AtomGit repositories. While the use of an API key provides some level of authentication, the lack of granular scopes and the presence of potentially destructive tools (comment deletion) necessitate careful management of the API key and its permissions. It's relatively safe for read-only operations, but risky for write operations if not properly controlled.
Performance will depend on the AtomGit API's responsiveness and the network connection. Consider implementing caching for frequently accessed data.
Cost depends on the number of API calls made to AtomGit. Monitor API usage to avoid exceeding rate limits and incurring unexpected costs.
{
"mcpServers": {
"command": "node",
"args": [
"/home/user/work/mcp-server-atomgit/dist/index.js"
],
"env": {
"ATOMGIT_PERSONAL_ACCESS_TOKEN": "<your-atomgit-api-key-here>"
},
}
}get_user_repositoryLists a user's authorized repository.
Read-only operation.
get_user_repositoriesLists all repositories authorized for a user.
Read-only operation.
get_org_repositoriesLists all repositories authorized for an organization.
Read-only operation.
create_issueCreates a new issue in a repository.
Creates content, but does not modify existing code.
create_issue_commentCreates a comment on an issue.
Adds content, but does not modify existing code.
delete_issue_commentDeletes a comment on an issue.
Deletes user-generated content.
get_issue_commentRetrieves a specific comment from an issue.
Read-only operation.
list_issue_commentsLists all comments on an issue.
Read-only operation.
list_issuesLists all issues in a repository.
Read-only operation.
get_issueRetrieves details for a specific issue.
Read-only operation.
set_assigneesSets the assignees for an issue.
Modifies issue metadata.
list_issue_assigneesLists the assignees for an issue.
Read-only operation.
check_if_user_is_assignableChecks if a user can be assigned to an issue.
Read-only operation.
create_pull_requestCreates a new pull request.
Creates a new pull request.
get_pull_request_detailsRetrieves details for a specific pull request.
Read-only operation.
create_pull_request_commentCreates a comment on a pull request.
Adds content, but does not modify existing code.
create_pull_request_replyReplies to a comment on a pull request.
Adds content, but does not modify existing code.
get_pull_request_commentRetrieves a specific comment from a pull request.
Read-only operation.
list_repository_branchesLists all branches in a repository.
Read-only operation.
get_repository_branch_detailsRetrieves details for a specific branch in a repository.
Read-only operation.
get_repository_labelsRetrieves all labels in a repository.
Read-only operation.
create_issue_labelsAdds labels to an issue.
Modifies issue metadata.
get_issue_labelsRetrieves all labels for an issue.
Read-only operation.
delete_issue_labelRemoves a label from an issue.
Modifies issue metadata.
get_label_by_nameRetrieves a specific label from a repository by name.
Read-only operation.
API Key
local
This server offers a mix of read and write operations on AtomGit repositories. While the use of an API key provides some level of authentication, the lack of granular scopes and the presence of potentially destructive tools (comment deletion) necessitate careful management of the API key and its permissions. It's relatively safe for read-only operations, but risky for write operations if not properly controlled.
The server defaults to read and write access based on the provided API key. There is no built-in sandboxing or rollback mechanism. Exercise caution when granting autonomy.
Production Tip
Implement robust logging and monitoring to track actions performed by the server and detect potential issues.
The server uses AtomGit Personal Access Tokens for authentication.
Rate limiting is not explicitly mentioned, so it's recommended to implement your own rate limiting logic.
The documentation does not specify granular permission scopes. It's best to use an API key with the minimum required permissions.
No, you'll need to implement your own logging and monitoring solution.
Error handling is not documented, but you can likely use standard Node.js error handling techniques.
No, this server does not appear to support webhooks. It relies on direct API calls.
No, this server is specifically designed for AtomGit.