Setup

One token, one endpoint.

QuizMCP is an MCP server over HTTP. Any client that speaks MCP can reach your bank — there’s nothing to install.

Get a token

In the portal, open Settings → Tokens and create one. A token is scoped to exactly one workspace — so a token for your personal bank can never read your club’s, and vice versa. Treat it like a password.

Open the portal

Add the server to your client

The endpoint is https://mcp.quizmcp.com/mcp. Pick your client below — the shape is the same everywhere: a URL and a bearer token.

Claude Codeshell

claude mcp add --transport http quizmcp \
  https://mcp.quizmcp.com/mcp \
  --header "Authorization: Bearer qmcp_your_token_here"

Claude Desktoptext

Settings → Connectors → Add custom connector

  Name  quizmcp
  URL   https://mcp.quizmcp.com/mcp

Paste your token when it asks to authenticate.

Any MCP client (JSON config)json

{
  "mcpServers": {
    "quizmcp": {
      "type": "http",
      "url": "https://mcp.quizmcp.com/mcp",
      "headers": {
        "Authorization": "Bearer qmcp_your_token_here"
      }
    }
  }
}

Know which workspace you're in

Every tool takes an optional workspace argument. Left out, it uses the personal workspace your token belongs to — so a search never silently spans your club. Name a workspace explicitly when you want to reach across.

In conversationtext

"which brand-origin questions have I used?"
   → your personal workspace

"pull the audio round from Bangalore QC"
   → names the club workspace explicitly

Say what you want

That’s it. No syntax to learn — your client picks the tools. Try “read this deck and add anything I don’t already have”, or “build me four rounds from questions I haven’t used since 2024”.

Reference

Every tool it exposes.

Thin wrappers over storage. None of them think.

`question_search`	Find questions by topic, tag, status, or recency.
`question_create`	Write questions to the bank, one or many.
`question_update`	Edit a question; the previous version is kept.
`seed_create`	Park a half-formed idea before it evaporates.
`deck_extract`	Raw text and slide images from a PPTX or docx. No interpretation.
`media_upload`	Store an image or audio file, hashed and addressable.
`set_compile`	Assemble questions into rounds, with scoring and rules.
`export_pptx`	Render a deterministic deck plus a printable run-sheet.
`publish_questions`	Copy questions out to a shared or club workspace.
`pull_questions`	Copy questions in, with duplicate detection.

You write the questions. Your AI and your bank do the rest.

Connect your AIOne token, one endpoint.