Claude connector (MCP)

The Survey Coder connector lets market research analysts who code open-ended survey questions work with their Survey Coder account from Claude. Ask how your projects are going, read the results of a coded question, have Claude analyze a newly uploaded .sav file and propose a coding plan, import it, and start coding — without leaving the conversation.

The connector works with your own Survey Coder user and permissions: Claude sees exactly what you see in the portal, nothing more. It is built to support your team, not replace it — reviewing and refining the codebook stays with the analyst in the portal.

Connect it

In Claude, open Settings → Connectors. Find Survey Coder in the directory, or choose Add custom connector and enter:
```
https://api.surveycoder.io/mcp
```
Claude sends you to Survey Coder. Sign in if needed, then click Authorize on the screen “Claude wants to access your Survey Coder account”.
You’re back in Claude with the connector enabled. Try “What needs my attention?”.

Sign-in uses OAuth 2.1 (authorization code with PKCE) through Survey Coder’s own account system; Claude never sees your password. Discovery metadata is published at https://api.surveycoder.io/.well-known/oauth-protected-resource.

Tools

Read-only

Tool	What it does
`advisor_attention`	Lists what needs attention: questions with pending Refine suggestions, and projects whose latest export is held for review or failed.
`advisor_project_status`	Status of one project: per-question responses, coding progress, pending suggestions, latest import and exports, and next steps.
`advisor_question_results`	Results of a coded question, computed like the dashboard: respondents per category and code over the question base, plus sample verbatims.
`advisor_question_segments`	Results of a coded question broken down by a segment variable (region, age…), with each segment’s base and 95% significance letters. Without a variable, lists the ones available.
`wave_check`	Checks whether an uploaded file fits as the next wave of a tracking study: which of the previous wave’s questions find their columns and which don’t. You add the wave in the portal.
`refine_suggestions`	Pending Refine suggestions for a question or project, explained in plain language with example responses. Approving them stays in the portal.
`advisor_review_question_setup`	Explains how a question is configured to be coded and flags settings that are usually mistakes.
`upload_link`	Returns the portal link where you upload new survey files (files can’t be attached through the chat). Upload, stop at the review screen and come back to Claude.
`inbox_list`	Files uploaded in the last 30 days that have not been imported yet, and failed imports.
`credits_overview`	Your credit balance, what was spent in the last 30 days and on which projects, recent purchases and the assistant’s credit limits.
`deliverables_list`	A project’s recent exports (what, when, status, files) and its saved export templates.
`deliverable_link`	Fresh download link (valid 15 minutes) for a file of a finished export.
`coding_estimate`	Exact credit estimate for coding a project, question by question, using the same planner that starts the job. Costs nothing.

Writes

Tool	What it does
`advisor_analyze_sav`	Analyzes an uploaded `.sav`, `.xlsx` or `.csv` and proposes a coding plan: which open-ended questions to code and how, “Other, specify” columns, context columns and estimated credits. Saves the proposal on the upload; imports nothing and spends no credits.
`question_config_update`	Changes how one question will be coded next time — AI instructions, multi-mention, the “Others” threshold, per-mention sentiment. Two steps: shows before/after and waits for your confirmation. Does not recode anything already coded.
`plan_apply`	Imports the uploaded file using that plan, with your edits.
`deliverable_create`	Creates a deliverable and returns its download link: coded results in Excel or `.sav`, the codebook in Excel, frequency tables — or one of your saved export templates. Free; never spends credits.
`coding_start`	Starts coding the questions from a previous estimate. Spends credits.

Nothing runs without your confirmation

plan_apply, question_config_update and coding_start always work in two steps:

The first call returns a summary (what will be imported, or which questions will be coded and how many credits it costs) and a confirmation_token.
Claude shows you the summary. The action only runs if you confirm and Claude calls again with that token. The token is valid for 10 minutes, works once, and is rejected if anything changed since the summary.

Two more safeguards:

Credits. coding_start spends credits exactly like coding from the portal. Each action is capped at 5,000 credits and each user at 20,000 credits per day through the connector (limits can be adjusted per organization); larger jobs are started from the portal. Questions that are already coded are never charged again.
Replacing data. plan_apply refuses to import into a project that already has questions. Only with replace_existing: true does it re-import, and that deletes the project’s existing questions and codes — the summary says so before you confirm.

Example prompts

“What needs my attention?”
“I want to upload a new file.”
“Analyze the .sav I uploaded to the FIFA project and propose a coding plan. Don’t code columns P3_5 to P3_10.”
“How much would it cost to code the Chelsea Nubank project?”
“What are people saying in question P5? Show me the top codes with their base.”
“Give me the results in Excel and the codebook for the coffee project.”

What it does not do

It does not delete projects, questions or API keys (the only deletion is the explicit, confirmed replace_existing re-import described above).
It does not apply Refine suggestions: Claude can explain them, but approving, merging codes and editing the codebook is done by the analyst in the portal.
It cannot receive files attached in the chat: ask “I want to upload a new file” and Claude gives you the upload link; come back when the upload reaches the review screen.
It does not add tracking waves (it can check the file first with wave_check). The client’s original .sav with codes appended and the full tab book (which costs credits) are created in the portal.

Pricing

The connector is free. Coding consumes credits exactly as it does in the portal; see your balance and purchases under Usage in Survey Coder.

Remove access

In Survey Coder, go to Settings → Connected apps → AI assistants and click Revoke access. Access stops immediately. You can also remove the connector from Claude’s settings.

Privacy and support

The connector acts with your session and your organization’s permissions. We log which tools were called, when, how long they took and whether they failed, and which project or upload they referred to, to operate and support the service. The contents of your questions, responses and results are not stored in that log.

Privacy policy: surveycoder.io/privacy
Support: support@surveycoder.io