Skip to content
For AI assistants · ChatGPT, Claude and Codex

Bring Wizzist to the assistant you already use.

Your assistant carries the conversation. Wizzist keeps the plan, the practice you choose to save, your checks and your next step. This page is the setup guide for people and for agents; the same content is at /agents.md as plain Markdown.

Wizzist in Claude Wizzist in Codex The ChatGPT journey How connected data is handled
Read this first

Status on this page is honest.

Available works today. Pilot is live for admitted pilot accounts only. Planned waits on a registration, deployment or review step Wizzist has not completed. Nothing here installs itself or connects an account; every connection goes through a Wizzist sign-in you approve.

Who can connect: You need a Wizzist student account. A planner key works for any account that can open Settings. The learning connector admits pilot accounts only for now; until self-service admission lands, connecting through it needs Wizzist to admit your account.

Two ways in

One learning service, two MCP endpoints.

Both speak MCP over Streamable HTTP with JSON responses. They differ in what they expose and how they authenticate.

Learning

pilot

https://app.wizzist.com/api/v1/learning/mcp

Auth
OAuth 2.1 with PKCE; registered public clients only
Tools
get_profile, get_study_context, today, get_study_source, propose_prep_plan, selected practice saves, canonical checks

Live, and admits pilot accounts only. Discovery is at https://app.wizzist.com/.well-known/oauth-protected-resource. Client self-registration (CIMD, dynamic registration) is not offered; each host connects with the client ID Wizzist registered for it.

Planner

available

https://app.wizzist.com/api/v1/planner/mcp

Auth
Personal planner key as a bearer token, created in Settings
Tools
today, plans, propose_prep_plan, schedule_study_event, set_learning_goal

Read-only or read-and-write keys. Proposed plans still wait for acceptance in Wizzist. This endpoint exposes planner tools, not the learning tools.

Setup by host

Copy the step your assistant needs.

Create a planner key in Wizzist Settings under AI assistants first. Keep it out of chat; put it in an environment variable and let the command read it from there.

Claude Code

available

Your planner from the terminal, with a personal planner key.

Works today for any Wizzist account: Claude Code reads today's steps and your plans, and can propose a plan if the key allows writes.

  1. Create a planner key in Wizzist Settings under AI assistants and export it as WIZZIST_PLANNER_KEY. 
  2. claude mcp add --transport http wizzist-planner https://app.wizzist.com/api/v1/planner/mcp --header "Authorization: Bearer $WIZZIST_PLANNER_KEY"
  3. Ask Claude Code what you should do today; it calls the planner's today tool. A plan it proposes waits for your acceptance in Wizzist.

After deployment: The learning connector is a later phase for Claude Code: it signs in with its own client metadata and a localhost callback, which Wizzist's authorization server does not accept yet. When it does, the command is claude mcp add --transport http wizzist https://app.wizzist.com/api/v1/learning/mcp, followed by the Wizzist sign-in it opens.

Codex

available

Your planner from the Codex CLI, with a personal planner key.

Works today for any Wizzist account: Codex reads today's steps and your plans, and can propose a plan if the key allows writes.

  1. Create a planner key in Wizzist Settings under AI assistants and export it as WIZZIST_PLANNER_KEY. 
  2. codex mcp add wizzist-planner --url https://app.wizzist.com/api/v1/planner/mcp --bearer-token-env-var WIZZIST_PLANNER_KEY
  3. Ask Codex what you should do today; it calls the planner's today tool. A plan it proposes waits for your acceptance in Wizzist.

After deployment: The learning server follows one deployment: the wizzist-codex client registration. After it, an admitted pilot account runs codex mcp add wizzist --url https://app.wizzist.com/api/v1/learning/mcp --oauth-client-id wizzist-codex, then codex mcp login wizzist, and approves the Wizzist sign-in that opens in the browser.

claude.ai and Claude Desktop

planned

A custom connector to the learning endpoint, added once in Settings.

Not yet: the connector cannot authorize until Wizzist deploys the wizzist-claude client registration. After that it admits pilot accounts only.

Connector URL
https://app.wizzist.com/api/v1/learning/mcp
OAuth client ID
wizzist-claude
OAuth client secret
leave blank
  1. Open Settings, then Connectors, then Add custom connector.
  2. Paste the connector URL. Under Advanced settings enter the OAuth client ID wizzist-claude and leave the client secret blank.
  3. Choose Add, then Connect, and approve the Wizzist sign-in and permission review.
  4. The same connector works in Claude Desktop once it is added on claude.ai.

After deployment: Deploying the wizzist-claude registration turns this on for admitted pilot accounts. When Wizzist later advertises client metadata, the client ID field becomes optional; the URL stays the same.

ChatGPT

planned

The Wizzist plugin, in private pilot; see the ChatGPT page for the journey.

Not yet: the plugin is a private pilot and is not listed in the ChatGPT directory.

  1. Install Wizzist from the ChatGPT plugin directory when it is listed.
  2. Connect your Wizzist account through ChatGPT's own sign-in prompt.
  3. The plugin's skills handle setup and study; nothing to paste.

After deployment: Listing in the ChatGPT directory follows OpenAI's review of the submitted package.

What every assistant must honor

Wizzist keeps the record. The assistant helps.

  • Help can begin without a plan or a saved Notebook page.
  • A plan the assistant proposes waits for the learner to accept it in Wizzist.
  • Save only the practice the learner selects; never the whole conversation.
  • Reported practice is labeled as reported. It is not independent mastery.
  • Wizzist owns checks, grades and the learning record. Assistants read results; they do not write them.
  • Purchases and credit top-ups are not available through an assistant.
For any MCP-capable assistant

Paste this after you add an endpoint.

It tells the assistant where to start and what it may not claim. Wizzist does not support other assistants beyond ChatGPT, Claude and Codex yet, but the planner key path and this prompt work with any host that can send a bearer header. 

You are connected to Wizzist, my study planner and learning record, through its MCP server. Start by calling `today` to see what I should do now. Help me with homework without requiring a plan. If you propose a plan, tell me it waits for my acceptance in Wizzist. Only save practice I explicitly ask you to save, and describe it as reported practice, not mastery. Do not claim to read my past conversations, award mastery, or buy anything. If a tool is missing or denied, say so and keep helping without it.
Connected assistant support Terms of service