Skip to main content
Glama
edgegap

Edgegap MCP Server

Official
by edgegap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Edgegap MCP Server

No user-submitted related servers found.

    Related Servers

    • antics-mcp by antics-gg

      antics-mcpofficial

      antics-gg
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to deploy multiplayer web games as playable URLs with rooms, live state sync, and leaderboards, all through a single tool call.
      4
      82 npm
      5
      -

    • deployplan

      jsuncar
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to deploy Next.js apps and provision Postgres, Redis, MinIO, NATS, Mailpit, and nginx locally via Docker without requiring Vercel or Supabase signups, using a single account and reading logs from the same environment.
      MIT

    • BasicDeploy MCP Server

      AkaciaNL
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create and manage BasicDeploy containers with PostgreSQL, S3 storage, and public URLs, including deploying apps, running commands, viewing logs, and sharing containers.
      18
      137 npm
      MIT

    • Godot MCP

      MhrnMhrn
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create, edit, and run Godot 4.5+ games by providing tools for project scaffolding, scene manipulation, and engine interaction. It supports full game development workflows including node editing, script attachment, and project execution with debugging capabilities.
      24
      5
      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.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: apps, versions, deployments, and logs. The only close pair is get_deployment vs wait_for_deployment, but their descriptions explicitly distinguish one-shot status read from polling helper, so there is no real ambiguity.

    Naming Consistency4/5

    All tools share the edgegap_ prefix and mostly follow a verb_noun pattern (list_deployments, create_app, get_deployment_logs). Minor deviations like the bare verb 'deploy' and 'wait_for_deployment' are still predictable and readable.

    Tool Count5/5

    With 10 tools covering apps, versions, and deployments, the count is well-scoped for the domain. Each tool maps to a clear lifecycle step, and no tool feels redundant.

    Completeness4/5

    The core workflow is fully covered: create/list apps, create/list versions, deploy, wait, get status, logs, and stop. Missing update/delete for apps/versions and bulk stop are minor gaps, but agents can complete typical tasks without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources