Edgegap MCP Server

Official

by edgegap

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Build a basic matchmaker configuration

edgegap_build_matchmaker_config

Read-onlyIdempotent

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 longer a player waits.

Instructions

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 longer a player waits. Checks the referenced application version exists and has ports. Edgegap has no API for creating a matchmaker, so this tool does NOT create one: save the returned config to a file (e.g. matchmaker-config.json) and have the developer upload it on the Matchmaker page of the dashboard. The matchmaker starts an authoritative dedicated server for each match, which is the recommended setup for multiplayer games.

Input Schema

TableJSON Schema

Name	Required	Description
`inspect`	No	Expose the inspection API for debugging. Default true; turn off for production.
`version`	Yes	Version the matchmaker deploys.
`expansions`	No	Rule relaxations after a player has waited this long, e.g. [{after_seconds: 30, min_team_size: 1}].
`team_count`	Yes	Teams per match. 1 for free-for-all or co-op.
`application`	Yes	Application the matchmaker deploys.
`profile_name`	Yes	Profile clients will queue into, e.g. "casual-2v2".
`max_team_size`	Yes
`min_team_size`	Yes
`max_latency_ms`	No	Adds a latency rule: drop players above this ping to the chosen region. Needs beacon pings from the client.
`verify_version`	No	Look up the application version first. Default true.
`ticket_expiration`	No	Default "5m".
`allowed_cors_origins`	No	Origins of web pages allowed to call the matchmaker, e.g. ["https://mygame.example.com", "http://localhost:8080"]. Required when game clients run in a browser (WebGL): browsers block matchmaker calls from any origin not listed. Scheme and host only, no path.
`latency_difference_ms`	No	Max ping spread between matched players. Default 100.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.2Oct 14, 2026

addedInput schema / properties / allowed_cors_origins

Added value: +{
+  "description": "Origins of web pages allowed to call the matchmaker, e.g. [\"https://mygame.example.com\", \"http://localhost:8080\"]. Required when game clients run in a browser (WebGL): browsers block matchmaker calls from any origin not listed. Scheme and host only, no path.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Addedv0.2.0Oct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already signal read-only/idempotent, which is consistent with a generator. The description adds real behavioral detail beyond annotations: it performs a lookup that verifies the referenced application version exists and has ports, and it explicitly clarifies that no server-side object is created and the developer must upload the config manually. It does not cover the inspect/verify_version toggles or failure modes when verification fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the concrete artifact and its contents, then the critical caveat about manual upload. Four sentences all carry weight, though the closing sentence about authoritative dedicated servers is more recommendation than instruction and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter generator with no output schema, the description explains what is produced, what is verified, and what to do with the result. It does not describe the shape of the returned JSON beyond 'config', but the schema and the tool's generative nature make that a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 85%, so the baseline is 3, but the description adds conceptual meaning the schema lacks: expansions are described as time-based rule relaxations ('relax the rules the longer a player waits'), and the latency rule is tied to the profiles's matching behavior. The two undocumented team-size parameters are only generically covered as 'team size'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and artifact: generate a ready-to-upload Edgegap matchmaker JSON configuration, plus the exact contents (team count/size, optional latency rule, optional expansions). No sibling tool produces matchmaker configs, and the description makes that boundary obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-to-use context and an explicit when-not: 'Edgegap has no API for creating a matchmaker, so this tool does NOT create one.' It also prescribes the follow-up workflow (save to file, upload manually on the dashboard). It stops short of pointing to any alternative or prerequisite sibling tools (e.g. app-version lookup tools), so not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Build a basic matchmaker configuration

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools