> ## Documentation Index
> Fetch the complete documentation index at: https://www.getsoundlink.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Other MCP clients

> Connect any Streamable HTTP or CIMD client to the Soundlink MCP server with a URL, API key, or OAuth app.

Any client that speaks **Streamable HTTP** can use the same endpoint:

```
https://api.getsoundlink.com/mcp
```

For Claude and Cursor, see [Claude Directory](https://www.getsoundlink.com/docs/mcp-claude.md) and the [Cursor plugin](https://www.getsoundlink.com/docs/mcp-cursor.md). This page covers any other client that accepts a remote MCP URL.

## CIMD browser login

If the client supports a Client ID Metadata Document (CIMD), paste the MCP URL and complete the browser login. You do not create an OAuth app.

If the client does not request specific scopes, Soundlink grants your identity and read access only (`openid`, `email`, and each `:read` scope).

If Soundlink does not recognize the app, the consent screen says it is not verified and shows the host it will send you back to. Check that host before you approve.

## API key

If the client cannot open a browser, send the key as `Authorization: Bearer sk_your_key`.

Create the key in [Settings → Developer → API keys](https://getsoundlink.com/settings/developer) with `campaigns:read`, `metrics:read`, `soundlinks:read`, and `wallet:read`. Add `pixels:read` for `get_pixels`.

Example config:

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "mcpServers": {
    "soundlink": {
      "url": "https://api.getsoundlink.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_your_key"
      }
    }
  }
}
```

## OAuth app

Use this when the client asks for a client id and secret and does not use CIMD.

**1. Open OAuth apps**

Go to [Settings → Developer → OAuth
apps](https://getsoundlink.com/settings/oauth-apps).

**2. Create the app**

Set a name. Enable the **Authorization code** grant. Paste the redirect URI
your MCP client shows you — it must match exactly, including `http` vs
`https` and `localhost` vs `127.0.0.1`. Select the scopes above.

**3. Copy the client id and secret**

Paste both into the MCP client. The secret is shown once. Access tokens last
one hour. The client refreshes them, so you stay connected without signing
in again. See [OAuth](https://www.getsoundlink.com/docs/set-up-soundlink-oauth.md).

Soundlink does not support RFC 7591 dynamic client registration. Clients that try to register at runtime still need an API key or an OAuth app.

OAuth-only config:

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "mcpServers": {
    "soundlink": {
      "url": "https://api.getsoundlink.com/mcp"
    }
  }
}
```

## Check the connection

Ask the client to call `ping`. A working credential returns `{"status":"ok"}`. For the full tool list and scopes, see the [MCP overview](https://www.getsoundlink.com/docs/mcp-server.md#tools).

## Next

[MCP overview](https://www.getsoundlink.com/docs/mcp-server.md) · [Claude](https://www.getsoundlink.com/docs/mcp-claude.md) · [Cursor](https://www.getsoundlink.com/docs/mcp-cursor.md) · [Authentication](https://www.getsoundlink.com/docs/authentication.md) · [OAuth](https://www.getsoundlink.com/docs/set-up-soundlink-oauth.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.