Edgegap is an MCP server with 10 tools an agent can call, among them edgegap_create_app, edgegap_create_app_version, edgegap_deploy. It answers at https://mcp.edgegap.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Deploy and operate multiplayer game servers on Edgegap's global edge network.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: name, is_active |
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 the Inputs: application, name, docker_repository, docker_image, docker_tag, cpu_units |
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_wait_for_d Inputs: application, version, users, env, tags, cpu_units |
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. Inputs: request_id |
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 deployments Inputs: request_id, max_characters |
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. Inputs: application |
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. Inputs: limit, page |
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. Inputs: filter, limit |
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. Inputs: request_id |
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 containe Inputs: request_id, timeout_seconds |
Every block below points at https://mcp.edgegap.dev/mcp. Pick your client and copy.
claude mcp add --transport http edgegap https://mcp.edgegap.dev/mcp
{
"mcpServers": {
"edgegap": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.edgegap.dev/mcp"]
}
}
}{
"mcpServers": {
"edgegap": {
"url": "https://mcp.edgegap.dev/mcp"
}
}
}{
"servers": {
"edgegap": {
"type": "http",
"url": "https://mcp.edgegap.dev/mcp"
}
}
}{
"context_servers": {
"edgegap": {
"url": "https://mcp.edgegap.dev/mcp"
}
}
}{
"mcpServers": {
"edgegap": {
"serverUrl": "https://mcp.edgegap.dev/mcp"
}
}
}{
"mcpServers": {
"edgegap": {
"url": "https://mcp.edgegap.dev/mcp"
}
}
}name: Edgegap
version: 0.0.1
schema: v1
mcpServers:
- name: Edgegap
type: streamable-http
url: https://mcp.edgegap.dev/mcp{
"mcpServers": {
"edgegap": {
"httpUrl": "https://mcp.edgegap.dev/mcp"
}
}
}{
"mcpServers": {
"edgegap": {
"type": "http",
"url": "https://mcp.edgegap.dev/mcp"
}
}
}{
"mcpServers": {
"edgegap": {
"url": "https://mcp.edgegap.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.edgegap.dev%2Fmcp&type=streamable_http&id=edgegap&name=Edgegap
It answered our last check on 24 October 2026 in 296 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by edgegap.dev and served from mcp.edgegap.dev, the vendor's own domain: https://mcp.edgegap.dev/mcp.
10, as returned by the server's own tools/list on 23 September 2026: edgegap_create_app, edgegap_create_app_version, edgegap_deploy, edgegap_get_deployment, edgegap_get_deployment_logs, edgegap_list_app_versions, edgegap_list_apps, edgegap_list_deployments, and 2 more.
It answered our last check on 24 October 2026 in 296 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.edgegap.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.edgegap. Endpoint host: mcp.edgegap.dev. ARD identifier: urn:air:dev.edgegap:mcp:mcp.
First indexed 12 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.