Skip to content
Connected learning · Claude

Study with Claude. Keep your learning in Wizzist.

Claude carries the conversation. Wizzist keeps your plan, the practice you choose to save, your checks and your next step. Claude Code can use your planner today; the claude.ai and Claude Desktop connector follows one deployment.

Create a planner key in Settings Every host and endpoint
Where this stands available

Status on this page is honest.

Today: Claude Code works with a personal planner key. Not yet: the claude.ai and Claude Desktop connector, which waits on the wizzist-claude client registration and then admits pilot accounts only.

After deployment: After that deployment, an admitted pilot account can add the custom connector below and Claude on claude.ai and Claude Desktop can read your study context, propose a plan and save practice you select. Nothing changes for Claude Code until its own sign-in is supported.

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.

Set it up

Copy the step your Claude 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.

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.

What crosses the connection

What Claude can and cannot do with Wizzist.

Claude can

  • Read today's steps and your plans through the planner key, and propose a plan or record a test date when your key allows writes.
  • Think with its own model. Assistant tool calls spend none of your Wizzist credits.
  • After the connector authorizes: read your study context, open material you select, propose a plan and save the practice you choose.

Claude cannot

  • Hand photos to Wizzist. Practice photos go through the signed-in Wizzist app.
  • Award mastery or grade. Practice saved from a conversation is labeled reported practice; checks run in Wizzist.
  • Read your past Claude conversations or import them into Wizzist.
  • Buy anything or top up credits.
What every assistant must honor

Wizzist keeps the record. Claude 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.
Your account, your choices

You decide what crosses the connection.

Every connection goes through a Wizzist sign-in or a key you create. Personal Notebook pages and class materials stay private unless you select one source for a specific request. You can revoke a planner key or disconnect the assistant, correct saved practice, or request an export or clearing of your data in Wizzist. Disconnecting stops future access; it does not erase practice already saved.

How connected data is handled Connected assistant support The guide as Markdown