Bring your own agent

Connect the AI agent you already use, such as Claude Code, Claude.ai, Codex, or Cursor, to Teacharium and let it build and revise your lessons for you.

Teacharium runs an MCP server (Model Context Protocol, the standard way AI agents connect to other apps). Once your agent is connected, it can do what the built-in Teacharium assistant does, and more: create a lesson, read a lesson, add sections and steps, build step content, update the abstract and variables, and use your step templates. Everything it does is saved to your lesson as if you had made the change in the editor.

Server address:

https://app.teacharium.io/api/mcp

Connect your agent

Pick your AI client:

claude mcp add --transport http teacharium https://app.teacharium.io/api/mcp

codex mcp add teacharium --url https://app.teacharium.io/api/mcp

{
  "mcpServers": {
    "teacharium": { "url": "https://app.teacharium.io/api/mcp" }
  }
}

{
  "mcpServers": {
    "teacharium": { "url": "https://app.teacharium.io/api/mcp" }
  }
}

npx -y mcp-remote https://app.teacharium.io/api/mcp

Signing in and approving access

When your agent connects for the first time, your browser opens Teacharium:

1. Log in to Teacharium if you aren’t already.
2. The consent page shows which application is asking for access.
3. Click Approve to let the agent work on your behalf, or Deny to cancel.

The agent then works as you. It can see and change the same lessons you can in your organization, and nothing more. You don’t need to create or paste an API key.

To see which agents have access, or to disconnect one, open Settings in Teacharium and go to Connected agents. Click Revoke next to an agent to remove its access. The same settings page also shows the server address and the Claude Code setup command.

What your agent can do

• Create lessons: start a new lesson with a title, tags, and abstract, optionally in a folder such as Science/Biology. Folders that don’t exist yet are created for you.
• Understand a lesson: its sections and steps, the abstract, variables, recent templates, and which components (widgets) the lesson can use.
• Change the structure: create, rename, reorder, move, duplicate, and delete sections and steps.
• Edit lesson details: the title, tags, abstract, and variables.
• Style the lesson: read and change the lesson’s custom CSS, the stylesheet from Lesson Settings that applies to every step (tools get_custom_css, update_custom_css, and edit_custom_css). Agents are told which Teacharium selectors to target and never to hide the lesson navigation.
• Build step content: lay out the step grid, then add, edit, move, and remove components. Content is checked against each component’s settings before it’s saved, just like the editor.
• Use templates: find a step template, apply it, or save a finished step as a new template for your team.
• Undo: list a step’s earlier versions and restore one.

A good way to start is to ask your agent to read the lesson and its abstract first, for example: “Read my Photosynthesis lesson and add a three-step introduction for 5th graders.”

Previewing the result

Your agent can ask Teacharium for a preview link for a single step or the whole lesson. The link opens the current draft in the lesson player without logging in, so agents with a browser tool can look at what they built and fix problems on their own. You can open the same link yourself.

Preview links expire after a short time. Don’t share them publicly.

Staying safe

• Deletions need confirmation. Deleting a section, step, or variable, replacing a step’s whole content, and restoring an older version of a step only happen when the agent explicitly confirms. Agents are instructed to ask you first.
• Open editors are respected. If someone else has the lesson open in the editor, the agent’s changes are refused until they close it. If you have it open, changes are saved but your editor won’t show them until you reload the page.
• No lost edits. The agent sends the version of the step it last read. If the step changed in the meantime, the save is refused and the agent re-reads the step before trying again.
• History is kept. Every change to a step is saved in its history, and every abstract or custom CSS change keeps the previous version.

Agent skills

Skills give your agent Teacharium know-how: how lessons are structured, how to write good steps, the step grid, text formatting, variables, and actions. They come from the same instructions the built-in Teacharium assistant uses.

• teacharium-lessons: lesson structure, the recommended workflow, and safety rules.
• teacharium-step-content: building the content of individual steps.

Install the skills

The skills are published in the public teacharium/agent-skills  repository on GitHub. Claude, Codex, and several other agents can install it as a plugin, which adds both skills and the Teacharium server.

claude plugin marketplace add teacharium/agent-skills
claude plugin install teacharium@teacharium

/plugin install teacharium --marketplace teacharium/agent-skills

codex plugin marketplace add teacharium/agent-skills
codex plugin add teacharium@teacharium

npx skills add teacharium/agent-skills -g

copilot plugin marketplace add teacharium/agent-skills
copilot plugin install teacharium@teacharium

gemini extensions install https://github.com/teacharium/agent-skills --auto-update