Edgegap

Name: Edgegap
Author: dev.edgegap

MCP serverMCP

Deploy and operate multiplayer game servers on Edgegap's global edge network.

by dev.edgegaprepository ↗homepage ↗v0.3.2Apache-2.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"edgegap","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability (some checks stopped at authentication)101/101 checks ok

Some successful checks reached the service and some stopped at an authentication response; figures combine both.

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	30 ms	server edgegap 0.3.3 · protocol 2025-06-18 · 19 tools
9 h ago	mcp initialize	ok	200	56 ms	server edgegap 0.3.3 · protocol 2025-06-18 · 19 tools
15 h ago	mcp initialize	ok	200	68 ms	server edgegap 0.3.2 · protocol 2025-06-18 · 19 tools
22 h ago	mcp initialize	ok	200	39 ms	server edgegap 0.3.2 · protocol 2025-06-18 · 19 tools
29 h ago	mcp initialize	ok	200	61 ms	server edgegap 0.3.2 · protocol 2025-06-18 · 19 tools
2 d ago	mcp initialize	ok	200	68 ms	server edgegap 0.3.0 · protocol 2025-06-18 · 19 tools
2 d ago	mcp initialize	ok	200	58 ms	server edgegap 0.3.0 · protocol 2025-06-18 · 19 tools
2 d ago	mcp initialize	ok	200	44 ms	server edgegap 0.3.0 · protocol 2025-06-18 · 19 tools
2 d ago	mcp initialize	ok	200	54 ms	server edgegap 0.3.0 · protocol 2025-06-18 · 19 tools
3 d ago	mcp initialize	ok	200	52 ms	server edgegap 0.3.0 · protocol 2025-06-18 · 19 tools

Tools observed via MCP handshake

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 du
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 d
edgegap_list_app_versions — List the versions under an application, with their container image, resources, ports (including whether TLS Upgrade is on, which browser/WebGL clients need for
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
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 multiplaye
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_d
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
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 ser
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
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 id
edgegap_generate_dockerfile — 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, t
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 t
edgegap_get_registry_credentials — Get the push login for this organization's private Edgegap container registry (registry.edgegap.com) and the exact docker login, build and push commands for you
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 land
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.
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_sessio
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 t
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.
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 rela

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

mcpedgegapgame-servermultiplayerunityunreal

kind Official MCP Registry

name Official MCP Registry

license npm registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

npm registry@edgegap/mcp

first seen 12 h ago · fetched 12 h agoopen ↗

Official MCP Registrydev.edgegap/mcp

first seen 28 d ago · fetched 12 h agoopen ↗

Field history (12 recent events)

12 h ago · declared · version → "0.3.2"
12 h ago · observed · packageFacts → {"name":"@edgegap/mcp","registry":"npm","publishedAt":"2026-10-08T18:19:13.234Z","latestVersion":"0.3.2","weeklyDownload
12 h ago · declared · license → "Apache-2.0"
6 d ago · declared · version → "0.3.0"
9 d ago · declared · version → "0.2.0"
22 d ago · declared · version → "0.1.4"
24 d ago · declared · version → "0.1.1"
28 d ago · declared · summary → "Deploy and operate multiplayer game servers on Edgegap's global edge network."
28 d ago · declared · protocols → ["mcp"]
28 d ago · declared · version → "0.1.0"
28 d ago · declared · repoUrl → "https://github.com/edgegap/edgegap-mcp"
28 d ago · declared · homepageUrl → "https://edgegap.com"

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from