Operate SubSchool from Codex through MCP
Use typed, permission-aware tools to inspect, create, and update real courses, lessons, exercises, and events without copying generated text between systems.
Inspect context
Each step stays editable, visible, and connected
These product views use example data to show what the teacher actually sees—not an abstract feature diagram.
- Step 01
Connect token
MCP lets Codex perform supported structured actions inside the product where the content will be edited, taught, and assessed.
sourceConnect token
DescriptionBook or PDFVideos＋Add approved source materialPDF, DOCX, video or lesson recording - Step 02
Inspect context
Tools represent course, module, lesson, exercise, event, and workflow actions rather than unrestricted database access.
courseInspect context
AI & PRODUCTDecision-making with evidenceModule 1Frame the decision3 lessons Module 2Collect useful evidence4 lessons Module 3Test the recommendation3 lessons - Step 03
Choose tools
Codex can inspect context, choose a tool sequence, create connected entities, and save the result for teacher review.
practiceChoose tools
Lesson contextInterview evidence and decision risks01 Explain your recommendationExtended answer · 10 pointsIncluded02 Prioritise the evidence gapsScenario · 8 pointsIncluded03 Record a two-minute defenceSpoken response · 12 pointsReview - Step 04
Perform actions
Authentication, permissions, validation, persistence, logs, and data integrity remain platform responsibilities.
responsePerform actions
AssignmentDefend the decision and name the largest uncertainty.▶02:14Student response“The strongest evidence supports option B, but the sample is still too narrow…”
Transcript ready - Step 05
Save draft
Teachers can verify drafts, inspect tool results, and correct or repeat a bounded operation instead of trusting a hidden mutation.
reviewSave draft
AI first pass84%Ready for teacher review- Uses evidence4 / 5
- Explains limitations5 / 5
- Recommendation clarity3 / 5
Teacher feedbackGood reasoning. Add one piece of evidence that could disprove your recommendation. - Step 06
Teacher review
The teacher compares the first pass with the original work, changes the score where needed, writes final feedback, and decides what the learner receives.
reviewTeacher review
AI first pass84%Ready for teacher review- Uses evidence4 / 5
- Explains limitations5 / 5
- Recommendation clarity3 / 5
Teacher feedbackGood reasoning. Add one piece of evidence that could disprove your recommendation.
Generated text should not require manual transfer
MCP lets Codex perform supported structured actions inside the product where the content will be edited, taught, and assessed.
Expose meaningful typed operations
Tools represent course, module, lesson, exercise, event, and workflow actions rather than unrestricted database access.
Coordinate multi-step work
Codex can inspect context, choose a tool sequence, create connected entities, and save the result for teacher review.
Keep security inside SubSchool
Authentication, permissions, validation, persistence, logs, and data integrity remain platform responsibilities.
Review action boundaries and recovery
Teachers can verify drafts, inspect tool results, and correct or repeat a bounded operation instead of trusting a hidden mutation.
Common questions
What can I automate with the codex MCP integration?
Use typed, permission-aware tools to inspect, create, and update real courses, lessons, exercises, and events without copying generated text between systems. MCP lets Codex perform supported structured actions inside the product where the content will be edited, taught, and assessed.
How do I connect the codex MCP integration to SubSchool?
Tools represent course, module, lesson, exercise, event, and workflow actions rather than unrestricted database access. Authentication remains under SubSchool control and the integration receives only the supported operations exposed for the current account.
Can the codex MCP integration create real courses and lessons?
Tools represent course, module, lesson, exercise, event, and workflow actions rather than unrestricted database access. Generated modules, lessons, exercises, criteria, scores, and feedback are saved as editable product objects rather than a block of text to copy elsewhere.
What permissions does the codex MCP integration receive?
The integration does not receive unrestricted database access. SubSchool continues to enforce authentication, account permissions, validation, and persistence for every structured operation.
Can I review changes from the codex MCP integration before publishing?
Authentication, permissions, validation, persistence, logs, and data integrity remain platform responsibilities. You can keep work private as a draft, test the complete flow with example data, and publish or assign it only after review.
How are errors and partial codex MCP integration workflows handled?
Codex can inspect context, choose a tool sequence, create connected entities, and save the result for teacher review. Keep multi-step changes as drafts where possible, inspect the returned result, and retry only the failed operation instead of repeating already completed changes.
Turn the page into a real teaching workflow
Keep the result editable, connect it to learners, and preserve teacher review.