RooQuiz MCP Server

Remote MCP server for RooQuiz — a lightweight assessment platform for lead capture and viral sharing. Build quizzes with AI-assisted authoring, capture leads from results pages, and analyze funnel conversion — straight from Claude, ChatGPT, Cursor, or any MCP client.

• Endpoint: https://payload.rooquiz.com/api/mcp (Streamable HTTP)
• Auth: OAuth 2.1 — authorization code + PKCE with dynamic client registration. Sign in with your RooQuiz account when your client prompts you; no API key needed.
• Registry name: com.rooquiz/rooquiz-mcp

Connect

One-click: VS Code · VS Code Insiders · Cursor

Claude Code

claude mcp add --transport http rooquiz https://payload.rooquiz.com/api/mcp

claude.ai / ChatGPT — add a custom connector and paste the endpoint URL.

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "rooquiz": {
      "url": "https://payload.rooquiz.com/api/mcp"
    }
  }
}

VS Code / GitHub Copilot (.vscode/mcp.json)

{
  "servers": {
    "rooquiz": {
      "type": "http",
      "url": "https://payload.rooquiz.com/api/mcp"
    }
  }
}

What you can do

• Quizzes — create knowledge quizzes, scored quizzes, and "which X are you" outcome quizzes; edit questions, scoring formulas, and dimension analysis; start from templates
• Translations — one source form, mirrored translations in any language
• Leads — list, tag, assign, and comment on leads captured from quiz results pages
• Respondents & records — look up respondents, submissions, stats, and funnel analytics
• Bookings — review and reschedule bookings made through quiz results pages
• Team — switch active team, invite members, manage question banks and categories

All tools act within the team your session is bound to.

stdio bridge

Hosts without native HTTP transport (Claude Desktop, older MCP clients) and registry crawlers that build a container can go through the bridge in bin/rooquiz-mcp.mjs — dependency-free, Node 18+. Everything above is a better path if your client speaks HTTP.

node bin/rooquiz-mcp.mjs           # or: docker build -t rooquiz-mcp . && docker run -i --rm rooquiz-mcp

Env	Default	Purpose
ROOQUIZ_MCP_URL	https://payload.rooquiz.com/api/mcp	Endpoint override
ROOQUIZ_TOKEN	(unset)	Bearer token — required to call any tool

Every method needs a token, initialize included: without one the server answers 401 with a WWW-Authenticate header pointing at the resource metadata. Clients with native HTTP transport get this for free through OAuth; the bridge has nowhere to run a browser flow, so give it a personal access token.

With no token set the bridge still completes a handshake and answers tools/list, reading both from bin/introspection.json — a snapshot of what the hosted server returns. That is there for registry crawlers, which build this container with no credentials and judge the server by whether it introspects; tools/call still goes upstream and still 401s. Once a token is set nothing is served from the snapshot: every message is forwarded, so a stale file can never shadow live data. Refresh it after changing tools:

ROOQUIZ_TOKEN=rqp_live_xxx node scripts/snapshot-tools.mjs

Support

Questions or issues: support@rooquiz.com

---

This repository carries the server.json manifest published to the official MCP Registry, plus the MIT-licensed stdio bridge. The hosted server implementation itself is closed source.