Skip to main content
Glama
deslay1

amendor-mcp

by deslay1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to amendor-mcp

No user-submitted related servers found.

    Related Servers

    • Agentic MCP Server

      ShunsukeHayashi
      -
      license
      B
      quality
      Not graded
      maintenance
      Enables 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
      -

    • bgagents

      michael-elkabetz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      46
      MIT

    • AutomateHub

      Xesderte
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate GitHub repository management, issue tracking, and commits using natural language.
      2 npm
      Apache 2.0

    • WebsiteOps MCP Server

      anilreddykota
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridges AI coding assistants with website codebases, local git repositories, and shared hosting via FTP/SFTP, enabling code discovery, file management, git operations, smart deployments, backups, and rollbacks.
      5 npm
      MIT

    • golive-mcp

      abbylester1
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to deploy code to any hosting provider by creating PRs, building, and verifying health checks, all from a single natural language command.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources