Skip to main content
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.
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.

​
Add the Decoda connector

Point your assistant at the Decoda connector URL:
In Claude, add it like this:
1

Open Connectors

Open Customize in the sidebar, then select Connectors.
Customize menu in the sidebar

Customize menu in the sidebar

2

Add a custom connector

Click Add in the upper-right corner, then choose Add custom connector.
Add menu showing Add custom connector

Add menu with Add custom connector

3

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.
Add custom connector form with name and URL

Add custom connector form with the Decoda name and URL

4

Add the connector

Click Add. Decoda now appears in your list of connectors, ready to connect.
Decoda connector in the connectors list

Decoda in the connectors list

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

1

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.
2

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.
3

Review the request

Decoda shows the client name and the access it is requesting. Confirm that the client name is one you recognize. To allow access to settings that contain protected health information (PHI), select I have a Business Associate Agreement (BAA) with [client] and consent to PHI access for this MCP. Leave it clear to keep those settings unavailable to the client.
4

Approve the connection

Click Connect to Decoda. Decoda records your choice and sends you back to the MCP client.

​
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. Decoda hides settings that contain PHI unless the user confirms the BAA and PHI option during connection. 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.