Loopwise / for agentsMCP · OAuth · REST

Your courses, invokable by AI.

Creators connect at mcp.loopwise.com. Every school origin also ships a catalog MCP, /auth.md, and OpenAPI. Agents act with the user's consent — never with a pasted secret.

01Surfaces

Three surfaces, one consent model

Creator MCP and OAuth need a browser consent on app.loopwise.com. A school's public catalog MCP and markdown routes do not.

mcp.loopwise.com

Creator MCP

Platform MCP for the school operator. Connect with OAuth; tools cover courses, members, orders, events, and settings. Each school origin also mounts a catalog MCP at /mcp.

connect.loopwise.com

OAuth 2.0 / OIDC

Authorization server metadata at /.well-known/oauth-authorization-server. Consent is on app.loopwise.com; token exchange is here. PKCE S256 required.

docs.loopwise.com

Docs and OpenAPI

Agent-readable docs at /llms.txt. Every school origin publishes its own /openapi.json, /auth.md, and markdown catalog at /api/md/*.

02Reference

Real code, not slideware

Copy-paste against live hosts. Swap in a school origin for catalog calls.

MCP clientbash
claude mcp add --transport http loopwise https://mcp.loopwise.com/

# Creator MCP. The user logs in (or first creates a school at
# https://app.loopwise.com/signup). Send resource=https://mcp.loopwise.com
# (RFC 8707); the MCP does not yet enforce that audience.
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.