Connect Claude Code, Cursor & VS Code

Claude Code, Cursor, and VS Code all speak MCP over Streamable HTTP natively — point them at the EDITED MCP gateway and pass your key as an x-api-key header. No mcp-remote bridge is needed (that's only for stdio-only clients like Claude Desktop).

The connection details are identical across all three; only the config mechanism differs. In every case:

• Endpoint: https://mcp.edited.com/mcp — no trailing slash. The gateway redirects …/mcp/ in a way HTTP clients can't follow, so the connection fails (see Concepts → Transports).
• Auth: an x-api-key header on every request. See Authentication & access for how to get a key and keep it safe. The examples below use YOUR_API_KEY as a placeholder and reference it via an environment variable or secret prompt, so the key never lands in committed config.

Can't get the key to connect?

Some clients don't reliably expand ${env:…} / ${input:…} references. If the server won't connect, paste your key directly in place of the placeholder to confirm everything else is right — then, for any config you commit or share, move it back into an environment variable or secret prompt so the key stays out of version control.

Claude Code

Prerequisites

• The Claude Code CLI installed.

Add the server

claude mcp add --transport http edited-mcp https://mcp.edited.com/mcp \
  --header "x-api-key: YOUR_API_KEY"

The flags:

• --transport http — Streamable HTTP (use stdio for stdio servers)
• edited-mcp — local alias you'll use to refer to the server
• --header "x-api-key: YOUR_API_KEY" — your API key, sent on every request

To install scoped to the project (so the config lives in this repo and ships with collaborators):

claude mcp add --scope project --transport http edited-mcp https://mcp.edited.com/mcp \
  --header "x-api-key: ${EDITED_MCP_API_KEY}"

Where the config lives

• --scope user (default) installs into your global Claude Code config.
• --scope project writes a .mcp.json at the repo root, checked into git. Reference your key via an environment variable (${EDITED_MCP_API_KEY}, as above) rather than pasting it in literally, so the committed .mcp.json stays free of secrets.

Verify

claude mcp list
# edited-mcp: https://mcp.edited.com/mcp (HTTP) - ✓ Connected

Then run claude in any directory and ask it something the server can answer — the tools are picked up automatically. To remove it later: claude mcp remove edited-mcp.

Cursor

Prerequisites

• A recent version of Cursor with MCP support. No Node or bridge needed — Cursor connects over HTTP directly.

Add the server

Add an mcpServers entry to your Cursor MCP config:

{
  "mcpServers": {
    "edited-mcp": {
      "url": "https://mcp.edited.com/mcp",
      "headers": {
        "x-api-key": "${env:EDITED_MCP_API_KEY}"
      }
    }
  }
}

Cursor resolves ${env:…} references in both url and headers, so set EDITED_MCP_API_KEY in your environment rather than pasting the key inline. (To paste it literally instead, replace the value with your key.)

Where the config lives

• Global: ~/.cursor/mcp.json — applies to every project.
• Project: .cursor/mcp.json in the repo root — scoped to that project.

Verify

Open Cursor Settings → MCP. edited-mcp should show as connected, with its tools listed. Then ask something in chat that needs EDITED data and confirm Cursor calls one of the mdmcp-search_* tools.

VS Code

Prerequisites

• A recent version of VS Code with MCP support (Agent mode).

Add the server

Create .vscode/mcp.json. VS Code uses a top-level servers object (note: not mcpServers), requires "type": "http" for remote servers, and can prompt for secrets via an inputs block so the key never lives in the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "edited-api-key",
      "description": "EDITED MCP API key",
      "password": true
    }
  ],
  "servers": {
    "edited-mcp": {
      "type": "http",
      "url": "https://mcp.edited.com/mcp",
      "headers": {
        "x-api-key": "${input:edited-api-key}"
      }
    }
  }
}

On first connection VS Code prompts for the key and stores it securely, so it's never written into the config file.

Where the config lives

• Workspace: .vscode/mcp.json in the repo root.
• User profile: run MCP: Open User Configuration from the Command Palette.

Verify

Run MCP: List Servers from the Command Palette — edited-mcp should show as running. In Agent mode the EDITED tools appear in the tools picker; ask something that needs the data and confirm a mdmcp-search_* tool is called.

Tips

• If permission prompts on every tools/call get noisy, allow them in your client's settings.
• EDITED's server-defined prompts (e.g. mdmcp-market_data_query_guide) aren't auto-injected into your context by most clients — fetch them explicitly with prompts/get and prepend the returned messages. See How to query → Using the server-defined prompts.
• Building your own agent instead of using an editor? See Connect a custom client for the MCP SDK and framework integrations.