Strella docs
GuidesDeveloper
Strella docs
GuidesDeveloper
Welcome to StrellaChangelog
Run your first studyHow AI helps you in StrellaGlossary
The Build screenStart with the study setup chatSet up your study detailsWrite research objectivesBuild your screenerBuild your question guideBest practicesAdd survey questions to your interviewAdd a stimulus to your interviewHost a prototype and add it to your interviewAdd a card sortAdd a tree testRandomize sections (A/B variants)Conditional sectionsVersion historyUse the build assistantPreview your interviewUpload an existing discussion guideImport from another study
How the AI moderator worksVoice, language & behaviorRecording modesCustom dictionary & pronunciationCustomize the participant experienceWhat the AI moderator can't do
How recruitment worksSchedule moderated interviewsHire from a participant panelBring your own participantsManage share links & redirectsPass data with URL parametersControl access & schedulingSet quotasApprove, reject & invitePay participants you recruitedReport a participantWatch the funnel
Publish your studyEdit a study after launch
Get oriented in ResultsBring in interviews you ran elsewhereReview a single interviewBrowse analysisCode responsesSee how participants complete on-screen tasksSee how participants sorted your cardsSee how participants use your Figma prototypeUse Strella's AI chatAI chat best practices
Build & share a reportCreate & share a highlight reel
Teammates, organizations & workspacesDelete projectsProject defaultsBilling & creditsConnect FigmaAPI, MCP & AI assistantsParticipant data accessMedia links and who can open themActivity logs
Step typesScreener question typesRecording settingsParticipant statuses & funnel stagesSupported languagesVoice optionsBrowser & device requirements
MCP serverConnect an AI clientTools & skills referenceUse cases & example promptsWhat's newSecurity & privacyFAQ & troubleshooting
Account & adminAPI, MCP & AI assistants
Account & admin

API, MCP & AI assistants

Strella exposes a public REST API, an MCP server, and connectors for Claude, ChatGPT, and Figma Make. Generate keys and configure connections here.

Strella offers three ways to connect from outside the app:

  • REST API: for automating Strella from your own code (creating studies, fetching results).
  • MCP server: lets AI assistants do real work with your research (build studies, run analysis, and pull quotes, themes, and results) by connecting over the Model Context Protocol.
  • Pre-built connectors: turn-key integrations for Claude, ChatGPT, and Figma Make so AI assistants can read your research.

The REST API authenticates with an API key you generate here. The MCP server and the connectors authenticate with your own Strella sign-in, so they need no key.

Steps

  1. Open the home sidebar → Developer

    The Developer page lists API keys and the MCP setup link. Only organization admins can see this page.

  2. Generate an API key

    Click + New API key. Give it a name (so you can identify it later) and pick scopes:

    • Read: fetch studies, participants, interviews, themes.
    • Write: create studies, update settings, manage participants.

    Strella shows the key plaintext once. Copy it now: you can't see it again.

  3. Use the API

    Send requests with Authorization: Bearer <your-key>. The full reference is at https://app.strella.io/docs/api. It lists endpoints, request bodies, and response shapes.

    Strella shows no rate-limit usage in the app.

  4. Connect Claude or ChatGPT via MCP

    The MCP server lets AI assistants work with your Strella data. Connect an AI client walks through each one:

    • Claude: web, desktop, and Cowork, which all share one Connectors flow.
    • ChatGPT: from ChatGPT's plugin directory.
    • Figma Make: pull Strella research into Figma Make.
    • Claude Code: one command in your terminal.
    • Cursor: a config file in your editor.
    • Any other client: add Strella as a custom connector.

    MCP setup does not use an API key. You sign in with your Strella account through a secure OAuth redirect, and the connection has only the permissions you already have.

  5. Revoke a key when needed

    On the Developer page, click the trash icon next to any key to revoke it. Revocation is immediate, and calls with that key return 401.

Your AI clients have access to your research. Ask Claude "what did participants in my last study say about pricing?" and it can answer from the actual data.

Tips

  • One key per use case. If you're connecting both Claude and a CI pipeline, generate two separate keys so you can revoke one without breaking the other.
  • API keys are organization-scoped. Any teammate with admin access can create and revoke them. The keys themselves access every study in the organization.
  • Use cases for the connectors: Use cases & example prompts has worked examples: competitive analysis from past studies, pulling quotes into a doc, etc.

Related

Audit logs

Track API key activity in the org.

Teammates & workspaces

Who has access to generate keys.

Connect Figma

Connect your Figma account so a Prototype step captures where participants click and turns it into a heatmap. Prototype steps work without the connection, and the connection adds the click data.

Participant data access

Control how much participant personal information each teammate and AI tool can read through the Strella API and AI assistants.

On this page

StepsTipsRelated