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
      F
      license
      A
      quality
      D
      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
      66 npm
      5
      -

    • Minecraft MCP Server

      avinash893
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage, configure, and operate game servers hosted on Pterodactyl panels, including power actions, console commands, file operations, plugin installation, and backups. It also supports Cloudflare challenge bypass and automatic request pacing for reliable panel automation.
      MIT
    • horizOn MCP Server by ProjectMakersDE

      horizOn MCP Serverofficial

      ProjectMakersDE
      A
      license
      A
      quality
      A
      maintenance
      Enables AI coding assistants to access documentation, live API tools, and workflow prompts for integrating a game/app backend service into Godot, Unity, and Unreal Engine projects, including auth, leaderboards, cloud saves, remote config, localization, news, gift codes, feedback, logs, crash reporting, email, and admin dashboard management.
      34
      428 npm
      MIT

    • 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
    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 22 tools

    Disambiguation4/5

    Almost every tool targets a distinct resource+action (apps, versions, deployments, relay sessions, registry, config, skills), and the descriptions explicitly steer between the few that could overlap. The deployment trio (deploy/get_deployment/wait_for_deployment) is the only real overlap, but the text clearly explains when to use each, so ambiguity is minimal.

    Naming Consistency4/5

    Nearly all tools follow a consistent edgegap_verb_noun pattern (list_apps, create_app, get_deployment, stop_deployment). Minor deviations like edgegap_deploy (verb only) and edgegap_context (noun only) break the pattern slightly but remain readable and unambiguous.

    Tool Count4/5

    22 tools is on the heavy side, but the domain is genuinely broad (app/version lifecycle, deployments, relay sessions, registry, Dockerfile/config generation, matchmaker, and skills). Each tool maps to a distinct capability rather than padding, so the count is justified though near the upper bound.

    Completeness4/5

    Deployment and relay lifecycles are well covered (create/list/get/wait/stop, plus logs, and full relay CRUD), and config/skill helpers round it out. The main gaps are app- and version-level update/delete operations, which are minor and likely intentional given the API surface.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources