MCP serverdev.edgegap/mcp
Deploy and operate multiplayer game servers on Edgegap's global edge network.
Overview
Score?
UNRATED 0.603
of what a free look can see, on 18 looks
Looks
24
last 3 hr ago
Tools
19
changed 2 days ago
More info
URL
mcp.edgegap.dev/mcp
streamable-http
Says it is
edgegap 0.3.0
protocol 2025-06-18
In the record since
22 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.603 · highest on record 0.8561
Toolsfrom sha256:3edde641ff…0d4e67 · +1 −0 2 days ago
| Tool | Schema |
|---|---|
| edgegap_authorize_relay_user Authorize one more player (by public IP) on an existing relay session, for a player joining after the session was created. Returns that player's authorization token. |
input · no output |
| edgegap_build_matchmaker_config Generate a ready-to-upload Edgegap matchmaker JSON configuration with one profile: team count and size, optional latency rule, and optional expansions that relax the rules the long |
input · no output |
| 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 anyth |
input · no output |
| 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 (see edgegap_get_registry_credential |
input · no output |
| edgegap_create_relay_session A relay is NOT a game server and is not the recommended default — for a multiplayer match, deploy an authoritative dedicated server with edgegap_deploy instead. A relay only forwar |
input · no output |
| edgegap_delete_relay_session Close one relay session. Connected players lose their relay connection. Delete every session you created for testing before ending your task. |
input · no output |
| edgegap_deploy Start one authoritative dedicated game server from an application version, placed near the players you specify. This is the recommended way to host a multiplayer match: the server |
input · no output |
| edgegap_generate_dockerfile added Write a Dockerfile for this project's headless game server build, ready for Edgegap: linux/amd64 base, the build folder copied in, the binary made executable, the right headless fl |
input · no output |
| 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 |
input · no output |
| 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 |
input · no output |
| edgegap_get_registry_credentials Return the registry URL, project, username and token for this organization's private Edgegap container registry (registry.edgegap.com), plus the exact docker login, build and push |
input · no output |
| edgegap_get_relay_session Read one relay session: whether it is ready, the relay address and ports, and each authorized player with their authorization token. edgegap_create_relay_session already waits for |
input · no output |
| 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 wh |
input · no output |
| 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 "applica |
input · no output |
| edgegap_list_deployments List active deployments, optionally filtered and sorted. Use this to find deployments left running from earlier sessions before starting new ones — orphaned servers cost money. Fil |
input · no output |
| edgegap_list_registry_tags List the tags pushed for one image in this organization's Edgegap container registry, with push time and size. Call it after docker push to confirm the tag landed before edgegap_cr |
input · no output |
| 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 d |
input · no output |
| edgegap_validate_server_config Check a game server Dockerfile and the ports/resources you intend to register against what Edgegap requires, BEFORE building and pushing. Catches the failures that otherwise only s |
input · no output |
| 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 |
input · no output |
Verify it yourself
npx teppi-check https://mcp.edgegap.dev/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M29X9WEZ01NS61N4SS2DE4MC