# Other MCP clients

> Connect Atlassian Rovo, Cursor, VS Code, Windsurf, Amazon Quick and other MCP clients, and the bridge for clients that only speak stdio.

Source: https://stensul.com/developers/quickstart/other-clients/ · Last reviewed 2026-10-07

Any client that supports remote MCP servers with OAuth can connect to your per-instance URL:

```text
https://mcp.stensul.com/<your-instance>/mcp
```

Every client below is available. The last column says how each one connects.

| Client | How it signs in | Our testing |
| --- | --- | --- |
| Claude, Claude Code, Copilot Studio, Writer, ChatGPT, Gemini Enterprise | See their quickstarts | [Available] Setup guides published |
| Atlassian Rovo | Self-registration (DCR). An Atlassian admin adds it | [Available] Tested with self-registration (DCR) |
| Cursor | Static Client ID in `mcp.json` | [Available] Paste the entry into Cursor's settings file |
| VS Code (GitHub Copilot), Windsurf | `mcp-remote` bridge with a static Client ID | [Available] Added through a small helper program |
| Amazon Quick | `mcp-remote` bridge with a static Client ID | [Available] Pasted as JSON in Amazon Quick's settings |

If you connect a client that isn't in the table, [tell us how it went](mailto:help@stensul.com?subject=MCP%20client%20report).

For every client that uses a static Client ID, your Stensul admin creates an Authorization Code API connection with **PKCE (Public)** on and the redirect URI `https://mcp.stensul.com/<your-instance>/oauth/callback`, as in step 1 of [Connect Claude](https://stensul.com/developers/quickstart/claude/#1-create-the-api-connection-in-stensul).

## Atlassian Rovo

Rovo registers itself with Stensul using Dynamic Client Registration (DCR), so there is no Client ID to create or paste. It does need an **Atlassian admin**:

1. The Atlassian admin adds Stensul to Rovo as a **custom MCP server** with the URL `https://mcp.stensul.com/<your-instance>/mcp`, using DCR.
2. Create a **custom agent** in Rovo with the Stensul MCP server as a tool.
3. Each person connects it in Rovo, logs in to Stensul and approves.

A self-registered client gets every Stensul scope; see [Self-registration (DCR)](#self-registration-dcr) below.

## Cursor

Cursor accepts a static Client ID in `mcp.json`:

```json
{
  "mcpServers": {
    "mcp-stensul": {
      "url": "https://mcp.stensul.com/<your-instance>/mcp",
      "auth": { "CLIENT_ID": "<client-id>" }
    }
  }
}
```

The exact `auth` syntax depends on your Cursor version. Check [Cursor's MCP docs](https://docs.cursor.com/context/model-context-protocol) if it's rejected.

## VS Code (GitHub Copilot) and Windsurf

These clients don't expose a static Client ID setting, so they use `mcp-remote` as a local bridge. Add this to the client's MCP configuration file:

```json
{
  "mcpServers": {
    "mcp-stensul": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.stensul.com/<your-instance>/mcp",
        "3334",
        "--static-oauth-client-info", "{\"client_id\":\"<client-id>\"}"
      ]
    }
  }
}
```

Pin the callback port (`3334`). Some clients launch `mcp-remote` more than once, and without a fixed port the duplicate sign-ins collide and can leave the server disabled.

## Amazon Quick

In Amazon Quick, go to **Settings > Capabilities > MCP > + Add MCP**, choose **Remote**, click **Paste JSON** and paste:

```json
{
  "command": "npx",
  "args": [
    "-y", "mcp-remote",
    "https://mcp.stensul.com/<your-instance>/mcp",
    "3334",
    "--static-oauth-client-info", "{\"client_id\":\"<client-id>\",\"scope\":\"libraries:read emails:read emails:write images:write\"}"
  ]
}
```

Add a name, then click **+ Add MCP**. Add `dam:read dynamic-content:read dynamic-content:write` to the `scope` value if your connection has those scopes.

## Clients that only support stdio

Wrap the HTTPS endpoint with `mcp-remote` and a pre-registered public Client ID. Pin the callback port so repeated launches don't collide:

```bash
npx -y mcp-remote https://mcp.stensul.com/<your-instance>/mcp 3334 \
  --static-oauth-client-info '{"client_id":"<client-id>"}'
```

## Self-registration (DCR)

Of the clients on this page, Atlassian Rovo is the one that uses Dynamic Client Registration: it discovers Stensul's registration endpoint and registers itself on first connect. What to know:

- Registered clients are public: PKCE required, no secret.
- Only the authorization-code grant (with refresh tokens) is issued. There is no client-credentials path.
- A self-registered client gets **every** Stensul scope and it can't be narrowed. The signed-in user's permissions still apply. If you need a narrower connection, give the client a static Client ID instead.
- Unused registrations are pruned. The client re-registers on its next connection, which means one more sign-in.