MCP concepts

Connecting

Private-beta access is provisioned by Juno. After approval, add the hosted server to the client configuration with the issued API key as a bearer token. The server is stateless and authorises every call independently. A key environment is separate from a study’s Test mode or Live mode.

Use whoami to identify the Juno-issued key — organisation, key environment, and scopes.

// Any MCP-native client — e.g. a .mcp.json / mcpServers entry
{
  "mcpServers": {
    "juno": {
      "type": "http",
      "url": "https://api.heyjuno.co/v1/mcp/",
      "headers": { "Authorization": "Bearer <issued-api-key>" }
    }
  }
}

Tool results

Each tools/call result contains REST-shaped JSON serialized in a text content block. Long-running tools return a job_id; use the matching status tool until the job is ready.

Files

Files support Create study or Update study. MCP has no upload tool. Upload files over REST first, then pass their file_ids to create_study or refine_study.

Export interviews

Start and monitor a Live-mode export with MCP. Download the completed file over REST.

Full endpoint reference