> For the complete documentation index, see [llms.txt](https://docs.elevateab.com/elevate-helpcenter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elevateab.com/elevate-helpcenter/mcp/connect-other-mcp-clients.md).

# Connect Other MCP Clients

Connect any MCP client to Elevate A/B Testing: server URL, Streamable HTTP transport, OAuth 2.1 or bearer token login, and a config most clients accept.

Any MCP client that supports Streamable HTTP can connect to Elevate A/B Testing, not only the clients with their own setup guide. This page lists the server details and the configuration most clients accept.

The connection is read-only unless you allow changes: your client can see your tests and results, and it can't change anything in your store. To let your client create, launch, pause, resume and end experiments, see [Let Your AI Assistant Make Changes](https://docs.elevateab.com/elevate-helpcenter/mcp/let-your-ai-assistant-make-changes.md).

***

### Server details

| Setting   | Value                           |
| --------- | ------------------------------- |
| URL       | `https://elevateab.app/api/mcp` |
| Transport | Streamable HTTP                 |
| Auth      | OAuth 2.1, or a bearer token    |

Elevate A/B Testing does not serve SSE. If your client asks for an SSE endpoint, pick Streamable HTTP.

You'll find these details in Elevate A/B Testing under **MCP** in the sidebar, then **Other MCP clients**.

### If your client supports OAuth

Point the client at the URL with no header, then log in to Elevate A/B Testing in the client and approve read-only access for your store. There is no key to create.

### If your client uses a bearer token

1. On the **Other MCP clients** setup screen, click **Create key**. Elevate A/B Testing adds the key to the setup. The key is read-only. To let the client make changes, tick **Can make changes** when you create it.
2. Copy the setup now. For your security, the full key is only shown once. If you lose it, disconnect it under **Connections** and create a new one.
3. Paste the setup into your client's configuration file. Most clients use this shape:

```json
{
  "mcpServers": {
    "elevate": {
      "url": "https://elevateab.app/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}
```

Usually only the file name changes from client to client.

### Confirm it's working

Ask your assistant: What tests am I running?

The status box on the setup screen reads **Waiting for a request** until the first request arrives, then changes to **Connected** on its own.

***

### Next steps

* [MCP Overview](https://docs.elevateab.com/elevate-helpcenter/mcp/mcp-overview.md): every client, and what the assistant can read
* [Manage MCP Connections](https://docs.elevateab.com/elevate-helpcenter/mcp/manage-mcp-connections.md): see and disconnect connections
