> For the complete documentation index, see [llms.txt](https://help.fungies.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fungies.io/for-saas-developers/fungies-mcp/cursor-claude-vs-code-integration.md).

# Cursor, Claude, VS Code integration

### Pick your AI tool

All configs use the same hosted endpoint: `https://mcp.fungies.io/mcp`. No local installation, no Node.js, no Docker.

#### Cursor

**Option A — One-click (recommended)**

Visit [mcp.fungies.io/install](https://mcp.fungies.io/install), paste your keys, click Install.

**Option B — Manual**

1. Open the Cursor settings JSON — press `Cmd/Ctrl + Shift + P`, search for **"Open MCP Settings"**, or edit `~/.cursor/mcp.json` directly.
2. Add this block:

```
{
  "mcpServers": {
    "fungies": {
      "url": "https://mcp.fungies.io/mcp",
      "headers": {
        "x-fngs-public-key": "pub_YOUR_PUBLIC_KEY",
        "x-fngs-secret-key": "sec_YOUR_SECRET_KEY"
      }
    }
  }
}
```

3. Restart Cursor. Open the Agent panel — you should see **"fungies"** in the tool list.

Omit `x-fngs-secret-key` for read-only mode (17 tools, no risk of accidental changes).

#### Claude Desktop

Claude Desktop supports remote MCP servers via its custom connectors UI.

1. Open Claude Desktop → **Settings → Connectors → Add custom connector**.
2. Fill in:
   * **Name**: `Fungies`
   * **Remote MCP server URL**: `https://mcp.fungies.io/mcp`
3. Under **Advanced → Custom headers**, add:
   * `x-fngs-public-key` → your `pub_...` key
   * `x-fngs-secret-key` → your `sec_...` key (optional)
4. Save. Start a new chat and Claude will offer Fungies tools.

> **Older Claude Desktop (no custom-connectors UI)** — use the [stdio fallback](https://github.com/dukenukemall/fungies-mcp#other-mcp-clients-stdio-fallback) at the bottom of this doc.

#### Claude Code (CLI)

Claude Code has native remote-MCP support via the `claude mcp add` command.

```
claude mcp add --transport http fungies https://mcp.fungies.io/mcp \
  --header "x-fngs-public-key: pub_YOUR_PUBLIC_KEY" \
  --header "x-fngs-secret-key: sec_YOUR_SECRET_KEY"
```

Verify with `claude mcp list` — you should see `fungies` listed. Start any chat and Claude Code will discover the tools automatically.

#### VS Code (GitHub Copilot Chat)

VS Code 1.95+ with GitHub Copilot Chat supports MCP servers.

1. Open the command palette — `Cmd/Ctrl + Shift + P`.
2. Run **"MCP: Add server → HTTP"**.
3. When prompted:
   * **URL**: `https://mcp.fungies.io/mcp`
   * **Name**: `fungies`
4. Open `~/.config/Code/User/mcp.json` (or `%APPDATA%\Code\User\mcp.json` on Windows) and add the headers:

```
{
  "servers": {
    "fungies": {
      "type": "http",
      "url": "https://mcp.fungies.io/mcp",
      "headers": {
        "x-fngs-public-key": "pub_YOUR_PUBLIC_KEY",
        "x-fngs-secret-key": "sec_YOUR_SECRET_KEY"
      }
    }
  }
}
```

5. Reload VS Code. Open Copilot Chat in **Agent** mode — Fungies tools appear in the tool picker.

#### Continue.dev

Edit `~/.continue/config.yaml` (or through Continue's settings UI):

```
mcpServers:
  - name: fungies
    type: http
    url: https://mcp.fungies.io/mcp
    requestOptions:
      headers:
        x-fngs-public-key: pub_YOUR_PUBLIC_KEY
        x-fngs-secret-key: sec_YOUR_SECRET_KEY
```

Restart Continue — Fungies tools show up in any agent session.

#### Windsurf

1. Open **Settings → Windsurf Settings → Cascade → MCP Servers → Add custom server**.
2. Paste:

```
{
  "mcpServers": {
    "fungies": {
      "serverUrl": "https://mcp.fungies.io/mcp",
      "headers": {
        "x-fngs-public-key": "pub_YOUR_PUBLIC_KEY",
        "x-fngs-secret-key": "sec_YOUR_SECRET_KEY"
      }
    }
  }
}
```

3. Save and refresh the server list. Fungies tools appear in Cascade.

#### OpenAI Codex CLI

Codex CLI supports remote MCP servers via `~/.codex/config.toml`:

```
[mcp_servers.fungies]
url = "https://mcp.fungies.io/mcp"

[mcp_servers.fungies.headers]
"x-fngs-public-key" = "pub_YOUR_PUBLIC_KEY"
"x-fngs-secret-key" = "sec_YOUR_SECRET_KEY"
```

Run `codex` in any terminal — it will pick up the config and expose Fungies tools to the session.

#### Zed

Zed 0.160+ ships MCP ("context servers") support. Add to `~/.config/zed/settings.json`:

```
{
  "context_servers": {
    "fungies": {
      "source": "custom",
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.fungies.io/mcp",
        "--header",
        "x-fngs-public-key:pub_YOUR_PUBLIC_KEY",
        "--header",
        "x-fngs-secret-key:sec_YOUR_SECRET_KEY"
      ]
    }
  }
}
```

Zed bridges to our HTTP endpoint through the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) helper (ships via `npx`, no install needed).

#### Other MCP clients (stdio fallback)

If your MCP host only speaks stdio, use `mcp-remote` as a bridge. Replace the `command`/`args` in your host's config with:

```
{
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://mcp.fungies.io/mcp",
    "--header",
    "x-fngs-public-key:pub_YOUR_PUBLIC_KEY",
    "--header",
    "x-fngs-secret-key:sec_YOUR_SECRET_KEY"
  ]
}
```

This works for any client that supports a local `command` + `args` style stdio server (older Claude Desktop builds, LibreChat, Goose, Sourcegraph Cody, etc.).