---
title: "Connect Channels to Cursor desktop"
canonical: https://workspace.socra.com/docs/channels/integrations/cursor
---

# Connect Channels to Cursor desktop

Connect Cursor desktop to Channels using a public OAuth client in your Cloud Project. You need permission to manage OAuth clients and a Cursor version that supports static OAuth for remote MCP servers.

If Channels is already connected, preserve that connection. For a separate setup, choose a distinct server name and use it throughout the configuration and verification.

## 1. Select your Project and enable Channels

Open [Cloud Projects](https://platform.socra.com/projects) and choose your Account. Use **Manage Cloud Projects → Switch Projects** to find and select the Project. Confirm it in **Switch Cloud Project**.

Create a Project if needed. From inspection details, use **Back to list → Switch Projects**, or close the manager when the intended Project is already active.

Open **Enabled services**. Continue if Channels is listed; otherwise choose **Enable service → Channels** and confirm it appears. Keep this Project selected. Service enablement does not establish host authorization.

## 2. Register a public client

Open **OAuth → Overview**. If needed, choose **Set up OAuth**, enter **Channels for Cursor**, complete the consent information and save. Preserve an existing configuration.

Open **OAuth → Clients → Create client**. Name it **Channels for Cursor desktop**, choose **Native**, leave JavaScript origins empty, and register:

```url
http://localhost:8787/callback
```

This guide uses the desktop callback from [Cursor's static OAuth documentation](https://cursor.com/docs/mcp#static-oauth-for-remote-servers). Cursor's web callback is a separate surface; use the callback for the host you are configuring.

Create the public client and copy its client ID. This client does not need a client secret. If access is denied, use **Copy access request** with your Account and membership identity; ask the Project owner to resolve it, then choose **Check access again**.

## 3. Add the remote server

Open `~/.cursor/mcp.json` for your user configuration, or `.cursor/mcp.json` in a project for project configuration. Merge this entry into its existing `mcpServers` object, replacing `YOUR_CLIENT_ID` with the public client's ID:

```json
{
  "mcpServers": {
    "socra-channels": {
      "url": "https://channels.socra.cloud/mcp",
      "auth": {
        "CLIENT_ID": "YOUR_CLIENT_ID"
      }
    }
  }
}
```

Preserve other server entries. If you chose a distinct server name, replace `socra-channels` here and use that same name when enabling and verifying the connection. The `auth` entry provides your registered client instead of relying on automatic registration. No fixed authorization header or client secret is needed for this public client.

## 4. Authorize your Account

Before authorizing, review the access you are granting. Channels tools can read and modify data that your selected Account permits. The single read-only verification below does not restrict the connection’s overall authority. Review later tool calls and approve only the actions you intend.

Open Cursor's **Customize** page and enable the configured server. Follow the OAuth sign-in prompt when Cursor requests authorization. In the browser, sign into Socra, choose the Account you use in Channels and approve access. Return to Cursor.

If interrupted, return to the same connection. Check the client ID, exact desktop callback, enabled service and Account before retrying an error. If your Cursor version or organization policy prevents the setup, ask its owner or support to resolve that prerequisite. Keep working configurations intact.

## 5. Verify a real read

Confirm Channels tools appear under **Available Tools**. Ask Cursor to use the configured Channels server:

```text
Use Socra Channels to make exactly one channels_list tool call with limit 1. Do not read messages or send, create, update or delete anything. Report whether the call succeeded. An empty list is valid.
```

Review the tool approval and arguments. `channels_list` must execute with `limit: 1` and return a result; an answer without execution does not verify the connection.

If no tool runs, check the server and tool controls. For a failed call, retain the error and check the authorized Account and enabled Channels service in the client's Project. Ask the Account or Project owner to resolve denied access before retrying.

## Stop or remove this connection

Open **Customize**, find only your Channels server and turn its toggle off. To remove its configuration, edit the same `~/.cursor/mcp.json` or project `.cursor/mcp.json` used above and remove only its `socra-channels` entry from `mcpServers`. Use your distinct name if you chose one; preserve other server entries. Disabling the server is temporary and does not revoke its Socra authorization.

For optional cleanup of a client registration dedicated to this connection, ask its Project owner to select the same Project in Platform, open **OAuth → Clients**, select that exact client and choose **Delete**, then review the confirmation that its secrets are also removed. Preserve clients shared by other working connections. Removing a host entry or deleting a registration is not proof that every previously issued token has been revoked; ask the Account authorization owner for server-side revocation when that is required.

## See also

- [Connect Channels to Codex](/docs/channels/integrations/codex)
- [Connect Channels to Claude Code](/docs/channels/integrations/claude-code)
- [Conversations and access](/docs/channels/concepts/conversations-and-access)