survey_list
List all surveys owned by or shared with the authenticated user
LABSCO SUMMARY
Separating the surveys scope from the responses scope is the right cut for research data.
Building a survey and reading what people answered are different sensitivities — the second is respondent data. Having them as separate scopes means an agent that drafts questionnaires need never see a response. Add resource indicators on top, and this is one of the more carefully specified authorisation setups in the directory. The AI-draft mode is convenient; the working-draft model is what keeps it from publishing something half-written.
What it is
Empirio's endpoint for their survey platform. Sixteen tools covering the lifecycle: list what exists, read the full design, create a draft manually or with AI, and edit it before it goes out.
What you get
- survey_list — surveys you own or that are shared with you
- survey_get — the full design: questions, settings and layout
- survey_create — a new draft, manual or AI-generated
- survey_edit — change the working draft
- And the remaining tools, covering responses and the rest of the lifecycle
Requirements
OAuth 2.1 with PKCE, dynamic client registration and resource indicators, with scopes split into surveys and responses. Bearer keys beginning sk_live_ are also accepted for REST use.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Drafting a questionnaire
Create the draft in AI mode, then edit it before anything is sent.
02
Reviewing an existing survey
Read the full design — questions, settings, layout — rather than opening the builder.
03
Keeping respondent data out of reach
Grant the surveys scope alone when the agent only needs to build.
16 tools
Listed in project docs. Your client may show a different list.
survey_get
Get full survey details including questions, settings, and design
survey_create
Create a new survey draft (manual or AI mode)
survey_edit
Edit the working draft
survey_publish
Publish an existing draft or update a live survey from the working draft
survey_duplicate
Clone a survey as a new unpublished draft
survey_delete
Permanently delete a survey and all its data
survey_unpublish
Unpublish a live survey and move it back to draft status
responses_list
List paginated responses with optional date and answer filters
responses_aggregates
Per-question aggregate statistics (counts per answer)
responses_crosstab
Cross-tabulate answers between two survey questions
responses_questions
Get question definitions for a survey
responses_survey_stats
Survey statistics — views, starts, completions, incompletes, avg. duration
responses_delete
Delete responses by ranked row numbers or delete all
responses_export
Export responses as CSV, XLSX, JSON, or SPSS
responses_export_charts
Export charts as PowerPoint (editable or image-based), PDF, Word, ZIP of PNGs, or chart JSON
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1 sign-in to your Empirio account, with separate surveys and responses scopes
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://platform.empirio.ai/mcpRequirements
- OAuth 2.1 sign-in to your Empirio account when your client connects, with separate surveys and responses scopes. Bearer keys beginning sk_live_ also work for REST use.
