Skip to main content
Glama
daffaoir

bedengan-apps

by daffaoir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to bedengan-apps

No user-submitted related servers found.

    Related Servers

    • Somewhere MCP

      Somewhere-Tech
      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

    • Deploy MCP

      Tusharjain-19
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to deploy websites directly to Vercel from the IDE, automating framework detection, build validation, and secure environment variable synchronization, with live status updates.
      1
      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

    • thedeployer

      Avinash147-1193
      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
    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.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a reasonably distinct role: validation, creation, updating, status lookup, and listing. The only mild overlap is between check_status and list_my_apps, since both expose submission/app state, but one is single-item-oriented and the other is an overview.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern: validate_project, submit_app, check_status, update_app, list_my_apps. The style is uniform and predictable, making it easy to anticipate what each tool does.

    Tool Count5/5

    Five tools is well-scoped for an app deployment workflow: validate, create, update, check status, and list apps. Each tool earns its place and there is no unnecessary redundancy or bloat.

    Completeness4/5

    The core lifecycle is covered: validate before deploy, submit new apps, update existing apps, check status, and list owned apps. A delete or rollback tool is missing, but rollback is explicitly handled through the web dashboard, so the gap is minor.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources