--- name: edge version: 0.5.0 license: MIT description: >- Setup guide for Edge, an MCP server that finds a fitting public agent skill for a task. Covers Claude Code, Codex, Cursor and the Claude app, the Free and Pro plans, what data it sends, and how to remove it. --- # Edge setup guide This file is a setup guide, not a skill to install. It explains how to add Edge to an agent and what that changes. Edge is an MCP server from getedge.cc. When a task needs specialist know-how (a slide deck, a security review, a data analysis), it searches over 100,000 public agent skills, withholds skills that fail its security checks, and loads the best fit's instructions for that task. Loading is read-only: the instructions apply to that task only, as text your agent reads and then follows or ignores, and nothing is installed. This guide is published under the MIT license with the `@getedge/mcp` npm package: https://www.npmjs.com/package/@getedge/mcp. Setting up Edge on Claude Code, at a glance: - Adds one MCP server entry named `edge` (`claude mcp add`), which runs the `@getedge/mcp` npm package with `npx`. - Recommended, with `npx -y @getedge/mcp setup claude`: a prompt hook and one marked line in your own `~/.claude/CLAUDE.md`. Both apply to every project. - Each search sends the task sentence to getedge.cc, as listed under "Data". File contents, paths and conversation history are not sent. - Every change has a removal command at the end of this guide. ## Plans - **Free:** no account and no key. Unlimited searches with task-fit ranking, and loading a skill for the current task. - **Pro:** $99 per month (https://getedge.cc/pricing/), as a key that starts with `edge_`. Same search, plus an optional comparison with the skills already installed on your machine (only after you opt in), and your ratings count under your key. The key is set as the `EDGE_KEY` environment variable of the `edge` entry. ## Your plan Edge is added only when you agree to it. The Free plan needs no key, so setup does not wait for one. If you have a Pro key (it starts with `edge_`), give it when you agree; a key can also be added later. Setup ends by saying which plan is in use. ## Claude Code Free, for all your projects, as the Edge plugin: ```bash claude plugin marketplace add getedgehq/edge-plugins claude plugin install edge@getedge npx -y @getedge/mcp setup claude ``` The plugin is public at https://github.com/getedgehq/edge-plugins. It adds the hosted Edge connector (`https://getedge.cc/mcp`), a short `edge` skill that tells Claude when to call it, and a prompt hook that asks Claude to check Edge before specialist work. The hook runs locally and sends nothing. `claude plugin list` then shows `edge@getedge` as enabled. The third command sees the plugin and adds only one instruction line in your own `~/.claude/CLAUDE.md`, never in a project's files, then runs one sample search to show Edge works. It prints what it added and how to remove it. If it fails or you skip it, the plugin works without it. If the plugin cannot be installed (no `claude plugin` command, no access to GitHub, or the install fails), add the npm connector instead: ```bash claude mcp add edge -s user -- npx -y @getedge/mcp npx -y @getedge/mcp setup claude ``` Pro uses the npm connector, the first command with your key: ```bash claude mcp add edge -s user -e EDGE_KEY=edge_YOUR_KEY -- npx -y @getedge/mcp npx -y @getedge/mcp setup claude ``` In the npm route, the first command adds Edge. The second is recommended and changes your user-level Claude Code settings, for every project: it adds the same prompt hook and one marked instruction line in your own `~/.claude/CLAUDE.md`, never in a project's files. It checks that the hook fires, then prints what it added and how to remove it. If you skip it or it fails, Edge still works; Claude just checks it less often. Wait for it to finish before the first chat: it also downloads the package, and a chat opened while the package still downloads misses Edge. If you skip it, run `npx -y @getedge/mcp --version` once instead and wait for the version number. Leave out `-s user` to add the npm connector to the current project only. The commands can be run in a terminal or by your agent after you agree; the npm route needs Node.js 20 or newer. If an `edge` entry already exists, `claude mcp get edge` shows it, and `claude mcp remove edge` clears it before adding it again with a key. Use one route, not both: with the plugin installed, do not also add the npm connector. Edge's tools (`find_skill`, `use_skill`) appear in the next Claude Code session. Setup ends with the plan in use, "Edge is set up on the Free plan" or "Edge is set up on the Pro plan", what was added (the plugin, or the instruction line quoted) and how to remove it, and a note that a new session picks it up. Any task that was in progress continues from there. ## Codex and the ChatGPT desktop app Both read `~/.codex/config.toml`. Add this block to that file exactly as shown (Free): ```toml [mcp_servers.edge] command = "npx" args = ["-y", "@getedge/mcp"] omit_tools_from = ["deferred"] ``` Pro: add one more line inside the block, `env = { EDGE_KEY = "edge_YOUR_KEY" }`. The `omit_tools_from` line exposes Edge's tools directly in clients that defer MCP tools. It is recommended for this setup, rather than required for the MCP connection. Tool discovery depends on your client and configuration. If an `[mcp_servers.edge]` block already exists, replace it with this one and read the file back to check the block. Also put `mcp_optional_startup_grace_ms = 10000` on its own line at the top of the file, above the first `[section]` (if that line exists, set it to 10000). Codex otherwise waits only 1 second for MCP servers that are still starting when the first message is sent, and an `npx` start takes longer, so the first chat misses Edge. Then run `npx -y @getedge/mcp --version` once and wait for the version number before the first chat. Edge's tools appear in the next Codex or ChatGPT chat. Setup ends with the plan in use, "Edge is set up on the Free plan" or "Edge is set up on the Pro plan", and a note that a new chat picks it up. In a chat, "Edge" means these Edge skills, not the Microsoft Edge browser. ## Other clients - **Cursor:** in `~/.cursor/mcp.json`: `{ "mcpServers": { "edge": { "command": "npx", "args": ["-y", "@getedge/mcp"], "env": { "EDGE_KEY": "edge_YOUR_KEY" } } } }` (leave out `env` for Free), then `npx -y @getedge/mcp --version` once. - **Claude app** (claude.ai or desktop): Settings, Connectors, Add custom connector, URL `https://getedge.cc/mcp`. Pro: header `Authorization: Bearer edge_YOUR_KEY`, or the URL `https://getedge.cc/mcp?key=edge_YOUR_KEY` where there is no header field. ## Claude app: optional instruction If you want Claude to reach for Edge on specialist work, you can paste this line into Claude Settings > Instructions for Claude yourself. The same line has a copy button at https://getedge.cc/docs/setup/ (Claude app tab). ```text Before specialist work, call Edge's find_skill. ``` ## Referral codes If you came from a link with `?ref=CODE`, set `EDGE_REF=CODE` in every host's Edge MCP environment. Claude Code also accepts `npx -y @getedge/mcp setup claude --ref CODE`. The code is stored locally and sent with later calls. ## Data | | What and how long | |---|---| | Edge receives | The task sentence the agent writes (up to 300 characters) and optional keywords, a random install ID (`~/.config/edge/install-id`) or session ID (in ChatGPT, a one-way hash of ChatGPT's anonymous user ID, so one person counts once), the Pro key if set, and the client name and version. Ratings and issue reports when the agent sends them. | | Edge stores | All of that, with the skills shown and loaded. Search text has no scheduled expiry: 31 days in daily files, then a compressed archive. Backups are encrypted. | | Never receives | File contents, paths, repository names and conversation history are not sent. | | Who else sees it | To rank candidates, TypeSafe (api.typesafe.ai), under Edge's own service key, gets the task sentence and candidate skill descriptions, with no install ID or key. | | How to delete | `npx -y @getedge/mcp@0.6.14 forget` deletes this install's records (with `EDGE_KEY` set, the key's too) and prints the counts. Or email fede@getedge.cc. | Details: https://getedge.cc/privacy/ ## Remove Claude Code plugin: `npx -y @getedge/mcp setup claude --remove` (the instruction line), `claude plugin uninstall edge@getedge`, then `claude plugin marketplace remove getedge`. npm connector: `npx -y @getedge/mcp setup claude --remove` (Claude Code: the hook and the instruction line), `claude mcp remove edge` (Codex: `codex mcp remove edge`), then `rm -rf ~/.config/edge`. Removing Edge deletes nothing stored on the server; `forget` does.