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 for compatible AI coding tools and agents that support remote MCP directly. The ChatGPT Plugin and Claude connector are planned integrations and are marked Coming Soon while vendor approval is pending.

Coming Soon

ChatGPT Plugin

Planned official ChatGPT integration. This is not available in production yet while Repitio completes OpenAI review and approval.

Coming Soon

Claude connector

Planned official Claude integration. This is not available in production yet while Repitio completes Anthropic review and approval.

Available Today

MCP-compatible clients

Use the MCP endpoint for Cursor, Gemini CLI, OpenCode, OpenClaw, Google Antigravity, Hermes Agent, and other tools that support remote MCP.

MCP server quick start

Use this section for AI tools that connect directly to remote MCP servers. Official ChatGPT and Claude integrations are coming soon.

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, dry-run 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`	Not required for current HTTP clients; not implemented
JSON-RPC batch requests	Not implemented

MCP-compatible AI tool setup

These examples are for tools that connect directly to Repitio's MCP server today. Official ChatGPT and Claude integrations are coming soon after vendor approval.

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
dry_run_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 dry_run_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 dry run/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.