A
licenseNot graded
qualityD
maintenanceAn MCP server for managing your repositories on Forgejo/Gitea server.
69
Mozilla Public 2.0
mcp-pagure
by lemenkov
Related Servers
Alternatives to mcp-pagure
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server for managing Git operations on local repositories, allowing users to list repositories, get and create tags, list commits, push tags, and refresh repositories through a standardized interface.63-
- FlicenseNot gradedqualityDmaintenanceMCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.-
- AlicenseAqualityCmaintenanceMCP server for interacting with GitHub Pull Requests, enabling listing, viewing, commenting, reviewing, and merging PRs.685 npm2MIT
- AlicenseBqualityDmaintenanceMCP server for interacting with Gitea, enabling issue and PR management, repository browsing, file reading, and safe git command execution.1137 npm1MIT
- FlicenseNot gradedqualityCmaintenanceUnified MCP server for Git forge management across GitHub, GitLab, Gitea, and Bitbucket, enabling repository, issue, PR, and CI/CD operations via CLI tools and APIs.-
TDQS
A3.6/5.0
Scored across 11 tools
Disambiguation5/5
Each tool has a clearly distinct purpose targeting specific resources and actions in the Pagure domain. For example, close_pull_request, merge_pull_request, and comment_on_pr all operate on pull requests but perform different operations, while get_commit, get_file, and get_project_info retrieve different types of information without overlap.
Naming Consistency5/5
All tools follow a consistent verb_noun naming pattern using snake_case throughout. The verbs are clear and descriptive (close, comment, fork, get, list, merge), and the nouns precisely identify the target resources (pull_request, project, commit, file, branches).
Tool Count5/5
With 11 tools, this server is well-scoped for a Pagure integration. The count covers essential operations for repository management, pull request handling, and project information retrieval without being overwhelming or insufficient for the domain.
Completeness4/5
The toolset provides strong coverage for core Pagure workflows including project listing/info, file/commit access, branch management, and full pull request lifecycle (list, get, comment, close, merge). A minor gap exists in creating or updating resources like projects or pull requests, but agents can work effectively with the available read and modify operations.
Maintenance
ActivityInactive
ResponsivenessNo issues