Edgegap MCP Server
OfficialRelated Servers
Alternatives to Edgegap MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables AI agents to deploy multiplayer web games as playable URLs with rooms, live state sync, and leaderboards, all through a single tool call.4116 npm5-
MileHost MCP Serverofficial
AlicenseCqualityBmaintenanceEnables AI coding agents to manage cloud containers, create and edit files, run commands, and deploy projects directly.247MIT- AlicenseAqualityAmaintenanceEnables 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.34786 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex and other agents to discover live AutoDL GPU stock, produce cost- and time-optimized rental plans with human review, and manage approved Elastic/Pro deployments through the official API.5Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables 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.1887 npmMIT
TDQS
Scored across 19 tools
Most tools target clearly distinct resources and actions (deploy vs. relay session, create_app vs. create_app_version vs. create_relay_session). The only mild overlaps are edgegap_get_deployment vs. edgegap_wait_for_deployment and edgegap_list_deployments vs. edgegap_get_deployment, but the descriptions explicitly distinguish polling from one-shot reads. Boundaries are well communicated overall.
Every tool uses the edgegap_ prefix with a consistent snake_case verb_noun pattern (list_apps, create_app_version, deploy, get_deployment, stop_deployment, delete_relay_session). The convention is uniform throughout with no camelCase or style mixing.
19 tools is on the heavier side but each maps to a distinct step in a genuinely broad domain (apps, versions, deployments, relays, registry, and build-time helpers). No tool appears redundant, so the count is justified though slightly high.
Covers the full deployment lifecycle (deploy, wait, get, list, stop, logs), app/version creation and listing, registry access, relay session management, and build-time helpers. Minor gaps exist (no delete/update for applications or versions, no explicit list of applications' full settings), but core workflows are complete.