Use this article to find the cause of a problem with Cint MCP in Claude and the steps to fix it. Find your symptom in the tables below. Problems are grouped by type: connection and sign-in, permissions, setup, duplicate tools, and Claude Code.
If you cannot find your symptom, or the fix does not work, see Contact Cint support at the end of this article.
Symptom Index
Find your symptom in the tables below. Problems are grouped by type: connection and sign-in, permissions, setup, duplicate tools, and Claude Code.
Connection and sign-in
Symptom | What to do |
|---|---|
“Can’t reach Cint” | Sign in to Cint again. Follow Claude's current instructions → Add a connector that isn't in the directory (see Connect as a member) |
Every request fails with a permissions error | Sign in again. If the error continues, contact Cint and include the error ID. |
Sign-in completes, but Claude cannot name a Cint account | Your Cint login is valid, but it is not attached to an account with Exchange access. Contact your Cint representative. |
The Exchange works in the Claude app but not in the Code view | The Code view is Claude Code, which authorizes separately from the Claude app. See Claude Code below. |
Permissions
Symptom | What to do |
|---|---|
You can view feasibility, projects, and target groups, but creating or launching is refused | You are signed in correctly, but your Cint account does not have write permissions. This is an account setting, not a sign-in problem, so signing in again will not fix it. Contact your Cint representative to have write access added. |
Setup
Symptom | What to do |
|---|---|
Claude says it has no Cint tools, the option to add a connector is unavailable, or there is no sign-in prompt and no way to authorize the connector | On Team and Enterprise plans, only an organization owner can add a connector. Ask an owner to add it, then sign in yourself. Follow Claude's current instructions → Get started with custom connectors using remote MCP |
| The skill may be switched off. Check your skills list. Follow Claude's current instructions → Use skills in Claude If the skill is not listed at all, the plugin did not install. Reinstall it. Follow Claude's current instructions → Use plugins in Claude |
Duplicate tools
Symptom | What to do |
|---|---|
Cint tools appear twice, or every approval prompt appears twice | The old Cint Exchange MCP connector is still installed next to the new Follow Claude's current instructions → Get started with connectors |
Claude Code
Symptom | What to do |
|---|---|
| The server was added in a different scope, or a |
The server shows as failed or disconnected | The token expired, or sign-in never completed. Run |
Sign-in completes, but no accounts are returned | Your credentials are valid, but your login is not attached to an account with Exchange access. Contact your Cint representative. |
Tools are listed twice, or approvals appear twice | An old |
Tools work, but every call asks for approval | Your permission rules still use the old Follow Claude Code's current instructions → All settings (settings reference) |
Claude says the server needs authorization and cannot run the sign-in flow itself | This is expected in the Code view. Run |
Behaviors that look like errors but aren't
Some Cint MCP behaviors look wrong at first but are expected. Find what you're seeing in the tables below.
Terminology and structure
What you see | Why it happens |
|---|---|
Claude says “target group” when you | The survey is your questionnaire, which lives on your own platform. The target group is the Exchange entity that fields it. It defines the market, qualifications, quotas, goal, price, supply, and dates. Claude uses the precise term so that statements like “three of your five target groups are live” are exact. You can keep saying “survey.” |
You asked for one survey in five markets | This is the correct structure: one questionnaire, five target groups, one project. Each market is priced, quota’d, and fielded separately. |
More qualifications than you asked for | A geographic qualification adds the qualifications that depend on it, usually postal code. The platform adds them to resolve the geography. |
Creating and launching
What you see | Why it happens |
|---|---|
Claude creates a draft when you asked it | Nothing goes into field without an explicit launch and an approval prompt. The draft is where you check the price and the goal. |
Claude shows a proposed quota split | When a qualification targets several values and has no quotas of its own, Claude proposes a split rather than inventing one. Approve the split, or give Claude your own numbers. |
Claude did not ask about supply | If you don’t specify supply, the target group uses your account’s default allocation. For most studies, this is the right choice. Ask Claude which allocation it used if you want to confirm. |
A new target group is named “Draft target | This is the default name when none is given. Tell Claude the name you want when you set up the target group. |
Claude says the goal counts “unknown,” | Fielding automation is on by default, as it is in the Exchange UI. The Exchange manages respondent flow to avoid overfilling quotas, and it decides what the goal counts. Automation does not reduce your fill. If you need the goal to count completes, ask for that when you set up the target group. This switches the automation off. |
Pricing and metrics
What you see | Why it happens |
|---|---|
A price you gave was ignored | The business unit uses a rate card, so the card sets the price of the target group. Claude should say so. If it does not, ask which pricing model the business unit uses. |
A price sits exactly on a round number | The price sits at the Exchange’s price floor or ceiling, which protect suppliers and buyers respectively. The estimate is sound. |
Metrics are blank or zero on a new | Counts are zero until respondents arrive, and rates are empty until there is data to calculate them from. This is not an error. |