Agent Tooling

Connect Your Tool

Ready-to-paste configs for every popular agent tool. Replace ea_live_YOUR_CODE_HERE with your access code — or skip the code entirely and let the MCP server sign itself up.

No account yet? You don't need one.

Omit EDGE_AGENT_CODE and the MCP server creates a free explore-tier Edge account on first run — no card, no human in the loop. It can deploy free-tier resources (static sites, DNS zones, Shield widgets, storage buckets) immediately. Set EDGE_OPERATOR_EMAIL to receive the claim link that unlocks paid resources. Agents talking straight to the API can sign themselves up the same way.

{
  "mcpServers": {
    "edge": { "command": "npx", "args": ["-y", "@edge-network/mcp"] }
  }
}

Getting an access code

Create one in the Edge control panel under Account → Agent Access — you choose which products it can touch, its permissions, and an optional monthly budget cap (soft or hard). The panel generates all of the configs below with your real code injected.

Pick your tool

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global)

{
  "mcpServers": {
    "edge": {
      "command": "npx",
      "args": ["-y", "@edge-network/mcp"],
      "env": { "EDGE_AGENT_CODE": "ea_live_YOUR_CODE_HERE" }
    }
  }
}

Try it: Deploy this folder as a static site on Edge and give me the URL.

Aider conventions file

Aider doesn't speak MCP, but it excels at following a conventions file. The Edge starter system prompt — what Edge offers, how to authenticate, dry-run discipline, the tell_user convention, and the claim flow — is served as plain markdown, so the conventions file is one curl away:

curl -s "https://edge.network/agent/prompt?format=text" -o CONVENTIONS.md
aider --read CONVENTIONS.md

Keep the access code out of the file: export it as EDGE_AGENT_CODE and tell Aider to use $EDGE_AGENT_CODE in its curl commands. The prompt is versioned — re-run the curl occasionally to pick up improvements.

What your agent gets

All integrations expose the same tool set, served live from the API (so they never go stale): deploy static sites and full VM-backed apps, manage projects (health, scale, teardown), storage buckets and uploads, DNS zones and records, Shield bot-protection widgets, and Assist AI-answer sites — plus discovery, cost-estimating dry runs, and the account claim flow.

Discovery endpoint → Deploy static site → Self-signup →