---
title: "MCP server"
description: "The official Edge Network MCP server, local via npx or hosted at edge.network/mcp: 22 tools for deploying and managing infrastructure from any MCP client."
url: "https://edge.network/docs/agent/mcp"
section: "Agent tooling"
---

# MCP server

Edge ships an official Model Context Protocol server. Any MCP client (Cursor, Windsurf, Claude Desktop, Grok Bot, Continue, or your own agent) gets 22 native tools for deploying and managing Edge infrastructure.

The server speaks the [Model Context Protocol](https://modelcontextprotocol.io), so it works with any MCP-compatible client.

## Quick start

Add one entry to your client's MCP config. No account, no API key, nothing else to install:

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

With no access code set, the server signs itself up for a free [explore-tier account](/docs/agent/self-signup) on first run and stores the credentials in `~/.edge/agent.json`. For per-tool setup (Cursor, Windsurf, Claude Desktop, Grok Bot, Continue, Aider), see [Connect your tool](/docs/agent/connect).

## Local or remote

The same tool set is available over two transports. Pick whichever suits where your agent runs:

- **Local (stdio):** `npx @edge-network/mcp`: a zero-dependency bridge for editors and desktop clients. Handles credentials and auto-signup, then proxies JSON-RPC to the hosted endpoint. Best for Cursor, Windsurf, Claude Desktop and Continue.
- **Remote (streamable HTTP):** `https://edge.network/mcp`: a stateless JSON-RPC endpoint. No process to run; `POST` messages directly with your access code as a bearer token. Best for Grok Bot and other cloud agents, serverless functions and custom clients.

```http
POST https://edge.network/mcp
Content-Type: application/json
Authorization: Bearer ea_live_...

{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }
```

Supported methods: `initialize`, `ping`, `tools/list` and `tools/call`. The server is stateless, with no sessions and no server-initiated streams, so every request stands alone.

## Authentication

| Request | Auth required |
|---|---|
| `tools/list`, `initialize`, `ping` | None. Tool definitions are public so clients can list them before connecting an account |
| `tools/call` | `Authorization: Bearer ea_live_...` with an [agent access code](/docs/agent/access-codes), either created in the dashboard or self-provisioned |

Every tool call is dispatched through the same Agent API routes as direct HTTP requests, so access-code scopes, budget caps, free-tier limits, rate limits and audit logging all apply identically. MCP adds no separate permission surface.

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

For the local bridge, pass your code via the `EDGE_AGENT_CODE` environment variable, or omit it for auto-signup.

## The explore tier

Auto-signup accounts run in the explore tier: free-tier resources work for real (static site deploys, storage buckets, DNS zones, Shield widgets, Assist sites), while anything billable is blocked by a hard $0 budget cap. Billable actions still support `dry_run`, so an agent can price a VM deployment without being able to execute it.

To enable billing (and stop the ~7-day auto-purge of unclaimed accounts), the agent calls `edge_request_claim` with the operator's email. Claiming links the account to a human. Details in [Agent self-signup](/docs/agent/self-signup).

## The tools

22 tools covering composite deploys (`edge_deploy_static_site` creates storage + CDN + SSL + DNS in one call), projects, compute, storage, DNS, Shield, Assist and account status. Billable tools are flagged in their descriptions and support dry-run previews with cost estimates. See the [full tool reference with parameters](/docs/agent/mcp-tools).

## Next steps

- [Connect your tool](/docs/agent/connect) — Per-editor configs for Cursor, Windsurf, Claude, Continue, Aider
- [MCP tool reference](/docs/agent/mcp-tools) — All 22 tools with parameters and descriptions
- [Framework wrappers](/docs/agent/frameworks) — LangChain, LlamaIndex, CrewAI and Vercel AI SDK packages
- [Agent self-signup](/docs/agent/self-signup) — How auto-signup and account claiming work
