This feature is currently in closed-beta. If you are interested in participating in the beta program, please contact your Customer Success Manager (CSM).
When you install an MCP, you're providing your AI assistant with instructions about how to connect to the server. The installation process varies by AI assistant.
Before you begin
You will need the following to install Cint MCP:
A Cint Exchange account with Exchange UI access and API access enabled for the beta. Confirm you can sign in at exchange.cint.com before you start. If you can't log in, installing the connector won't help.
An organization owner, if your company is on a Claude Team or Enterprise plan. Only owners can add a connector. It is one step for the whole organization, done once.
Claude app (desktop or web) or Claude Code. The install steps differ slightly between the desktop and web app. This guide covers the Claude app in Part 1 and Claude Code in Appendix A. If your team uses both, each person authorizes separately in each surface.
You do not need an API key, a client secret, or anything from a developer. Simply, sign in with your own Cint login.
Clear out earlier versions
If you took part in an earlier beta round, remove the old connector—named Cint Exchange MCP—before adding the new cint-mcp. They are separate connectors, and adding the new one will not remove the old one.
Why this matters: If both are installed, Claude will load two complete sets of Cint tools. You will see every approval prompt twice, and Claude may read from one connector while creating work through the other, giving you advice that contradicts itself.
How to remove the earlier version: Follow Claude's current instructions for removing a connector → Remove a connector
You do not need to remove the plugin. Installing the current version will replace it. You also do not need to revoke anything on the Cint side; signing out happens automatically when the connector goes.
Add the Cint connector
The connector is what lets Claude talk to the Cint Exchange. An organization owner adds it once, for the whole org. Connector access cannot be scoped to part of an organization. Once it's added, it is available to everyone.
Please note, adding the connector does not give anyone access to Cint data. The connector only tells Claude where the Cint server is. Each person who wants to use Cint MCP must sign in afterward with their own Cint credentials (§1.5). They will only be able to see what their credentials allow. Nothing is shared between colleagues, and the connector itself holds no login.
How to add the Cint connector: Follow Claude's current instructions for adding a custom connector → Add a custom connector
What to enter:
Field | Value |
|---|---|
Name |
|
Server URL |
Do not change the values for any other fields.
You will not need an OAuth client ID, client secret, or scopes. The Cint server identifies itself to Claude automatically during sign-in. If a field is asking you for a client ID, then you may need to disconnect an outdated connector.
Install the plugin
Cint will provide you with the plugin file directly.
The plugin contains the "skills—or the judgment layer. It teaches Claude how targeting and quotas work, what the numbers mean, and which mistakes produce a confident wrong answer.
How to install the plugin: Follow Claude's current instructions for installing a plugin from a file → Use plugins in Claude
Upload the cint-exchnage-0.7.0.plugin
Sign in to Cint
Now that the connector has been configured, each user will need to sign in using their Cint credentials.
What signing in does: It authorizes Claude to call the Cint Exchange as you. The permissions you have within Claude match your permissions within Cint Exchange. If you attempt to do something within Claude that you can’t do within Cint Exchange, Claude will state it can’t complete the prompt.
How to sign in: Follow Claude's current instructions for connecting to a connector → Connect as a member
Find
cint-mcpin your connectors list and connect. You will be sent to Cint's sign-in page.Use the same credentials as exchange.cint.com.
Approve the access request.
You can also skip straight to work and let Claude prompt you. Simply ask Claude something about the Exchange in a new chat, and it will offer to connect at the point it needs to. The result is identical.
Sign-in is per person: The connector holds no credentials of its own. Each person who wants to use the Cint Exchange must go through the steps above with their own login.
Sign-in is also per surface: The Claude app and Claude Code authorize separately. Signing in to one does not carry over to the other. This includes the Code view inside the Claude desktop app, which is Claude Code — see Appendix A.
How long your authorization will last: Your authorization is remembered and refreshes on its own, so day-to-day use involves no sign-in at all. You will be asked again only if:
You revoke access
The authorization expires after a long gap
Cint changes what it requires. If this happens, Claude will prompt you at the point of your next request rather than failing silently
Turning off your connection: Disconnect to revoke your authorization. Nothing is deleted on the Cint side, and you can sign in again whenever you like. Follow Claude's current instructions for disconnecting a connector → Manage or disconnect a connector
If you can view things but cannot create or launch anything, this is not a sign-in problem. Re-signing in will not fix this issue. It means your Cint account doesn't have write permissions yet. Contact your Cint representative to get write access added to your account.
Verify your setup
Check the connector in one of the following ways:
Check the connector: Start a new chat and ask "check my Cint connection." Claude will report the Cint account it's working in. That single answer proves three things at once:
The connector is reachable
Your credentials were accepted
Claude can read from the Exchange on your behalf
Check the skill loaded: In a new chat, type
/cint-demand-mpcYou should get the following message:Welcome to the Cint Exchange. What can I help you with today?
If either check fails, go to the symptom index in §4.3.
See the following articles for more information:
Appendix A - Claude Code CLI