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

# Connect MCP clients

> How to connect an approved MCP client to Decoda with a signed-in user account.

MCP clients can connect to Decoda after a user signs in and approves the connection. The client receives short-lived access for the selected tenant, so it can only use the Decoda tools available to that tenant.

Any AI assistant that supports MCP connectors can connect to Decoda — the steps below use Claude as the example, but the same connector URL works in other assistants.

<Info>
  **Prerequisites:** Use an MCP client that supports custom connectors and sign in with a Decoda account that has access to the tenant you want to connect.
</Info>

## Add the Decoda connector

Point your assistant at the Decoda connector URL:

```
https://api.decodahealth.com/settings/mcp
```

In Claude, add it like this:

<Steps>
  <Step title="Open Connectors">
    Open **Customize** in the sidebar, then select **Connectors**.

    <Frame caption="Customize menu in the sidebar">
      <img src="https://mintcdn.com/decodahealth/epp129nQRd2Yoh_-/images/mcp-connector-customize-menu.png?fit=max&auto=format&n=epp129nQRd2Yoh_-&q=85&s=0f09c9151f4e6f7c57c39dc6f7a8a0d0" alt="Customize menu in the sidebar" width="622" height="474" data-path="images/mcp-connector-customize-menu.png" />
    </Frame>
  </Step>

  <Step title="Add a custom connector">
    Click **Add** in the upper-right corner, then choose **Add custom connector**.

    <Frame caption="Add menu with Add custom connector">
      <img src="https://mintcdn.com/decodahealth/epp129nQRd2Yoh_-/images/mcp-connector-add-custom-menu.png?fit=max&auto=format&n=epp129nQRd2Yoh_-&q=85&s=837f7ac3689265628da4767ea25cef35" alt="Add menu showing Add custom connector" width="636" height="276" data-path="images/mcp-connector-add-custom-menu.png" />
    </Frame>
  </Step>

  <Step title="Enter the name and URL">
    Give the connector a name, such as **Decoda**, and paste the connector URL above into the URL field. Leave the OAuth fields under **Advanced settings** blank.

    <Frame caption="Add custom connector form with the Decoda name and URL">
      <img src="https://mintcdn.com/decodahealth/epp129nQRd2Yoh_-/images/mcp-connector-custom-form.png?fit=max&auto=format&n=epp129nQRd2Yoh_-&q=85&s=60359cce74b2709f8046b56a7cae745b" alt="Add custom connector form with name and URL" width="1094" height="1350" data-path="images/mcp-connector-custom-form.png" />
    </Frame>
  </Step>

  <Step title="Add the connector">
    Click **Add**. Decoda now appears in your list of connectors, ready to connect.

    <Frame caption="Decoda in the connectors list">
      <img src="https://mintcdn.com/decodahealth/epp129nQRd2Yoh_-/images/mcp-connector-list-add.png?fit=max&auto=format&n=epp129nQRd2Yoh_-&q=85&s=ef4ba90ecbe3de87365a7389d75719a8" alt="Decoda connector in the connectors list" width="1922" height="394" data-path="images/mcp-connector-list-add.png" />
    </Frame>
  </Step>
</Steps>

Other assistants use a similar setup — look for an option to add a custom MCP connector or server, and enter the same URL.

## What the user sees

<Steps>
  <Step title="Start the connection from the MCP client">
    Open the MCP client and choose the Decoda connection. The client opens a Decoda sign-in page if you are not already signed in.
  </Step>

  <Step title="Sign in if prompted">
    Sign in with your Decoda account. After sign-in, Decoda sends you to the connection approval screen for the same MCP client, so you can finish the request without starting over.
  </Step>

  <Step title="Review the request">
    Decoda shows the client name and the access it is requesting. Confirm that the client name is one you recognize.
  </Step>

  <Step title="Approve the connection">
    Click **Connect to Decoda**. Decoda sends you back to the MCP client after the connection is approved.
  </Step>
</Steps>

## What connected clients can do

A connected client can use Decoda's MCP tools for the tenant included in the connection. Decoda checks the tenant on each request and blocks access to other tenants.

Access tokens are short-lived. If a token expires, the client must send the user through the connection flow again.

## Register a client

Integrators can register a public client with Decoda before starting the user connection flow. The registration includes:

* Client name shown to users during approval.
* One or more secure return URLs.
* The requested access scope. Decoda currently supports **mcp:access**.

Return URLs must use HTTPS. Local development URLs may use **localhost**, **127.0.0.1**, or **::1** over HTTP.

## Disconnect or revoke access

The current MCP connection uses short-lived access tokens. A revoke request is recorded for audit history, but existing access tokens are not immediately invalidated yet. Tokens stop working when they expire.