> For the complete documentation index, see [llms.txt](https://docs.subsalt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subsalt.io/retrieving-data/mcp/connecting-a-client.md).

# Connecting a client

## Connecting a client

The Subsalt MCP server speaks the **Streamable HTTP** transport and authenticates with **OAuth 2.0**. Supported clients must send the required OAuth client ID. Sign-in happens in your browser against your normal Subsalt identity provider — the same login you use for the portal, including SSO — so there is no separate API key to manage.

#### Endpoint

Point your client at your deployment's MCP endpoint:

```
https://mcp.<your-subsalt-domain>/mcp
```

{% hint style="info" %}
Your exact endpoint hostname is specific to your deployment. If you're not sure what it is, ask your Subsalt administrator or check the **Connection details** in the Subsalt portal.
{% endhint %}

The first time a client connects, it opens a browser window for sign-in and authorization. Your client stores and refreshes the resulting token. If a session expires, sign in again. This uses standard OAuth 2.0 discovery ([RFC 9728](https://datatracker.ietf.org/doc/html/rfc9728)).

***

#### Claude Code

Add the server from the command line, then authenticate:

```bash
claude mcp add --transport http --client-id subsalt-mcp subsalt https://mcp.<your-subsalt-domain>/mcp
```

Run `/mcp` inside Claude Code to complete the browser sign-in and confirm the connection is live.

{% hint style="warning" %}
The MCP endpoint requires OAuth and the `subsalt-mcp` client ID. Clients that cannot configure this client ID are not currently supported.
{% endhint %}

***

#### Verifying the connection

Once connected, ask your agent to call the **`instructions`** tool. It returns a short getting-started guide and lists the databases available to you — a quick confirmation that authentication succeeded and that your access is what you expect. From there, follow the standard workflow.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.subsalt.io/retrieving-data/mcp/connecting-a-client.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.