On-server help, learning support, and MCP integrations
Staff get navigation help, notice drafts, and text polish, while learners get guided K-12 doubt clearing, explanations, practice, revision, and quizzes from a local AI worker on your server. Optional MCP registry connects approved external tools with role gates and audit. Schoolyi AI is designed for operators, not hype. The in-app assistant answers how-to questions from your help knowledge base, drafts short notices, and polishes text without sending student PII to a public API. Platform admins can register MCP servers for approved integrations while keeping processing on infrastructure you control.
AI assistant & tools in Schoolyi
On-server help, learning support, and MCP integrations. Captured from a demo school so evaluators see the live workspace, not a mock.
Outcomes
Practical results schools report after rolling out this area on the shared calendar and roster.
Teachers find screens faster without opening a separate support queue
Notice drafts start from school tone, not blank pages
Processing stays on your server for sensitive environments
MCP gives a governed path to extend AI without shadow IT
Product truth
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Deep dive
Use these details to turn a product page into an implementation conversation.
Schoolyi AI is designed for operators, not hype. The in-app assistant answers how-to questions from your help knowledge base, drafts short notices, and polishes text without sending student PII to a public API. Platform admins can register MCP servers for approved integrations while keeping processing on infrastructure you control.
Staff get navigation help, notice drafts, and text polish, while learners get guided K-12 doubt clearing, explanations, practice, revision, and quizzes from a local AI worker on your server. Optional MCP registry connects approved external tools with role gates and audit. Because AI assistant & tools shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Everything included in this module, from daily workflows to exports your team relies on.
Role-scoped workspaces so each team sees only the tasks they own.
Focused pages for evaluators comparing specific ai assistant & tools workflows during an SMS rollout.
Workflow
A typical path from setup through daily use on Schoolyi.
Part of the AI assistant & tools workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the AI assistant & tools workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the AI assistant & tools workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the AI assistant & tools workflow on Schoolyi, connected to roster, calendar, and role permissions.
Deep dive
Long-form context for evaluators comparing modules during an SMS rollout.
Schoolyi AI is designed for operators, not hype. The in-app assistant answers how-to questions from your help knowledge base, drafts short notices, and polishes text without sending student PII to a public API. Platform admins can register MCP servers for approved integrations while keeping processing on infrastructure you control.
Staff get navigation help, notice drafts, and text polish, while learners get guided K-12 doubt clearing, explanations, practice, revision, and quizzes from a local AI worker on your server. Optional MCP registry connects approved external tools with role gates and audit. Because AI assistant & tools shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
These areas work closely with ai assistant & tools and share the same calendar, roster, and role model.
Straightforward answers for visitors evaluating the product.
Teachers, Office staff, Platform admins run daily workflows in this module while leadership reviews dashboards and exports when needed.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Dates, working days, and class structure flow from the shared calendar so downstream modules do not maintain parallel date lists.
Set the academic calendar before enabling dependent workflows, then test one holiday and one working-day exception against the resulting attendance or exam view. Keep the school’s local policy as the authority for edge cases.
Schools often launch admissions, roster, and fees first, then add this module when the foundation data is stable.
Choose the next phase only after the team has reconciled one complete operating cycle. Record the data, role, calendar, and support dependencies before widening access.
Role-scoped workspaces show only the tasks each team needs. Most schools run a short coordinator session plus self-serve docs.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
We'll show how this module fits your school's workflows and which teams benefit first.
Already using Schoolyi? Sign in
