Edgegap
dev.edgegap/mcp · v0.1.4 · MCP 2026-07-28
Deploy and operate multiplayer game servers on Edgegap's global edge network.
Reachability
reachable
checked 2026-09-20 05:33 UTC
Registry status active
Tools pinned 10
70c6f5ff5dab
Tools last changed
unchanged since first capture 2026-09-17
Repo last push 2026-09-17
GitHub stars 1
Provenance
Registry namespace dev.edgegap
(domain verified by the official registry)
Repository
github.com/edgegap/edgegap-mcp
repo gone
Website
https://edgegap.com
Remote endpoints
https://mcp.edgegap.dev/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-09-17 05:33 | first capture | 10 tools pinned |
Pinned tool definitions (10)
| Tool | Description |
|---|---|
| edgegap_list_apps | List the applications in the Edgegap organization. Start here before creating or deploying anything, so you reuse an existing application instead of making a duplicate. An "application" groups versions of one game server. |
| edgegap_create_app | Create a new application to hold game server versions. Only call this after edgegap_list_apps confirms no suitable application exists. Creating an application does not deploy anything — follow with edgegap_create_app_version. |
| edgegap_list_app_versions | List the versions under an application, with their container image and resource settings. Use this to find the version name to deploy, or to copy settings from a working version when creating a new one. |
| edgegap_create_app_version | Register a container image as a deployable version of an application. The image must already be pushed to a registry that Edgegap can pull from. Resource units: 1024 cpu units = 1 vCPU; memory_mb must be at least 256 and at most double... |
| edgegap_deploy | Start one containerized instance of an application version, placed near the players you specify. Returns immediately with a request_id; the server is still starting and has no connection details yet. Follow this call with... |
| edgegap_get_deployment | Read the current status of one deployment, including connection address and ports once it is ready. For a deployment you just created, prefer edgegap_wait_for_deployment — it polls for you instead of making you call this in a loop. |
| edgegap_wait_for_deployment | Poll a deployment until it is ready, errors, or the timeout expires, then return the connection details. This is the tool to call right after edgegap_deploy. Do not build your own polling loop — this handles backoff and reports the... |
| edgegap_list_deployments | List active deployments, optionally filtered. Use this to find deployments left running from earlier sessions before starting new ones — orphaned servers cost money. |
| edgegap_stop_deployment | Gracefully stop one deployment by request_id, sending SIGTERM to the container. Stop every deployment you started for testing before ending your task. This tool stops exactly one deployment; bulk stop is deliberately not exposed. |
| edgegap_get_deployment_logs | Retrieve stdout/stderr and crash output for a deployment. Call this whenever a deployment errors or a server exits unexpectedly — the crash exit code usually identifies the problem faster than redeploying does. Logs for stopped... |
Get alerted when this changes.
Email the moment dev.edgegap/mcp drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/dev.edgegap/mcp)
Maintain this server? Add the badge to your README. It links your users to this live status page.