---
title: "Connect Your Tool"
description: "Ready-to-paste Edge configs for Cursor, Windsurf, Claude Desktop, Continue, Aider, LangChain, LlamaIndex, CrewAI, and the Vercel AI SDK."
url: https://edge.network/docs/agent/connect/
---

# Connect Your Tool

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. For how the server
works (transports, auth, explore tier), see [MCP Server](https://edge.network/docs/agent/mcp);
for what your agent can do once connected, see the
[tool reference](https://edge.network/docs/agent/mcp-tools).

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](https://edge.network/docs/agent/self-signup) 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](https://control.edge.network/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 Windsurf Claude Desktop Continue Aider LangChain LlamaIndex CrewAI Vercel AI SDK Remote MCP Raw API
.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" }
    }
  }
}
```

Copy

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

~/.codeium/windsurf/mcp_config.json

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

Copy

Try it: Deploy this project as a static site on Edge.

claude_desktop_config.json (Settings → Developer → Edit Config)

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

Copy

Try it: Create a DNS zone for example.com on Edge and list its nameservers.

.continue/config.yaml

```
mcpServers:
  - name: Edge Network
    command: npx
    args: ["-y", "@edge-network/mcp"]
    env:
      EDGE_AGENT_CODE: ea_live_YOUR_CODE_HERE
```

Copy

Try it: Add bot protection to my contact form using Edge Shield.

Terminal — Aider has no MCP support, so it reads Edge instructions from a conventions file

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

Copy

Try it: Using the Edge API described in CONVENTIONS.md (auth via $EDGE_AGENT_CODE), deploy ./dist as a static site.

pip install "edge-network-agent[langchain]"

```
from edge_network_agent import EdgeAgentTools

edge = EdgeAgentTools(agent_code="ea_live_YOUR_CODE_HERE")
tools = edge.langchain_tools()
system_prompt = edge.starter_prompt()
```

Copy

Try it: agent.invoke({"input": "Deploy my React build to portfolio.example.com"})

pip install "edge-network-agent[llamaindex]"

```
from edge_network_agent import EdgeAgentTools
from llama_index.core.agent import ReActAgent

edge = EdgeAgentTools(agent_code="ea_live_YOUR_CODE_HERE")
agent = ReActAgent.from_tools(edge.llamaindex_tools(), llm=llm)
```

Copy

Try it: agent.chat("Create a storage bucket called assets and upload ./images to it")

pip install "edge-network-agent[crewai]"

```
from edge_network_agent import EdgeAgentTools
from crewai import Agent

edge = EdgeAgentTools(agent_code="ea_live_YOUR_CODE_HERE")

deployer = Agent(
    role="Infrastructure Engineer",
    goal="Deploy and monitor applications on Edge Network",
    tools=edge.crewai_tools(),
)
```

Copy

Try it: Task: "Deploy the marketing site and verify it responds with a 200"

npm install @edge-network/ai-tools ai

```
import { generateText } from 'ai'
import { createEdgeTools, fetchStarterPrompt } from '@edge-network/ai-tools'

const edgeTools = await createEdgeTools({ agentCode: 'ea_live_YOUR_CODE_HERE' })

const result = await generateText({
  model,
  system: await fetchStarterPrompt(),
  tools: edgeTools,
  prompt: 'Deploy the ./dist folder to my-site.example.com',
})
```

Copy

Try it: prompt: 'Deploy the ./dist folder to my-site.example.com'

For clients that support remote MCP servers — nothing to install

```
{
  "mcpServers": {
    "edge": {
      "url": "https://edge.network/mcp",
      "headers": { "Authorization": "Bearer ea_live_YOUR_CODE_HERE" }
    }
  }
}
```

Copy

Try it: Works with any MCP client that supports streamable-HTTP servers.

Any HTTP client — the API is self-describing

```
curl https://edge.network/agent \
  -H "Authorization: Bearer ea_live_YOUR_CODE_HERE"
```

Copy

Try it: The discovery response documents every endpoint. Add "X-Dry-Run: true" to any mutation to preview it with a cost estimate.

## 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 →](https://edge.network/docs/agent/discovery) [Deploy static site →](https://edge.network/docs/agent/deploy-static-site) [Self-signup →](https://edge.network/docs/agent/self-signup)
[Back to Docs](https://edge.network/docs) [Need help?](https://edge.network/support)