Loopwise / for agentsMCP · OAuth · REST

Your courses, invokable by AI.

Every Loopwise school ships with an MCP server, scoped OAuth, and a REST API. Any agent can read courses, enroll students, or surface content — with the user's consent.

01Surfaces

Three surfaces, one consent model

Pick the integration depth that fits your agent. All three share the same OAuth token and scope boundaries.

mcp.loopwise.com

Hosted MCP server

Every school exposes a Model Context Protocol endpoint with pre-built tools for enrolling students, reading courses, and tracking progress. Agent-friendly schemas out of the box.

connect.loopwise.com

Per-school OAuth

Scoped OAuth 2.0 per school with PKCE required. Agents request narrow permissions — courses:read, students:write — and users consent once. Tokens are revocable anytime.

api.loopwise.com

REST API

The same surface your apps use. Full CRUD for courses, schools, and students. Webhooks for event-driven workflows. OpenAPI spec published.

02Reference

Real code, not slideware

Every sample is copy-pasteable against a live school. Swap in your own subdomain and token.

MCP clientts
import { Client } from '@modelcontextprotocol/sdk/client'

const school = new Client({
  name: 'my-agent',
  url: 'https://mcp.loopwise.com/{school}',
})

await school.connect()
const tools = await school.listTools()
// → [list_courses, enroll_student, get_progress, ...]

await school.callTool('enroll_student', {
  course: 'quantum-101',
  email: 'alice@example.com',
})
03Thesis

Built for the agentic web

The next generation of course platforms will be judged by whether an agent can act on a learner's behalf. Enrol a student. Fetch the next lesson. Refund a purchase.

Loopwise ships all of that as first class — not an afterthought API bolted onto a 2015 course platform.

Explore the protocol reference
04 — Start

Ready to launch your course?

Start free today. No credit card required.

No credit card required.