Analyse your SurveyLane results with AI.
A hosted, read‑only MCP endpoint that lets Claude (or any MCP‑capable client) read the surveys and responses in your SurveyLane account — so it can summarise open text, test which differences are significant, find the key drivers, compare segments and write up findings. No SDKs, no glue.
01Quick start
Three steps from zero to chatting with your survey data.
Generate a token
Open Settings → API access and click Generate. Copy the value once — it’s shown only at creation.
Wire up your client
Add the endpoint and Bearer header to Claude Code, Claude Desktop or Cursor — one CLI command or a small JSON snippet.
Ask in plain English
The model decides which tools to call. You describe what you want to learn, not which query to run.
02Install
Drop the endpoint into any MCP‑capable client. HTTP transport, Bearer auth, no SDK.
Add the server with one CLI call. Positional args come before the flags, otherwise the URL gets swallowed by --header.
claude mcp add surveylane https://mcp.surveylane.app \ --transport http \ --header "Authorization: Bearer slk_..."
Verify with claude mcp list — you should see surveylane alongside any other servers.
03Authentication & privacy
Every request other than GET /health must carry a Bearer token. Tokens are personal, read‑only, and shown once at creation.
Read‑only by design
The AI can list and analyse your surveys, results and responses — it cannot create, edit or delete anything. Safe to hand to any MCP client you want to give visibility.
- list_surveys, get_survey
- get_results, get_open_text, get_funnel
- get_responses, whoami
Respondent privacy
For anonymous surveys, respondent names and e-mail addresses are never returned — only aggregates and de-identified answers. For non-anonymous surveys the choice you made on the survey is honoured.
- isAnonymous enforced server-side
- aggregate tools never expose PII
- scoped to your account only
Tokens are per‑user and revocable
Every tool query is scoped to your own data and cannot see other accounts. Revoke a leaked token from Settings → API access — it’s effective immediately.
04Tools · 22
Everything the AI can call. All read‑only. Each returns plain building blocks (counts, distributions, raw text) — the model does the interpretation.
whoami
list_surveys
get_survey (survey_id)
get_results (survey_id, only_complete, filter, segment_by)
get_open_text (question_id, limit, offset)
get_responses (survey_id, only_complete, limit, offset, include_pii, question_ids)
get_funnel (survey_id)
get_crosstab (question_a, question_b)
get_group_summary (survey_id)
get_data_quality (survey_id)
compare_surveys (survey_a, survey_b)
test_significance (survey_id, question_id, group_question_id, group_a, group_b)
get_correlation_matrix (survey_id, group_id)
key_drivers (survey_id, target)
scale_reliability (survey_id)
query_cohort (survey_id, where, aggregate)
get_weighted_results (survey_id, weight_question_id, target_shares)
compute_index (survey_id, items, normalize, segment_by)
auto_insights (survey_id, top_n)
get_verbatims (question_id, link_question_id, min_score, max_score, limit)
response_timeline (survey_id, bucket)
report_bundle (survey_id, driver_target)
05Prompts
Server‑hosted prompt templates the AI invokes directly. In Claude Code: /mcp__surveylane__<name>. One click gives you a full guided analysis instead of having to ask the right questions yourself.
analyze_survey
Analyze a survey
Run a full analysis of a survey's results and write a report with findings and recommendations.
06Example prompts
Real questions you can paste into your AI client — from a quick summary to significance tests, key-driver analysis, cohorts, weighting and pre/post comparisons. The model decides which tools to call and chains them together; you stay in plain English.
Aanmelden interventieperiode survey last get a response?”
07From data to a polished report
Ask your AI for a full analysis and it reads the numbers straight from the MCP tools — then a small script turns them into a branded, board-ready PDF. Here’s the workflow and a sample.
- 1Ask in plain language
“Run a full analysis and write a confidential, group-level report with findings and recommendations.”
- 2The AI calls the tools
It chains
report_bundle,key_drivers,compute_index,test_significanceand more — all read-only, all scoped to your account. - 3A script renders the PDF
Hand the returned numbers to a small ReportLab (or HTML‑to‑PDF) script with your own colours and logo. Re-run it whenever the data changes.
Tools behind the sample: report_bundle, key_drivers, get_correlation_matrix, test_significance, compute_index, get_weighted_results, query_cohort, response_timeline.
22% sit more than 8 hours a day and never do mobility work — a concrete cohort for the intervention. Movement and nutrition carry the most effect.
08Rate limits
Per‑user, sliding 60‑second window. Hitting the limit returns a clean tool error with a retry_after_seconds hint — not an HTTP 429 — so your AI client can back off without breaking the conversation.
Counted across all of your tokens, so minting more tokens can’t multiply the budget. All tools are pure database reads.
Read‑only this version. The scope column exists so write tools can be added later behind an explicit upgrade.
Backoff hints, not HTTP 429
The MCP SDK has no transport‑level retry semantics. AI clients DO read the error text — the rejected response includes a precise retry_after_seconds.
09FAQ
report_bundle, key_drivers, compute_index …); a small script then turns those into a branded PDF. See the Reports section for a worked example.