AtomGit 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_user_repositoryC | Search for AtomGit user repository |
| assign_issueC | Assign users to an issue in a AtomGit repository |
| list_repository_issuesC | List issues in a AtomGit repository |
| get_issue_detailsC | Get details of a specific issue in a AtomGit repository |
| list_issue_assigneesC | List assignees for a specific issue in a AtomGit repository |
| check_if_user_is_assignableC | Check if a user can be assigned to an issue in a AtomGit repository |
| get_user_repositoriesC | Search for AtomGit user repositories |
| get_org_repositoriesC | Search for AtomGit org repositories |
| create_issueC | Create a new issue in a AtomGit repository |
| create_issue_commentC | Create an issue comment in a AtomGit repository issue |
| create_pull_requestC | Create a new pull request in a repository |
| get_pull_request_detailsC | Get details of a specific pull request |
| create_pull_request_commentC | Create a comment on a pull request |
| create_pull_request_replyC | Reply to a comment on a pull request |
| get_pull_request_commentC | Get details of a specific pull request comment |
| list_repository_branchesC | List branches in a repository |
| get_repository_branch_detailsB | Get details of a specific branch in a repository |
| get_repository_labelsC | Get all labels in a repository |
| create_issue_labelsC | Add labels to an issue in a repository |
| get_issue_labelsB | Get all labels for an issue in a repository |
| delete_issue_labelC | Remove a label from an issue in a repository |
| get_label_by_nameB | Get a single label by name from a repository |
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 22 tools
Most tools have distinct purposes, but there is some overlap between 'get_user_repositories' and 'get_user_repository' which could cause confusion, and 'create_pull_request_comment' vs 'create_pull_request_reply' might be ambiguous without clear context. Overall, the tools are well-differentiated by resource and action.
All tools follow a consistent verb_noun pattern with snake_case, such as 'create_issue', 'get_issue_details', and 'list_repository_issues'. The naming is predictable and uniform throughout the set, making it easy for agents to understand and use.
With 22 tools, the count is on the higher side for a Git repository server, bordering on heavy. While it covers many operations, it might be overwhelming or redundant, such as having separate tools for 'get_user_repositories' and 'get_user_repository'.
The tool set provides comprehensive coverage for managing issues, pull requests, labels, repositories, and branches in AtomGit. It includes CRUD operations for issues and pull requests, label management, and repository/branch queries, with no obvious gaps for core workflows.