ติดตั้ง Edgegap อย่างไร?

คัดลอกคอนฟิก http สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP

Edgegap ต้องใช้ API key ไหม?

ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: EDGEGAP_API_TOKEN

Edgegap ใช้ทรานสปอร์ตแบบใด?

Edgegap เข้าถึงได้ผ่าน HTTP

Edgegap ถูกตรวจสอบล่าสุดเมื่อใด?

ตรวจสอบล่าสุดเมื่อ 2026-11-14 Deploy and operate multiplayer game servers on Edgegap's global edge network.

เซิร์ฟเวอร์ MCP Edgegap

Power your agent

เพิ่มเซิร์ฟเวอร์นี้

URL ของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP

เพิ่มใน Cursor เพิ่มใน Claude เพิ่มใน VS Code รันบน PlugMCP

Host a copy with our keys and logs.

URL ของเซิร์ฟเวอร์

https://mcp.edgegap.dev/mcp

ข้อมูลรับรองจากผู้เผยแพร่

EDGEGAP_API_TOKEN — Edgegap API token. Optional — omit it and you're prompted at first use.

ปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง

shClaude Code

1claude mcp add --transport http dev.edgegap-mcp https://mcp.edgegap.dev/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "dev.edgegap-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.edgegap.dev/mcp"9      ]10    }11  }12}

claude_desktop_config.json

รีโมต · HTTPการติดตั้งจากผู้เผยแพร่ทีละขั้นตอน: เพิ่มใน Claude

URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร

รันบน PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

เปิด

ข้อมูลเซิร์ฟเวอร์

รีโมต

ทรานสปอร์ต: http
เวอร์ชัน: 0.19.0
API key

จากผู้เผยแพร่

เอกสารประกอบ

Edgegap MCP Server

Connect AI coding agents to Edgegap through our MCP server. Your agent can take a headless server build all the way to players connecting: write or check the Dockerfile, push the image to your private Edgegap registry, deploy an authoritative dedicated server close to players, and read logs when something breaks.

	Dedicated server (recommended)	Relay
What Edgegap runs	Your headless server build, close to players	A traffic forwarder only, no game code
Who runs the game	The server	One player's game (the host)
Cheating	Much harder, the server has authority	The host can change anything
Fairness	Every player connects directly to the server	The host has no latency, everyone else goes through two hops
When the host leaves	The match continues	The match ends, unless your game supports host migration
Performance limited by	The server's allocated CPU and memory	The host's PC and home internet upload
You need	A server build in a container image	Netcode built as a listen server (host-client)

Variable	Default	Purpose
`EDGEGAP_API_TOKEN`	(prompted)	API token. Optional: omit it and you're asked at first use. The `token` prefix is added for you. Never pass it as a command-line argument.
`EDGEGAP_READ_ONLY`	`0`	Set to `1` and the eight mutating tools are never registered, so the agent cannot be talked into calling them.
`EDGEGAP_APP_ALLOWLIST`	(empty)	Comma-separated application names. Limits what the agent can create and deploy into. Reading (listing apps and versions) is not limited, and neither is touching deployments once running. See DESIGN.md.
`EDGEGAP_MAX_DURATION_MINUTES`	`60`	Ceiling on `max_duration` the agent may set on a version.
`EDGEGAP_MAX_AGENT_DEPLOYMENTS`	`5`	`edgegap_deploy` refuses while this many deployments tagged `edgegap-mcp` are running. `0` turns the cap off.
`EDGEGAP_TIMEOUT_MS`	`30000`	Per-request HTTP timeout.

Skill	For
`edgegap`	Start here for any engine other than Unity or Unreal Engine, or platform questions. Routes to the rest.
`edgegap-unity`	Unity end to end: server build, matchmaker, client, end-to-end test.
`edgegap-ngo`	Unity with Netcode for GameObjects end to end: server start and self-stop, Find Match panel, Boss Room adapter, matchmaker.
`edgegap-fishnet`	Unity with FishNet end to end: headless server, Bayou/WebGL, matchmaker, end-to-end test.
`edgegap-purrnet`	Unity with PurrNet end to end: dedicated server, connect panel, matchmaker, end-to-end test.
`edgegap-fusion`	Unity with Photon Fusion 2 end to end: IL2CPP Linux server, server bound to 0.0.0.0, Edgegap deployment, BR200 kit.
`edgegap-manus`	Browser games built with Manus: backend matchmaking, Steam sign-in, signed join tokens, Node WebSocket server.
`edgegap-unreal`	Unreal Engine end to end: source engine, Linux server, matchmaker, end-to-end test.
`edgegap-eos-voice`	Voice chat for an Unreal game on Edgegap with EOS Voice: server-side room tokens, match and team rooms.
`edgegap-server-design`	Authoritative server design and the deployment lifecycle.
`edgegap-containerize`	The container contract, Dockerfiles, registries, app versions.
`edgegap-local-testing`	Parity tests on your machine, then one smoke-test deployment.
`edgegap-troubleshoot`	Pull errors, crash loops, out-of-memory, clients that can't connect.
`edgegap-deployments-api`	Backend code that deploys servers: webhooks, cleanup, Nakama, PlayFab, UGS, EOS.
`edgegap-launch`	Launch checklist, rollouts, caching, cost control.

Tool	What it does
`edgegap_context`	Shows which API this server talks to, its version, local or hosted, and the guardrails in force. No API call; never shows the token.

Tool	What it does
`edgegap_generate_dockerfile`	Writes a Dockerfile for your server build: your build folder, server binary or start script, ports, and launch arguments, with the right headless flags (Unity `-batchmode -nographics`, Godot `--headless`), a non-root user for Unreal, and matching ports. Lists anything it had to assume so your agent can confirm it. Works for Unity, Unreal Engine, Godot, and any other engine.
`edgegap_validate_server_config`	Checks an existing Dockerfile, ports, resources, and image tag before you build. Catches ARM or Windows images (Edgegap runs `linux/amd64`), Unreal servers running as root, missing Unity `-batchmode -nographics`, servers bound to `localhost`, ports that don't match your netcode transport, and the `latest` tag.
`edgegap_get_registry_credentials` ●	Returns push credentials for your private Edgegap container registry, with the exact `docker login`, build, and push commands. Edgegap only gives these to the Unity/Unreal plugins' quick-start token; with a regular API token, it tells your agent to ask you for the login from the dashboard's Container Registry page instead.
`edgegap_list_registry_tags`	Confirms your image push landed before you register it. Takes the image name only, e.g. `my-game-server`: the project comes from your token.

Tool	What it does
`edgegap_list_apps`	Lists your applications.
`edgegap_create_app` ●	Creates an application.
`edgegap_list_app_versions`	Lists versions with their image, resources, ports (with TLS Upgrade), and whether a registry login is set.
`edgegap_create_app_version` ●	Registers a container image as a deployable version. Supports TLS Upgrade on WS and HTTP ports, which browser (WebGL) clients need for `wss://`.
`edgegap_deploy` ●	Deploys an authoritative dedicated server close to your players. Always tagged `edgegap-mcp`, and reports when Edgegap will stop it.
`edgegap_wait_for_deployment`	Waits until the server is ready and returns the connection address.
`edgegap_get_deployment`	Reads a deployment's status.
`edgegap_list_deployments`	Lists running deployments, filtered by application, version, status, tags and more, and sorted by age. Finds servers left running; `only_agent_deployments: true` lists every one an agent started. See Filter Deployments.
`edgegap_get_deployment_logs`	Reads container logs and crash details while the deployment runs. After it stops, logs are only kept if Endpoint Storage was set up.
`edgegap_stop_deployment` ●	Stops one deployment, by its exact request ID. No bulk stop.

Tool	What it does
`edgegap_build_matchmaker_config`	Generates a matchmaker configuration (teams, team size, optional latency rules and expansions) and checks that the version it deploys exists. Set `allowed_cors_origins` for browser (WebGL) clients. Upload the result in the dashboard to create your matchmaker, which starts a dedicated server for each match.

Tool	What it does
`edgegap_create_relay_session` ●	Creates a relay session for your players and returns the relay address and each player's authorization token.
`edgegap_get_relay_session`	Reads a relay session.
`edgegap_authorize_relay_user` ●	Adds a player who joins later.
`edgegap_delete_relay_session` ●	Closes a relay session.

Guardrail	What it does
Dry run	Every tool that changes something takes `dry_run: true`: it returns the exact method, host, path and body, with the token, registry tokens and env values masked, and sends nothing. Local checks still run.
No token in containers	A deploy or version is refused, with nothing sent, if your API token appears in an env var name or value, a tag, or a webhook URL. Env values are never echoed back.
Agent tag	Every deployment gets the `edgegap-mcp` tag, even when the agent passes its own tags. `edgegap_list_deployments` with `only_agent_deployments: true` finds them all.
Auto-stop	Every deploy reports when Edgegap will stop it: the version's `max_duration`, capped at `EDGEGAP_MAX_DURATION_MINUTES` (default 60) for versions the agent creates. Edgegap has no per-deployment time limit, so a version made elsewhere can run up to its own limit (1440 minutes by default); the result warns when it is over an hour or unlimited.
No moving image tags	`edgegap_create_app_version` refuses `latest` (any case), an empty tag, or a tag Docker would reject, with nothing sent: Edgegap caches images by tag, so a re-pushed tag can deploy a stale build. Deploying an existing version on `latest` is refused too, and so is asking for registry push commands for `latest`.
Image reference check	A `docker_image` that also holds a registry host, tag or digest (e.g. `registry.edgegap.com/proj/server:v2`) is refused, and the error gives the right `docker_repository` / `docker_image` / `docker_tag` split. `edgegap_validate_server_config` flags the same things.
Deployment cap	`edgegap_deploy` is refused while `EDGEGAP_MAX_AGENT_DEPLOYMENTS` (default 5) deployments tagged `edgegap-mcp` are already running, so a looping agent cannot pile up billing servers. The refusal says how to list and stop them.
Hidden secret env vars	Env vars whose names look like secrets (`TOKEN`, `SECRET`, `PASSWORD`, `API_KEY`, `CREDENTIAL`, `AUTH`…) are sent with `is_hidden`, so the dashboard does not show their values in plain text.
Strict stop	`edgegap_stop_deployment` stops one deployment by its exact request ID. Empty IDs, wildcards and lists are refused. There is no bulk stop.
Host on every result	Every result starts with the API host, e.g. `[api.edgegap.com]`, or `[custom · host]` when `EDGEGAP_BASE_URL` points elsewhere. A base URL naming `api.edgegap.com` must be exactly `https://api.edgegap.com`, or the server refuses to start.
Redaction	The token is stripped from every error before it reaches the agent.

Guardrail

What it does

Dry run

Every tool that changes something takes dry_run: true: it returns the exact method, host, path and body, with the token, registry tokens and env values masked, and sends nothing. Local checks still run.

No token in containers

A deploy or version is refused, with nothing sent, if your API token appears in an env var name or value, a tag, or a webhook URL. Env values are never echoed back.

Agent tag

Every deployment gets the edgegap-mcp tag, even when the agent passes its own tags. edgegap_list_deployments with only_agent_deployments: true finds them all.

Auto-stop

Every deploy reports when Edgegap will stop it: the version's max_duration, capped at EDGEGAP_MAX_DURATION_MINUTES (default 60) for versions the agent creates. Edgegap has no per-deployment time limit, so a version made elsewhere can run up to its own limit (1440 minutes by default); the result warns when it is over an hour or unlimited.

No moving image tags

edgegap_create_app_version refuses latest (any case), an empty tag, or a tag Docker would reject, with nothing sent: Edgegap caches images by tag, so a re-pushed tag can deploy a stale build. Deploying an existing version on latest is refused too, and so is asking for registry push commands for latest.

Image reference check

A docker_image that also holds a registry host, tag or digest (e.g. registry.edgegap.com/proj/server:v2) is refused, and the error gives the right docker_repository / docker_image / docker_tag split. edgegap_validate_server_config flags the same things.

Deployment cap

edgegap_deploy is refused while EDGEGAP_MAX_AGENT_DEPLOYMENTS (default 5) deployments tagged edgegap-mcp are already running, so a looping agent cannot pile up billing servers. The refusal says how to list and stop them.

Hidden secret env vars

Env vars whose names look like secrets (TOKEN, SECRET, PASSWORD, API_KEY, CREDENTIAL, AUTH…) are sent with is_hidden, so the dashboard does not show their values in plain text.

Strict stop

edgegap_stop_deployment stops one deployment by its exact request ID. Empty IDs, wildcards and lists are refused. There is no bulk stop.

Host on every result

Every result starts with the API host, e.g. [api.edgegap.com], or [custom · host] when EDGEGAP_BASE_URL points elsewhere. A base URL naming api.edgegap.com must be exactly https://api.edgegap.com, or the server refuses to start.

Redaction

The token is stripped from every error before it reaches the agent.

Test	Covers
`test/package.mjs`	Packaging: one `bin`, runtime dependencies, versions in step
`test/skills.mjs`	Skills over MCP: tools, prompts, resources, path safety, bundle matches the pin
`test/smoke.mjs`	Handshake, tool registration, read-only mode
`test/guards.mjs`	Local validation and allowlist enforcement
`test/elicit.mjs`	Token prompt: accept, refuse acknowledgement, decline, no support
`test/newtools.mjs`	Validator, Dockerfile generator, registry, deployments, relay and matchmaker tools against a local mock API
`test/http.mjs`	Self-hosted HTTP server: discovery without a token, per-request tokens, foreign credentials
`test/live-check.mjs`	Not in `npm test`. Runs against the real API with a token from a non-production organization

เพิ่มเซิร์ฟเวอร์นี้

Host a copy with our keys and logs.

ข้อมูลเซิร์ฟเวอร์

เอกสารประกอบ

Edgegap MCP Server

👉 Supported Features

⚖️ Dedicated Servers or Relays?

🚀 Installation

Popular Agents

Claude Code

ChatGPT Codex

Claude Desktop and claude.ai

mcp.json

Custom Integration

Local Server

📚 Skills

🧰 Tools

Before Your First Deployment

Dedicated Servers (Recommended)

Matchmaking

Relays (Host-Client Games Only)

Example Prompts

🛡️ Guardrails

🚨 Troubleshooting

401 Unauthorized

403 Forbidden

424 Image Could Not Be Pulled

Registry Credentials Unavailable

Server Starts Locally but Not on Edgegap

Other API Errors

🛠️ Self-Hosting

Development

Edgegap

เครื่องมือ

คำถาม

ติดตั้ง Edgegap อย่างไร?

Edgegap ต้องใช้ API key ไหม?

Edgegap ใช้ทรานสปอร์ตแบบใด?

Edgegap ถูกตรวจสอบล่าสุดเมื่อใด?