---
title: "Connect Any MCP Client to Rendley | Rendley MCP Docs"
description: "Connect Cursor, VS Code, Windsurf, Zed, Perplexity or any client that speaks remote MCP, with a JSON config or the mcp-remote bridge."
url: https://docs.rendley.com/mcp/other-clients/
---

# Other clients

Any client that speaks remote MCP can connect. Point it at the endpoint and sign in.

```
https://mcp.rendley.com/mcp
```

## Config block

Most clients accept a JSON config like this. Match the keys your client expects:

```
{
  "mcpServers": {
    "rendley": {
      "url": "https://mcp.rendley.com/mcp"
    }
  }
}
```

Without a header, the client opens a browser sign-in flow the first time it connects. Approve access in Rendley and the client stores the session. You can revoke access later from your Rendley settings.

Some clients want `"type": "http"`, and some use `serverUrl` instead of `url`.

### Using an API key instead

For clients that take a static token but cannot run a browser flow, send the key as a header:

```
{
  "mcpServers": {
    "rendley": {
      "url": "https://mcp.rendley.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_RENDLEY_API_KEY"
      }
    }
  }
}
```

The `Bearer` prefix, including the trailing space, is required. One key reaches both endpoints, so this also skips a second sign-in if you configure the [Claude directory version](https://docs.rendley.com/mcp/public-connector/) alongside it under a different server name.

## Clients without native remote MCP

If a client only speaks local MCP, bridge to the remote server with [`mcp-remote`](https://www.npmjs.com/package/mcp-remote):

```
{
  "mcpServers": {
    "rendley": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.rendley.com/mcp"
      ]
    }
  }
}
```

The bridge opens the browser sign-in flow on first run. To use a key instead, append `--header` and `Authorization:Bearer YOUR_RENDLEY_API_KEY` to the `args` array.

## Per-client notes

- **Cursor.** Settings, then **MCP**, then **Add new MCP server**. Native HTTP and sign-in are supported.
- **VS Code (Copilot).** Run **MCP: Add Server**, choose **HTTP**, and paste the URL.
- **Windsurf.** Uses `serverUrl` with `"type": "streamable-http"`. If your build does not connect directly, use the bridge above.
- **Zed.** The remote URL form does not accept custom headers yet. Sign-in works, but use the bridge above if you need to send a key.
- **Perplexity.** Settings, then **Connectors**, then **Add a connector**, then **Custom MCP server**, and sign in. Available on paid tiers.

Using a client not listed here? Send the client name and your config to [support@rendley.com](mailto:support@rendley.com) and it gets added to this page.

## What to read next

- **[Connect your AI client](https://docs.rendley.com/mcp/connect/)** covers the endpoint choice and the test that proves the connection.
- **[Authentication](https://docs.rendley.com/mcp/authentication/)** covers OAuth sign-in, API keys and the paid-plan gate.
- **[Automation connector](https://docs.rendley.com/mcp/automation/)** runs the whole edit and returns a download URL.
- **[Troubleshooting](https://docs.rendley.com/mcp/troubleshooting/)** lists the errors people hit and what fixes them.

[Previous pageChatGPT and Codex](https://docs.rendley.com/mcp/chatgpt/) [Next pageWhat the agent can do](https://docs.rendley.com/mcp/capabilities/)
