Connecting Claude Code over MCP
A token plus an endpoint is the whole setup, and the card gives you both without leaving the app.
- Open Settings and find the MCP Connection card.
- Click Generate token. Give it a name you will recognise later, such as the client you are setting up, then click Generate.
- Copy the token from the Your new token dialog. It is shown exactly once, and only a hash of it is stored, so if you lose it you generate another rather than recover it. Click Done when it is safely in place.
- Click Connection guide on the same card and pick your client’s tab: Claude Code, Claude Desktop, Cursor or Other. Each tab lists the steps and the exact snippet for that client, with a copy button.
- For Claude Code, run the command from the Claude Code tab in any terminal, then start Claude Code and ask it about your helpdesk. For Claude Desktop, open Settings, Connectors, Add custom connector, paste the endpoint and add an
Authorizationheader. For Cursor, open Settings, MCP, Add new MCP server and paste the JSON. Any client that speaks Streamable HTTP can use the Other tab. - Replace
<token>in whichever snippet you copied with the token you generated. The endpoint is already filled in for you, read from the Endpoint field at the top of the card, so you are copying a value rather than looking one up. The small copy button beside it takes it on its own if you need it. - Expand Setup snippet on the card for the same one line command without opening the guide dialog.
The card lists every token you hold, with its name, its hint, when it was created and when it was last used. Revoke beside a token cuts its access immediately, after one confirmation, and a revoked token stays in the list marked Revoked so the history is still readable.
Custom connectors on claude.ai work differently. Instead of pasting a token you go through a sign in and consent flow, and the token that flow mints appears in the very same list, named after the client that asked for it, with the same Revoke button. There is one place to see what has access, whichever way it was granted.
See this on your own workflow
This is the product as it stands today. A call is where you find out which parts of it your team would turn on, and what a deployment looks like.
partnerships@dhcertainty.com