LMS — Features and what they do

MCP (AI assistant layer) — main emphasis

What it is

Named lms-analytics-mcp: a controlled set of actions the AI can run on your behalf against real data (only while you’re signed in).
Works in the browser/app (same login as the rest of the product) and on the desktop for staff who use Cursor or Claude with the local connector; optional default scope to one institution on desktop.
If you’re not logged in, nothing runs. Changes (create/rename/delete org items) only go through if your role allows it—the same rules as the rest of the system.
The assistant can match institution names you type to the right place without you pasting internal codes.

Agents (chat)

Analytics — Read-only: institutions, headcounts, quiz lists, who submitted, leaderboards, score cut-offs, what’s running now, activity over a date range.
Admin — Everything analytics can read, plus add/change/remove institutions, groups, departments, categories, and tags (only where permitted).
Support — Same read-only picture as analytics; answers are phrased more like help-desk guidance.

How people ask → what they get back (5 examples)

Ask: “How many students do we have, and how does that split by department?”
Answer: “Your institution has 842 users. By department: Mechanical 310, CS 280, Civil 152, ECE 100.”
Ask: “For Aptitude Set 02, how many people actually submitted?”
Answer: “416 students have a submission on Aptitude Set 02.” (Can also list who if they ask.)
Ask: “Who did best on Mid-term MCQ? Top few.”
Answer: “Top scores on Mid-term MCQ: Ananya 98%, Rahul 96%, Sneha 95%, …”
Ask: “How many scored at least 80% on Weekly Quiz 3?”
Answer: “127 students scored 80% or higher on Weekly Quiz 3.”
Ask: “What assigned quizzes are live right now?”
Answer: “You currently have 2 ongoing assignments: Gate drill (ends 6 PM today) and Python basics (ends Friday).”

Chat with MCP

Analytics chat — Ask numbers and lists; replies come from live data; past threads are saved.
Same thing in three modes — Analytics (read-only), Admin (read + org changes when allowed), Support (read-only + how-to tone).
Conversations — See past chats, open one thread, delete a thread.

Other

Institutes (institutions)

Create, list, update, and manage institutes.
Registration links built from your configured front-end address.
Licences — See how many seats are allocated, in use, and free; update totals when your plan changes.

Users

List users, profiles, and day-to-day user management (only for roles that are allowed).

Roles and access rules

Roles — Who is staff, student, admin, etc.
Policies — Fine-grained rules for who may view or change what.

Organization

Department — Departments per institution; add, list, edit, remove.
Group — Groups and membership.
Categories — Buckets for content or org structure.
Tags — Labels for filtering and organization.

Questions and quizzes

Question bank — Build and maintain questions.
Quiz — Build quizzes from questions; publish or hold back as needed.
Assigned quiz — Schedule quizzes for cohorts; collect submissions; mark and store results.
Live quiz tracking — While a quiz window is open, students’ apps quietly report which question they’re on and focus events (tab away, etc.). Staff see a live board: who’s active, where they are in the paper, and rough integrity signals. The board updates in real time; many students at once are handled without hammering the server (brief batching on refresh). Works for normal assigned quizzes and public link quizzes; sign-in or link session is required so only the right people stream data.
Public quizzes — Share-by-link quizzes with sessions and submissions handled in the background so the app stays responsive.

Assessments

Assessments — Non-coding tests and structures.
Assigned assessments — Hand out to users or groups; track who finished.
Coding assessments — Code challenges with automatic run/check where configured.
Assigned coding assessments — Assign code tests; collect code runs and results.
Public assessments — Open sessions, start/stop visibility, custom fields on the form, dates and attempts.

Courses and content

Course — Course records and metadata.
Section — Parts inside a course.
Lecture — Lessons inside a section.
Assigned course — Enrol cohorts; track progress where the product supports it.

Problems and practice

Problems — Single coding/problem items (large banks supported).
Problem set — Curated lists of problems.
Assigned problem set — Hand a set to a class; track who did what.

Subscriptions

Institution-level subscription and access limits.

Multiple tenants (instances)

Instance — Separate worlds of data; top-level staff can put users on an instance and see who belongs where.

Trainers

Trainer records tied to institutes and training flows.

Attendance

Attendance tied to sessions, assessments, and quizzes as the product defines them.

Audit

History of important actions for compliance and troubleshooting.

Misc

Small helpers that don’t fit a single box above (including service health checks).

Chatbot (MCP lives here too)

Analytics Q&A backed by real data.
Analytics / admin / support chat modes (see MCP above).
Saved conversations; open or delete old threads.

Docs and operations for teams

Machine-readable description of everything the server can do.
Human-readable docs in the browser (product + sign-in).
Browser access from allowed front-end sites only.
Health — Quick check that the app and database are reachable.

Background processing

Quiz submissions (institution) — Heavy submit work finishes in the background so the student screen doesn’t freeze.
Quiz submissions (public) — Same idea for link-based quizzes.

For developers: path and schema details live in the repo docs and generated reference—this sheet is for non-technical readers.