Skip to main content
Glama
Constructor Research MCP

Constructor Research MCP

by NRGGIT

Related Servers

Alternatives to Constructor Research MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to build and deploy an app from a GitHub repository to a managed live server and then operate it — logs, captured errors, health checks, managed Postgres, secrets, custom domains, email authentication, and Stripe checkout links. It also exposes safe, read/write-labelled tools so agents can rebuild, start/stop, and inspect projects without ever editing source code.
      MIT
    • A
      license
      Not graded
      quality
      C
      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.
      63 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables deployment and management of applications on the Citizen platform from git repositories or local files. It allows AI assistants to monitor deployment logs, handle authentication, and automatically fix build errors using intelligent error analysis.
      11
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to build, deploy, and inspect apps through a hosted backend service, including reading platform docs, deploying raw source, inspecting logs, verifying live pages in browsers, and managing project tasks.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to check repository deploy readiness, deploy apps to your own cloud (AWS, Google Cloud, Azure, DigitalOcean), and migrate apps from platforms like Heroku, Railway, Render, or Vercel with rollback.
      MIT

    TDQS

    A3.9/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target clearly distinct resources/actions (file ops vs image ops vs service lifecycle vs observability). There is some conceptual overlap: deploy_app and update_app both trigger builds that build_image can do standalone, and get_deployment overlaps with get_logs for observing failures, but the descriptions give enough guidance to pick correctly.

    Naming Consistency5/5

    All names are snake_case and verb-first (list_files, build_image, create_folder, sync_files, move_path, delete_path, deploy_app, start_app, get_deployment, get_logs). sign_in is a phrasal verb but fits the same convention cleanly.

    Tool Count5/5

    14 tools is well within the ideal range and each earns its place across file management, image building, deployment lifecycle, and auth. Nothing feels redundant or thin.

    Completeness4/5

    Core workflows are covered: upload/move/delete files, build/list images, deploy/update/start/stop services, observe deployments and logs, and sign in. Minor gaps exist—no tool to read/download file contents from a disk and no image deletion—but agents can work around these.