Edit your templates from ChatGPT, Claude and other AI apps
By the Workshopy teamUpdated 6 min read
Workshopy has an MCP server, so an AI app you already use — ChatGPT, Claude, Codex, Claude Code — can read and edit your workshop templates for you: turn your notes into steps, add a quiz, rewrite a step, build an interactive animation that explains a point, add an image (a file or a link), go back to an earlier version, and see where your last class got stuck to improve the lesson. It works on your templates and your classes' numbers only. It can't run a class, and it never sees a student's name, their answers or anything they wrote. You connect it once with your Workshopy sign-in and can disconnect it any time.
Connect an app
Every app connects to the same address, https://workshopy.io/mcp. The first time, the app opens Workshopy's sign-in page: sign in, check what the app will be allowed to do, and choose Allow. Connecting is open to every Workshopy account, on every plan.
In Workshopy, Connect your AI at the foot of the sidebar shows the address and the steps for each app below, and tells you when your app is connected.
Workshopy names the app by where the sign-in returns: ChatGPT for chatgpt.com, Claude for claude.ai. Any other app is shown as “an app that calls itself …” with its full return address, because an app's name is only its own claim. Only allow an app you started connecting yourself.
- Claude — Settings → Connectors → Add custom connector, with the address above.
- ChatGPT — Workshopy isn't in ChatGPT's app directory yet. Until it is, turn on developer mode (Settings → Apps → Advanced) and create an app with the address above, choosing OAuth to sign in. On a personal plan ChatGPT connects it read-only: the app can read your templates but not change them. On a Business, Enterprise or Edu workspace it can edit them too.
- Codex and Claude Code — add it from the terminal with the commands below. Codex opens the sign-in page itself; in Claude Code, type /mcp and choose Workshopy to sign in.
- Any other app that connects to remote MCP servers over HTTP with a sign-in (OAuth) — add the address above as a server. The app opens Workshopy's sign-in page the first time.
# Codex
codex mcp add workshopy --url https://workshopy.io/mcp
codex mcp login workshopy
# Claude Code
claude mcp add --transport http workshopy https://workshopy.io/mcpWhat an app can and can't do
The limits are enforced by Workshopy's database, not by the app's good behaviour: a token issued to an app reaches only your templates, your media library and your classes' numbers.
- It can see your templates and the images in your media library.
- It can create templates and edit their steps, quizzes, interactive animations and settings, and add an image to your media library — a file it has, or a public https link.
- It can move a template to the recycle bin or restore one. It can't delete anything for good — the bin keeps a template for 30 days.
- It can list a template's earlier versions — the lesson as it was before each round of changes, yours or an app's, kept for 30 days — and put one back. The lesson it replaces is saved as a version first.
- It can see how a finished class went, as numbers: per step how many finished, got stuck or asked for help and how long it took, quiz results per question, poll counts. Never a student's name, an answer they wrote, the chat or a help note.
- It can't start, run or end a live class, see your students' names or anything they wrote, or change your account, plan or billing.
Your changes are never overwritten
Every template has a revision number that goes up with each change. An app passes the revision it read when it edits; if the template changed in between — you edited it in Workshopy, or another app did — the edit is refused and the app reads the template again first.
If you have the template open in the editor while an app changes it, the editor stops saving and tells you which app changed it, with Load their version or Keep mine. Nothing is merged behind your back.
And before an app changes a template, Workshopy keeps the lesson as it was: the editor's ⋯ → Version history shows it ("Before Claude's changes") and puts it back in one step.
Things to ask
The app reads Workshopy's writing guide on its own, so you can ask in plain words. A few that work well:
- “Turn these notes into a Workshopy workshop with one step per exercise.”
- “Add a three-question quiz after step 2 of my Git basics template.”
- “Rewrite step 4 of my React workshop so a beginner can follow it.”
- “Add the diagram at this link to step 1.”
- “Add an interactive animation to step 3 that shows how binary search halves the list, with Step and Reset buttons.”
- “Which of my templates mention Docker?”
- “Where did my last Flexbox class get stuck? Fix those steps.”
- “Undo the changes you made to my React workshop.”
Limits
To keep the service fast for everyone, each account can make up to 60 requests a minute from AI apps and add up to 30 images an hour (files and links together). When an app goes over, it is told how long to wait.
A template holds up to 200 steps. An image file the app sends can be up to 3 MB; an image from a link must be on a public https address, up to 10 MB. Either way it is resized and stored in your media library like an upload from the editor, and counts toward your storage.
Plans and limits
An app works within your Workshopy plan, exactly like the editor: the Free plan includes 10 workshop templates and 250 MB of media; Pro includes unlimited workshop templates and 5 GB of media. When a limit is reached, the app tells you which one.
Workshopy sells nothing inside ChatGPT, Claude or any other app. Plans are managed in Workshopy, under Settings → Plan.
Privacy
The app receives what it reads to do what you asked: the template's title, description, tags, settings and steps — quiz answers included — the names of your media files, and, when you ask about a class, its numbers (no student's name or words). What happens to it there is up to the app's provider (OpenAI for ChatGPT and Codex, Anthropic for Claude), under the terms you have with them.
Workshopy records which apps you connected and when (until you disconnect them or delete your account), marks changes an app made in the template's history, keeps a per-account request counter for the limit above for two hours, and counts requests per day and app without any account in the count. The privacy policy has the details.
Disconnect an app
Open Workshopy → Settings → Connected apps and choose Disconnect. The app's access ends on its next request, not when its token runs out. You can also remove Workshopy from the app's own settings; that doesn't revoke the access on Workshopy's side, so disconnect here too.
Frequently asked questions
Can the AI app see my students?
Not as people. An app can read how a finished class went as numbers — how many finished each step, got stuck or answered a quiz question right — but never a student's name, an answer they wrote, the chat or a help note, and never a live class. The database refuses the rest, whatever the app asks.
Can an app delete my templates?
It can move a template to the recycle bin, where it stays for 30 days and you (or the app) can restore it. Deleting for good is only possible in Workshopy itself.
Does connecting an app cost anything?
No. Connecting is available on every plan; what the app creates counts toward your plan's limits, as if you had made it in the editor.
What if I'm editing the same template?
Neither side overwrites the other. An app's edit is refused if the template changed after it read it, and your open editor pauses and asks whether to load the app's version or keep yours.
Keep reading
How to write a workshop in Markdown
The complete authoring format: how # headings become steps, what Markdown is supported, and how to import or export a single .md file.
3 min read · 12 Sept 2026
Using WorkshopyHow to add a quiz to your workshop
Write graded quizzes in plain Markdown with #[quiz], ## questions and - [x] answers — and see how correct answers stay hidden.
2 min read · 12 Sept 2026
Using WorkshopyHow to run your first live session
From a Markdown file to a running session: starting it, how participants join with a 6-character code, and pacing the room.
3 min read · 12 Sept 2026
Ready-made lessons from the library
Intro to Git — Snapshots, Branches & Sharing
A short, hands-on first lesson in Git for complete beginners. Students build the mental model one idea at a time — snapshots, the three areas…
10 steps · Free
Teacher trainingMeet Workshopy — A Live, Interactive Product Tour
A live, interactive product tour of Workshopy for new users. It runs as a real Workshopy session, so the audience experiences the product as participants while…
16 steps · Free
Teacher trainingTrain the Trainer: How to Design a Hands-On Workshop
A train the trainer workshop on designing hands-on sessions: write objectives you can see, plan an hour of talks, exercises and checks, find who's stuck.
11 steps · Free
Learn any of them on your own, free, or copy one and teach it live. Browse the library
See it with a class of 24. No sign-up.
The live demo runs the real product with a simulated class. When you're ready, start free.
