Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>QubeSurvey extensionNew to Visual Studio Code? Get it now.
QubeSurvey extension

QubeSurvey extension

qubesurvey

|
32 installs
| (0) | Free
QubeSurvey extension for VS Code to write and test QubeScript and Odin locally, and upload versions for team review when hosted access is enabled.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

QubeSurvey extension

Write survey scripts in VS Code with your LLM agent of choice. The QubeSurvey extension includes local MCP tools, language checks and an interview runner. A script gives you and your agent the questions, answer domains and routing in one editable source.

1. Write and test a survey script in VS Code

Install the QubeSurvey extension, then run QubeSurvey: New Hello World Survey for a runnable starting point. Use your agent with the bundled local MCP to adapt it or write a .qube script. Review the changes and run QubeSurvey: Run Interview with invented answers. Local editing and testing require no QubeSurvey sign-in.

For Copilot, run MCP: List Servers and select QubeSurvey. For Antigravity, OpenCode, Codex, Claude Code, Cline or another MCP client, run QubeSurvey: Set up local MCP and review its client-specific configuration. See local MCP setup and the QubeScript quickstart.

2. Upload for team testing and tickets

Run QubeSurvey: Open in QubeSurvey (online) to upload a reviewed version to app.qubesurvey.com. Teammates test the same version and file tickets. The cloud Assistant can propose fixes to supported tickets for review.

3. Run fieldwork

Create and activate a Run using the reviewed version and share its survey link.

4. Export and download the data

Export the Run’s responses and data dictionary. Local and team test answers are separate from fieldwork responses.

See the survey guide and extension manual for setup and current support.

The extension also supports Odin: run Odin surveys on QubeSurvey, or audit and test scripts here before running them on NIPO Fieldwork System. NIPO filenames are conventionally extensionless and end in q (for example p1234q); use a .odin copy (p1234q.odin) for VS Code language recognition. See Using existing Odin scripts.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft