Integrations

Repitio Integrations

Connect AI assistants to Repitio Study Room so they can create subjects, validate question bundles, and import study questions after your approval.

Repitio's MCP server is available today. Connect Claude or ChatGPT in your browser as a custom connector, or wire up any MCP-compatible developer tool. One-click listings in Claude's connector directory and the ChatGPT apps directory are pending Anthropic and OpenAI review.

For everyone

Advanced users

Add Repitio as a custom connector in Claude or a Developer Mode app in ChatGPT — no coding. Generate and import questions after your approval.

Jump to setup →

For developers

Developers

Connect Claude Code, Codex CLI, Cursor, Gemini CLI, and other remote-MCP tools to the Repitio endpoint.

Jump to setup →

For everyone

Connect Claude or ChatGPT in your browser

No coding required. You'll need a Repitio subscription for your Study Room plus a supported Claude or ChatGPT plan. After connecting, ask the assistant to generate questions — it validates and previews them, then imports only after your approval.

Claude — custom connector

Works on Claude Free, Pro, Max, Team, and Enterprise. Free accounts can add one custom connector.

Open Customize → Connectors.
Click +, then Add custom connector.
Paste the Repitio MCP URL https://repitio.io/mcp and click Add.
Click Connect and approve the Repitio permissions.
In a chat, open the + menu (lower left) → Connectors, enable Repitio, then ask it to generate questions and import after your approval.

Team or Enterprise: an owner adds the connector once under Organization settings → Connectors; members then click Connect.

ChatGPT — Developer Mode app

Works on ChatGPT Plus, Pro, Business, Enterprise, and Education on the web.

Open Settings → Apps → Advanced settings and turn on Developer mode.
Click Create app, then enter a name, a description, the MCP URL https://repitio.io/mcp, and set Authentication to OAuth.
Approve the Repitio permissions, then toggle on the tools you want.
In a conversation, choose Developer mode from the + menu, select the Repitio app, and ask it to generate questions and import after your approval.

Developer Mode is a beta feature with full read/write MCP access — review each action before approving.

One-click listings in Claude's connector directory and the ChatGPT apps directory are pending Anthropic and OpenAI review. Until then, the steps above are how to connect today.

For developers

MCP server for AI tools

Connect any MCP-compatible client to Repitio's remote MCP server. The quick start, capability matrix, per-tool setup, and troubleshooting below are for CLI and coding agents.

MCP server quick start

Connect any supported AI tool to Repitio's remote MCP server, including Codex CLI and Claude through its custom connector.

MCP endpoint


            https://repitio.io/mcp

Transport

Streamable HTTP-style JSON-RPC POST

Authentication

OAuth 2.1 authorization code + PKCE, or bearer plugin token

Add Repitio as a remote HTTP MCP server using the exact endpoint https://repitio.io/mcp.
Let your client perform OAuth discovery and dynamic client registration. Repitio advertises metadata through /.well-known/oauth-protected-resource/mcp and /.well-known/oauth-authorization-server.
Approve the scopes shown by Repitio. Import tools require studyroom:write; schema-only tools require schema:read.
Ask your AI coding tool to create a Repitio question bundle, validate it, show you the preview, and import only after you approve.

{
  "mcpServers": {
    "repitio": {
      "type": "http",
      "url": "https://repitio.io/mcp"
    }
  }
}

Some clients use serverUrl or httpUrl instead of url. Use the client-specific examples below.

Supported MCP capabilities

Capability	Status
JSON-RPC `initialize`, `tools/list`, `tools/call`	Supported
`resources/list`, `resources/read`, `prompts/list`, `prompts/get`	Supported
OAuth dynamic client registration + PKCE	Supported
Server-sent events on `GET /mcp`	Use HTTP JSON-RPC POST instead
JSON-RPC protocol batch requests	Send one MCP request per HTTP POST. This does not limit question imports: one validation or import can still include a bundle with multiple questions.

MCP-compatible AI tool setup

Use these examples to connect your AI tool directly to Repitio's MCP server today.

Claude Code ⌄

Add Repitio as a remote HTTP MCP server, then use /mcp in Claude Code if you need to complete OAuth.

claude mcp add --transport http repitio https://repitio.io/mcp

Codex CLI ⌄

Add Repitio to ~/.codex/config.toml or a trusted project-scoped .codex/config.toml, then run codex mcp login repitio if Codex does not start OAuth automatically.

[mcp_servers.repitio]
url = "https://repitio.io/mcp"

Cursor ⌄

Add this to user-level ~/.cursor/mcp.json or project-level .cursor/mcp.json.

{
  "mcpServers": {
    "repitio": {
      "type": "http",
      "url": "https://repitio.io/mcp"
    }
  }
}

Gemini CLI ⌄

Add this to ~/.gemini/settings.json or your workspace .gemini/settings.json.

{
  "mcpServers": {
    "repitio": {
      "httpUrl": "https://repitio.io/mcp",
      "authProviderType": "dynamic_discovery",
      "oauth": {
        "enabled": true,
        "scopes": ["schema:read", "studyroom:read", "studyroom:write"]
      }
    }
  }
}

Gemini CLI commonly uses a localhost /oauth/callback redirect; Repitio accepts that path.

Google Antigravity ⌄

Add this to ~/.gemini/antigravity/mcp_config.json, ~/.gemini/antigravity-cli/mcp_config.json, or workspace .agents/mcp_config.json, depending on the Antigravity product you are using.

{
  "mcpServers": {
    "repitio": {
      "serverUrl": "https://repitio.io/mcp"
    }
  }
}

Repitio accepts Antigravity's hosted OAuth callback https://antigravity.google/oauth-callback.

OpenCode ⌄

Add this to opencode.json, then run opencode mcp auth repitio if OpenCode does not start OAuth automatically.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "repitio": {
      "type": "remote",
      "url": "https://repitio.io/mcp",
      "oauth": {
        "scope": "schema:read studyroom:read studyroom:write"
      }
    }
  }
}

OpenClaw ⌄

OpenClaw supports remote Streamable HTTP MCP servers. If your OpenClaw runtime does not start OAuth automatically for remote MCP servers, create a Repitio plugin/API token and pass it as a bearer header.

{
  "mcp": {
    "servers": {
      "repitio": {
        "url": "https://repitio.io/mcp",
        "transport": "streamable-http",
        "headers": {
          "Authorization": "Bearer <repitio-plugin-token>"
        }
      }
    }
  }
}

Hermes Agent ⌄

Hermes supports remote HTTP MCP servers with OAuth. If your Hermes version accepts direct remote MCP config, use the Repitio endpoint and OAuth mode; otherwise use Hermes' MCP catalog/configure flow and choose a remote HTTP server.

mcp_servers:
  repitio:
    url: "https://repitio.io/mcp"
    transport: "http"
    auth: "oauth"

Repitio MCP tools

get_question_bundle_schema
get_question_bundle_documentation
list_question_bundle_examples
get_question_bundle_example
get_repitio_app_linking_metadata
list_studyroom_subjects
validate_question_bundle_import
import_question_bundle_after_user_approval

Authoring rules for AI clients

Call get_question_bundle_schema and an example before creating a bundle.
Use validate_question_bundle_import first and show the preview to the user.
Call import_question_bundle_after_user_approval only after explicit user approval.
For open-ended test-bank requests, start with about 20 questions per batch. Never send more than 50 importable questions in one validation/import.
Do not ask users for organization IDs. Repitio chooses the authenticated user's default Study Room organization server-side.
Do not create questions with obvious answers where the learner can guess by simple elimination.
If the user does not specify question types, tell them the generated batch will use all supported Repitio structured question types when the content supports them.

Troubleshooting

401 Unauthorized: Start or repeat the client OAuth flow. The 401 response includes a WWW-Authenticate header pointing to Repitio's protected-resource metadata.
Invalid redirect URI: Use a supported hosted callback or a native loopback callback on http://localhost:<port>/callback or http://localhost:<port>/oauth/callback.
Invalid Origin header: Server-to-server clients should omit Origin. Hosted browser clients must use an explicitly allowed origin.
SSE-only client: Repitio currently supports HTTP JSON-RPC POST, not a server-sent-event stream on GET /mcp.