Docs

Connect Cursor, VS Code & others

Connect Cursor, VS Code, Windsurf, Gemini CLI, Cline, Zed or any other MCP client with one connection link.

On this page

Code editors and other MCP clients connect to your site with a connection link: one address that already carries its own key. Cursor and VS Code install it in one click. Other apps take it as the server URL, with no headers or sign-in to set up.

Go to Uncoder → AI & MCP → Connect a client and pick the app on the left.

On the app's panel, click Create connection link. The link appears with a Copy button, and it is filled into the install button and every snippet on the page, so you can copy them as they are.

The link is shown only once. If you leave the page, the snippets show YOUR_CONNECTION_LINK again: paste your link there, or create a new one. Each app gets its own link, so you can revoke one without breaking the others. See Connection links.

Warning

A link gives access to your site. Keep configuration files that contain a link out of Git and other shared folders. Put them in your user settings rather than in a project.

Cursor

The Cursor instructions: Create connection link, an Add to Cursor button, an mcp.json entry with the url, and a check in Cursor's MCP settings
Connect a client → Cursor
  1. Install in one click

    Click Add to Cursor. Cursor opens with your site filled in. Confirm the install.

  2. Or add it to mcp.json

    Open ~/.cursor/mcp.json to use your site in all projects, or .cursor/mcp.json inside one project, and add the snippet from Uncoder:

    JSONmcp.json
    {
      "mcpServers": {
        "uncoder-my-site": {
          "url": "https://example.com/wp-json/uncoder/v1/mcp?token=uncoder_link_…"
        }
      }
    }
  3. Check the connection

    Open Cursor's MCP settings. Your site's server should show a green dot and its list of tools.

Do not commit a project mcp.json that contains a link.

VS Code

VS Code uses your site's tools in GitHub Copilot's agent mode.

The VS Code instructions: Create connection link, an Install in VS Code button, and an mcp.json entry with type http and the url
Connect a client → VS Code
  1. Install in one click

    Click Install in VS Code. VS Code opens the server's install page. Confirm the install.

  2. Or add it by hand

    Run MCP: Add Server from the Command Palette, choose HTTP and paste the link. Or open your user configuration with MCP: Open User Configuration and add:

    JSONmcp.json
    {
      "servers": {
        "uncoder-my-site": {
          "type": "http",
          "url": "https://example.com/wp-json/uncoder/v1/mcp?token=uncoder_link_…"
        }
      }
    }
  3. Start it

    Start the server, then open Copilot Chat, switch to agent mode and pick the tools under Tools.

On Copilot Business and Enterprise, an organization admin must allow MCP servers first. Keep links in your user configuration, not in a shared workspace.

Windsurf

Windsurf, now also called Devin Desktop, connects to remote servers with a serverUrl.

The Windsurf instructions: Create connection link, where to find mcp_config.json and an mcpServers entry with serverUrl
Connect a client → Windsurf
  1. Open the MCP config

    In the app's MCP settings, choose View raw config. The file is mcp_config.json: in Devin Desktop it is in %APPDATA%\devin on Windows and ~/.config/devin on Mac and Linux; in older Windsurf versions it is ~/.codeium/windsurf/mcp_config.json.

  2. Add the server

    JSONmcp_config.json
    {
      "mcpServers": {
        "uncoder-my-site": {
          "serverUrl": "https://example.com/wp-json/uncoder/v1/mcp?token=uncoder_link_…"
        }
      }
    }
  3. Refresh

    Refresh the MCP servers list.

With the Devin CLI, one command does the same: devin mcp add uncoder-my-site "<your link>".

Any other MCP client

Choose Other clients on the Connect a client tab. It has three methods.

Any client that takes a remote (Streamable HTTP) server URL works with the link alone. Uncoder shows ready-made snippets for the most common ones.

The Other clients instructions: Create connection link, then snippets for Gemini CLI, Cline, Zed and Continue, each with the link
Connect a client → Other clients → Connection link
AppWhere the link goes
Gemini CLIgemini mcp add --transport http uncoder-my-site "<your link>"
ClineMCP Servers → Remote Servers, or cline_mcp_settings.json with "type": "streamableHttp" and "url"
Zedsettings.json under "context_servers", with "url"
ContinueA file in .continue/mcpServers/ with type: streamable-http and url

For any other app, paste the link wherever it asks for the MCP server URL and choose Streamable HTTP (sometimes called "HTTP") if it asks for a type.

Local (stdio) apps

Some apps can only start a local program (a "stdio" server) and cannot connect to a remote address. For those, use mcp-remote, a small open-source bridge that runs on your computer and forwards everything to your site. It needs Node.js (opens in a new tab) 18 or newer; npx downloads it the first time.

The Local (stdio) apps instructions: Create connection link and the npx mcp-remote command with the link
Connect a client → Other clients → Local (stdio) apps

Use this as the server command in your app:

Terminal
npx -y mcp-remote "https://example.com/wp-json/uncoder/v1/mcp?token=uncoder_link_…"

For a local site on plain http with an address other than localhost (such as mysite.test), add --allow-http at the end; Uncoder's snippet does this for you.

In an app that uses the common mcpServers format, that looks like this:

JSON
{
  "mcpServers": {
    "uncoder-my-site": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://example.com/wp-json/uncoder/v1/mcp?token=uncoder_link_…"]
    }
  }
}

API key in a header

For apps and scripts that send their own headers, and when you prefer no key in an address, use an API key instead of a link. Give the client:

  • the Server URL, for example https://example.com/wp-json/uncoder/v1/mcp
  • the API key as a bearer token in every request:
Text
Authorization: Bearer YOUR_API_KEY

An API key lets you choose its permissions (including Site) and an expiry date. Clients that support OAuth 2.1 can sign in instead, like the Claude and ChatGPT connectors. They find the sign-in details on their own from the Server URL. Your site must be public and use HTTPS for that.

Local sites

A site on your own computer (for example http://localhost/… or mysite.test) works with every app on this page, because the app runs on the same computer. Plain http links are accepted only for local addresses. Only connectors that run on the AI company's servers, such as the Claude app and ChatGPT on the web, need a public HTTPS site.