Cloud Services

edge.network

Manages Edge cloud deployments, enabling users to deploy static sites and applications, update deployments, and view project resources.

1 endpoint22 known toolsFirst detected August 23, 2026Last detected August 23, 2026

ENDPOINT 1

https://edge.network/mcp

No auth detected

MCP server metadata

Name: edge-network
Version: 1.0.0

Capabilities

tools

Server instructions

You can provision and manage real cloud infrastructure on Edge Network (https://edge.network) — CDN, compute VMs, object storage, DNS, Shield bot protection, and Assist AI answers — through a REST API designed for agents. ## Connecting - Base URL: https://edge.network/agent - Authenticate every request with: Authorization: Bearer ea_live_... - No access code? Create your own account autonomously: GET https://edge.network/agent/signup describes the flow (Ed25519 keypair + small proof-of-work, no human required). You get a free explore-tier account that can deploy free-tier resources immediately. - Start every session with GET /agent — the discovery endpoint returns your account, budget, enabled products, current projects, and full endpoint documentation. Never guess endpoints; discovery is the source of truth. ## Working safely - Plan before you act: any POST/PATCH/DELETE accepts the header "X-Dry-Run: true" and returns what would happen, including cost estimates, without changing anything. Always dry-run first for anything that costs money. - Use an "Idempotency-Key" header on POST requests so retries are safe. - Respect the budget: discovery shows the monthly budget cap on your access code. Before creating billable resources (VMs), check the cost with a dry run and stay within budget. Report expected monthly costs to the user before and after provisioning. - Deleting things is permanent. Project teardown requires the "X-Confirm: teardown" header — only use it when the user has clearly asked. ## Talking to your human - Every API response includes a "tell_user" field: a plain-English summary written to be relayed to the user. Prefer relaying or paraphrasing it over inventing your own summary. - If your account is in the explore tier (self-signup, unclaimed), you can build free-tier things for real — static sites, Shield widgets, DNS zones, storage buckets, Assist sites — but paid resources are dry-run only. To unlock them, ask the user for their email address and POST it to /agent/signup/bind-email; they receive a claim link. Unclaimed accounts are deleted after ~7 days, so encourage claiming anything worth keeping. ## Typical first task Deploying a static site is one call: POST /agent/deploy/static-site with a project name and files (base64) or a git repo. Edge creates the storage bucket, uploads files, configures the CDN with SSL, and wires DNS if the zone is on Edge. The free tier covers it.

Known tools 22

edge_discover

Get everything about the connected Edge account: plan, budget, enabled products with limits and regions, current projects, and full API documentation.

Inferred read-only

edge_deploy_static_site

Deploy a static website to Edge in one call: creates a storage bucket, uploads files (or clones a git repo), configures the global CDN with SSL, and wires DNS if the zone is on Edge.

Inferred read-only

edge_deploy_app

Deploy a full application on a VM: provisions compute, runs a setup script, and optionally adds CDN and DNS.

Inferred read-only

edge_update_deployment

Update an existing deployment: upload changed files and optionally purge the CDN cache.

Potential side effects

edge_list_projects

List all projects (groupings of resources) on the connected Edge account.

Inferred read-only

edge_project_health

Comprehensive health check for every resource in a project: status, metrics, and actionable suggestions.

Inferred read-only

edge_scale_project

Scale the compute resources in a project up or down.

Inferred read-only

edge_teardown_project

PERMANENTLY delete a project and every resource in it (VMs, buckets, CDN deployments, DNS zones).

Potential side effects

edge_list_vms

List all virtual machines on the account with status, size, and IPs.

Inferred read-only

edge_get_vm

Get one VM: live status, metrics, IPs, attached SSH keys, and the ready-to-use SSH command.

Potential side effects

edge_list_buckets

List storage buckets on the account.

Inferred read-only

edge_create_bucket

Create an object storage bucket (S3-compatible).

Potential side effects

edge_upload_files

Upload files to an existing storage bucket.

Potential side effects

edge_list_dns_zones

List DNS zones on the account.

Inferred read-only

edge_create_dns_zone

Create a DNS zone for a domain on Edge authoritative DNS.

Potential side effects

edge_add_dns_record

Add a DNS record to a zone.

Inferred read-only

edge_list_shield_widgets

List Edge Shield widgets (free, privacy-first CAPTCHA alternative).

Inferred read-only

edge_create_shield_widget

Create an Edge Shield widget to protect a form or page from bots.

Potential side effects

edge_list_assist_sites

List Edge Assist sites (AI answers widget) with usage and index status.

Inferred read-only

edge_create_assist_site

Create an Edge Assist site: AI answers for a website, grounded in its own content.

Potential side effects

edge_account_status

Check whether the connected account is a self-signed-up guest (explore tier) or fully claimed, and how to unlock it.

Inferred read-only

edge_request_claim

Nominate the human operator of a self-signed-up (explore tier) account.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.edge-network]
url = "https://edge.network/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "edge-network": {
      "type": "http",
      "url": "https://edge.network/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: edge-network
Remote MCP URL: https://edge.network/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "edge-network": {
      "url": "https://edge.network/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "edge-network": {
      "type": "http",
      "url": "https://edge.network/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "edge-network",
  "transport": "streamable-http",
  "url": "https://edge.network/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.