Edgegap MCP Server

Official

by edgegap

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List running deployments

edgegap_list_deployments

Read-only

Lists active deployments with optional filters and sorting to find orphaned servers left running from earlier sessions before starting new ones, helping avoid unnecessary costs.

Instructions

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. Filter by status, application, version, tags, request_id, created_at, fleet_name or host_name, e.g. [{field:"application",operator:"eq",value:"my-game"},{field:"status",operator:"eq",value:"ready"}]. Operators: eq and neq on every field except created_at (eq, gte, lte); in and nin with an array value on request_id, tags, application, version, fleet_name, host_name; ilike with % wildcards on fleet_name and host_name. At most one filter per field. Sort by created_at or available_session_sockets. To find every deployment an agent started through this server, pass only_agent_deployments: true (the same as filtering tags in ["edgegap-mcp", "mcp"]).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "edgegap_list_deployments"
  }
}

Input Schema

Name	Required	Description
`limit`	No	1-100. Default 50.
`filters`	No	Omit for all deployments.
`order_by`	No	e.g. [{field:"created_at",order:"asc"}] for oldest first.
`only_agent_deployments`	No	Only deployments started through this server: tagged "edgegap-mcp", or "mcp" by versions up to 0.3.3. Cannot be combined with a tags filter.

Output Schema

Name	Required	Description	Default
`total`	No
`showing`	No
`next_step`	No
`truncated`	No
`deployments`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.12.0Oct 27, 2026

changedInput schema / properties / limit / description

Previous value: -"Default 50."New value: +"1-100. Default 50."

changedInput schema / properties / limit / maximum

Previous value: -100New value: +9007199254740991

changedInput schema / properties / limit / minimum

Previous value: -1New value: +-9007199254740991

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "deployments": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "fqdn": {
+            "type": "string"
+          },
+          "ready": {
+            "type": "boolean"
+          },
+          "request_id": {
+            "type": "string"
+          },
+          "started": {
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "showing": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedv0.5.2Oct 14, 2026

addedInput schema / properties / only_agent_deployments

Added value: +{
+  "description": "Only deployments started through this server: tagged \"edgegap-mcp\", or \"mcp\" by versions up to 0.3.3. Cannot be combined with a tags filter.",
+  "type": "boolean"
+}

Changed3 schema fields changedv0.2.2Oct 2, 2026

removedInput schema / properties / filter

Removed value: -{
-  "description": "Edgegap filter expression, e.g. by tag. Omit for all deployments.",
-  "type": "string"
-}

addedInput schema / properties / filters

Added value: +{
+  "description": "Omit for all deployments.",
+  "items": {
+    "properties": {
+      "field": {
+        "enum": [
+          "status",
+          "request_id",
+          "tags",
+          "created_at",
+          "application",
+          "version",
+          "fleet_name",
+          "host_name"
+        ],
+        "type": "string"
+      },
+      "operator": {
+        "enum": [
+          "eq",
+          "neq",
+          "in",
+          "nin",
+          "gte",
+          "lte",
+          "ilike"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        ],
+        "description": "A string, or an array of strings for in/nin. created_at is ISO 8601, e.g. \"2026-09-30T00:00:00Z\"."
+      }
+    },
+    "required": [
+      "field",
+      "operator",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / order_by

Added value: +{
+  "description": "e.g. [{field:\"created_at\",order:\"asc\"}] for oldest first.",
+  "items": {
+    "properties": {
+      "field": {
+        "enum": [
+          "created_at",
+          "available_session_sockets"
+        ],
+        "type": "string"
+      },
+      "order": {
+        "enum": [
+          "asc",
+          "desc"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "field",
+      "order"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedv0.1.2Sep 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: the cost/orphan risk and the equivalence of only_agent_deployments to a tags filter (with a note about versions up to 0.3.3). It could still say more about pagination limits beyond the schema, but this is strong.

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?

Purpose and when-to-use are front-loaded, and every sentence carries constraint information. It is dense and the operator rules run long, but little is wasted. Slightly sprawling for a single paragraph.

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

Completeness5/5

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

An output schema exists, so return values need not be explained. All four parameters, their interactions, and the usage context are covered adequately. Nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but the description adds substantial meaning the schema does not: which operators apply per field, ilike only on fleet_name/host_name, in/nin requiring array values, created_at restricted to eq/gte/lte, and the one-filter-per-field constraint. This is genuinely additive.

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 resource (list active deployments) plus scoping (optionally filtered and sorted). An agent can immediately distinguish this from edgegap_get_deployment (single) and edgegap_deploy (create). The scope is precise.

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

Usage Guidelines5/5

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

Explicitly names the use case: find deployments left running from earlier sessions before starting new ones, warning that orphaned servers cost money. It also gives a targeted mode (only_agent_deployments) for agent-started deployments, effectively directing the agent when to use which variant.

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

Deploy Server