amendor-mcp
Related Servers
Alternatives to amendor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects MCP-compatible AI coding agents to self-hosted instances so they can discover projects, repositories, and branches, then create or update pull requests from a local Git context and return the PR number and browser URL. An explicit repository allowlist restricts all repository and pull request reads and writes.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI chatbots to act like coding agents on your own computer by executing code, editing files, running terminal commands, and performing Git operations through a secure cloud bridge. Supports token-based pairing, path sandboxing, and configurable approval for destructive actions.MIT
- -licenseBqualityNot gradedmaintenanceEnables AI-driven orchestration of GitHub development workflows including automated issue analysis, code generation, code review, and PR creation through multiple specialized agents. Integrates with GitHub Actions to automate the complete development process from issue to pull request.7-
- AlicenseNot gradedqualityDmaintenanceEnables turning AI code agents like Anthropic Claude and OpenAI Codex into background agents accessible via MCP protocol for code generation, branch creation, and PR automation.48MIT
- AlicenseNot gradedqualityAmaintenanceConnects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.18MIT
- FlicenseNot gradedqualityCmaintenanceEnables autonomous coding agents to inspect Git commits, create pull requests, parse issue threads, and post reviews on GitHub repositories.-
TDQS
Scored across 7 tools
Most tools have distinct purposes, but publish_preview and set_preview_url both mark a change request as ready for review, potentially confusing an agent. start_build is a separate local-mode flow that could be misused if the normal GitHub flow is expected.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_change_request, publish_preview, ship_change), making them predictable and easy to understand.
With 7 tools covering listing, detail retrieval, status updates, preview management, and final shipping, the count is well-scoped for managing change requests without excess or deficiency.
The tool set covers the main lifecycle but lacks a creation tool, which is acceptable if change requests are always created externally. update_status provides flexibility for status transitions.