Connect Edgein about a minute.

Claude Code from the terminal

The pasted prompt runs this for you. To run it yourself:

npx -y @getedge/mcp@0.6.56 setup claude

Start a new session.

It adds the Edge connector for all your projects, as Node running a copy of this exact release in ~/.edge/mcp, so no npm process stays open next to each session. It also adds a prompt hook, and this one line in your own ~/.claude/CLAUDE.md, between <!-- edge:begin --> and <!-- edge:end -->, never in a project's files: “Before doing specialist work such as slides, documents, design, data analysis, video, security review, or work involving a named framework/API, use Edge's find_skill to check for a relevant public skill. Do not use Edge for routine edits or tasks where no specialist skill is relevant.” It runs one sample search, and prints all of this before it changes anything. Undo it with npx -y @getedge/mcp@0.6.56 setup claude --remove. It needs Node.js 20 or newer. The npm commands pin the exact release.

No Node.js 20? Install the Edge plugin instead: the hosted connector, a short skill that tells Claude when to use Edge, and a prompt hook. Use one route, not both. The plugin is public at github.com/getedgehq/edge-plugins.

claude plugin marketplace add getedgehq/edge-plugins
claude plugin install edge@getedge

Start a new session. claude plugin list then shows edge@getedge as enabled.

Or connect the hosted connector directly, with nothing installed (Pro: add --header "Authorization: Bearer edge_YOUR_KEY"). Details in the Claude Code guide.

claude mcp add --transport http -s user edge https://getedge.cc/mcp

Codex and ChatGPT desktop from npm

One command, Free or Pro. No Node.js 20? Use codex plugin add edge@openai-curated-remote instead.

npx -y @getedge/mcp@0.6.56 setup codex

Start a new chat; codex mcp get edge shows the entry. In the ChatGPT desktop app, restart it and type /mcp in a new chat to see Edge listed.

The command adds the Edge entry to ~/.codex/config.toml with Edge’s tools exposed directly, puts mcp_optional_startup_grace_ms = 10000 at the top of the file so the first chat waits for Edge to start, and downloads the package. Your other settings stay as they are. Undo it with npx -y @getedge/mcp@0.6.56 setup codex --remove. It needs Node.js 20 or newer. Pro: after setup, add EDGE_KEY = "edge_YOUR_KEY" to the [mcp_servers.edge.env] table in that file. The ChatGPT desktop app on your local computer shares the same ~/.codex/config.toml, so the same command sets it up there.

Or by hand: install Edge once with npm install -g @getedge/mcp, then merge this block into ~/.codex/config.toml, replacing any existing Edge block and keeping your other servers, with the first line at the top of the file, above the first [section]. Codex otherwise waits only 1 second for MCP servers that are still starting when the first message is sent, and a first start can take longer, so the first chat misses Edge.

mcp_optional_startup_grace_ms = 10000

[mcp_servers.edge]
command = "edge"
omit_tools_from = ["deferred", "code_mode"]

One command adds Edge to your agent. It needs Node.js 20 or newer, and there is no account and no key to create.

What this changes

• Config: on Claude Code, the Edge plugin under ~/.claude/plugins/ and its entry in ~/.claude/settings.json; elsewhere, or on the npm route, one MCP server entry named edge, which runs Edge’s npm package with Node (setup keeps a copy of the release in ~/.edge/mcp). On Claude Code, setup claude also adds one marked line to your own ~/.claude/CLAUDE.md. No project file or skill folder is written.
• Claude Code npm route, with setup claude: it also pins that entry to the exact release (for example @getedge/mcp@0.6.56), adds a prompt hook (~/.claude/hooks/edge-nudge.mjs and one entry in ~/.claude/settings.json) and the one marked line in ~/.claude/CLAUDE.md shown above. Skip them with --no-hook and --no-instruction.
• One local file: on first start the server creates ~/.config/edge/install-id, a random ID with no hardware, user or path information in it.
• On start: one request to getedge.cc with the connector version, the client name and that random ID.
• On each search: the task description your agent writes, the random ID, a per-session ID, the connector version and the client name go to getedge.cc, which logs the query and searches Edge’s own index of public skills with it. What leaves your machine lists every party that sees it.
• To remove it: claude plugin uninstall edge@getedge for the Claude Code plugin, or npx -y @getedge/mcp@0.6.56 setup claude --remove (the connector, the hook and the line, in one command; Codex: npx -y @getedge/mcp@0.6.56 setup codex --remove, or codex mcp remove edge for an entry added by hand), then rm -rf ~/.config/edge. Removing Edge deletes nothing Edge stored; run npx -y @getedge/mcp@0.6.56 forget first for that.

Or give the link to your agent

Set up Edge for me: fetch https://getedge.cc/SKILL.md with curl, read it, and follow it

The file is short and written for you as much as for the agent. The agent shows you the list above, asks once, and after your yes runs the one command for its host. It writes nothing else and sends nothing before you answer.

Claude Code

The setup prompt above runs npx -y @getedge/mcp@0.6.56 setup claude (what it does). Edge also comes as a Claude Code plugin. To use the plugin instead, run:

claude plugin marketplace add getedgehq/edge-plugins
claude plugin install edge@getedge
npx -y @getedge/mcp@0.6.56 setup claude

The plugin brings the remote connector https://getedge.cc/mcp (its tools show up as mcp__plugin_edge_edge__*), the edge skill and the prompt hook. setup claude sees the plugin, so it adds no second connector or hook. It adds only the instruction line and the sample search. To remove the plugin, run claude plugin uninstall edge@getedge, then claude plugin marketplace remove getedge. The plugin has no field for a key, so Pro uses the hosted connector with a header or the npm connector, both below.

The hosted connector also works on its own, with nothing installed: Claude Code talks to https://getedge.cc/mcp over HTTP. It adds no hook or instruction line and cannot rank your installed skills. Free, then Pro:

claude mcp add --transport http -s user edge https://getedge.cc/mcp
claude mcp add --transport http -s user edge https://getedge.cc/mcp --header "Authorization: Bearer edge_YOUR_KEY"

Run one of the two. claude mcp get edge shows Status: Connected; Edge's health tool reports auth: pro once the key is accepted. More in the Claude Code guide.

The npm connector is the fallback. Install it once, add it, then run setup. The commands pin the exact release:

npm install -g @getedge/mcp@0.6.56
claude mcp add edge -- edge
npx -y @getedge/mcp@0.6.56 setup claude

That uses Claude Code's default scope, this project only. Add -s user to use Edge in every project. Check the entry with claude mcp get edge.

The last command adds a prompt hook that asks Claude to check Edge before specialist work and one marked instruction line in your own ~/.claude/CLAUDE.md. It checks that the hook fires, then prints what it added and how to remove it: npx -y @getedge/mcp@0.6.56 setup claude --remove. If it fails or you skip it, Edge works without these. The connector runs from the installed package, so no download waits at the start of a chat. To update later: npm install -g @getedge/mcp@latest.

With an Edge Pro key, pass it as an environment variable in the same entry:

claude mcp add edge -e EDGE_KEY=your_key -- edge
npx -y @getedge/mcp@0.6.56 setup claude

The project-scoped .mcp.json equivalent:

{
  "mcpServers": {
    "edge": {
      "command": "edge",
      "env": { "EDGE_KEY": "your_key" }
    }
  }
}

Omit EDGE_KEY if you do not have a key: a yes without a key sets up the Free plan right away, with no waiting for a key. Edge without a key is a working product, not a crippled one; see Free and Pro. Keep a key out of any file under version control.

Codex

One command writes the Edge entry, pinned to the release that ran it, the startup wait line and a package warm-up into ~/.codex/config.toml, merging with what is there (setup codex --remove undoes it). $CODEX_HOME selects a different config directory.

npx -y @getedge/mcp@0.6.56 setup codex

By hand: install Edge once with npm install -g @getedge/mcp, then put the [mcp_servers.edge] block in ~/.codex/config.toml, replacing any existing Edge block. The omit_tools_from line exposes Edge’s tools directly: Codex otherwise defers MCP tools behind a tool search (and, from 0.160, code mode), and a deferred find_skill is rarely called.

[mcp_servers.edge]
command = "edge"
omit_tools_from = ["deferred", "code_mode"]

Also put mcp_optional_startup_grace_ms = 10000 on its own line at the top of ~/.codex/config.toml, above the first [section]. Codex otherwise waits only 1 second for MCP servers that are still starting when the first message is sent, and a first start can take longer, so the first chat misses Edge.

mcp_optional_startup_grace_ms = 10000

[mcp_servers.edge]
command = "edge"
omit_tools_from = ["deferred", "code_mode"]

Manual, not recommended: codex mcp add edge -- edge adds the entry without these lines, so Codex usually never sees Edge's tools. If you use it, add the lines above afterwards and check with codex mcp get edge.

With a Pro key, add EDGE_KEY = "your_key" to the [mcp_servers.edge.env] table that setup codex adds; on the manual route, add --env EDGE_KEY=your_key before --. Codex asks for approval the first time it calls a tool from a new MCP server, so expect a prompt on the first find_skill.

Cursor

In ~/.cursor/mcp.json, or .cursor/mcp.json in the project:

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

Claude app (claude.ai and desktop)

Claude Desktop step by step, with your Pro key and a test question: Set up Edge in Claude Desktop.

The Claude app connects to Edge's hosted server, so nothing runs on your machine and Node is not needed. Open Customize, then Connectors, click + Add, choose Add custom connector, and enter:

https://getedge.cc/mcp

There is no sign-in. For Pro, send the key as a request header:

Authorization: Bearer your_key

If a client has no field for headers, https://getedge.cc/mcp?key=your_key also works, but a URL ends up in more logs than a header does, so prefer the header. The hosted server has the catalog tools; local scanning and benchmark require the npm connector. It does not create an install ID.

You have to start a new session

MCP tools bind when a session starts. The session you ran the install command in has already built its tool list, so find_skill is not callable there no matter what the config now says. Start a new session and the tools are there. This is how MCP works, not a sign that anything failed.

The same applies to the key. The connector reads EDGE_KEY once, at startup, from the environment the host gave it. Adding a key, changing it or removing it has no effect until the next session starts.

When your agent uses Edge

Edge helps your agent find specialist steps and checks for a new task when they would add value. The agent can reuse a fitting skill for follow-ups, and skip searches for routine work. A material new phase or diagnosed gap may justify another search, with a budget of at most two searches and two loads per task. You can also ask it to use a skill or to skip Edge. The MCP server supplies this guidance. In Claude Code, setup claude adds the one marked line above as a reminder; Edge works without it.

If an earlier setup saved ~/.claude/skills/edge/ or added an Edge line to CLAUDE.md or AGENTS.md outside the edge:begin markers, the server no longer needs either. Keep or delete them.

Ranking your own skills (optional, off)

Edge does not read or send your installed skills unless you opt in. On the npm connector, setup asks nothing; Edge asks once in chat, after your first result: “Rank your installed skills too? Edge and its ranking provider receive skill names and short descriptions, never skill contents.” The answer is no unless you say yes. Either answer is recorded as on or off in ~/.config/edge/local-skills so it is not asked again, and a yes also records the consent version in ~/.config/edge/local-skills-consent. EDGE_LOCAL_SKILLS=0 in the Edge entry turns it off.

Verify it is working

In a fresh session, ask for something a skill would plausibly help with. The quickest test is whatever you are working on:

Find me a skill for what I'm working on.

A working setup calls edge.find_skill. This first line was captured from the live hosted MCP on 2 October 2026:

3 candidate skills for "review a pull request for correctness bugs", ranked by Edge for this task.

Three other outcomes are all normal rather than broken:

• The agent does not call Edge at all. For a trivial edit, or a task an installed skill already covers well, not calling Edge is the documented correct behaviour.
• No candidates. No candidate skills found for "<query>". Choosing none is valid. is a successful search that found nothing.
• A failure message. Anything starting Edge skill discovery failed: ends with an instruction to continue without Edge, and the agent should carry on with local skills.

A key is optional for task-fit catalog search. The result header reports whether ranking ran; it does not verify a key. With a key, the local-skills comparison is offered only after you opt in.

Setup didn't finish? Edge also works in ChatGPT with no install: Edge Skills in ChatGPT.