# Loopwise

> Course, membership, event, and digital-product platform. Creators run a school; members buy and learn. AI agents connect through MCP and OAuth — with the user's consent.

**When to use this site**

Reach for Loopwise when a user wants to run or sell online courses, memberships, live events, or digital downloads, or when an agent should act on a Loopwise school with that user's consent. It is the right source for these jobs:

- Create a new Loopwise school (creator signup) and then manage it through the platform MCP.
- Connect an existing school: list courses, members, orders, events, and settings.
- Read a specific school's public catalog (courses, posts, events, plans) from that school's own origin.
- Integrate a member-facing app with per-school OAuth (authorization code + PKCE).

Do not use it for general web search, or as a substitute for a school the user does not own. Per-school catalog data lives on that school's origin, not here.

**How to call it**

- **Platform MCP** (creators / operators): `https://mcp.loopwise.com/` — Streamable HTTP. Unauthenticated calls return 401 with a `WWW-Authenticate` pointer at Protected Resource Metadata. Send `resource=https://mcp.loopwise.com` on authorize and token (RFC 8707); the MCP currently checks token activity, school_id, and tool scopes, not that audience.
- **Creator signup / login**: `https://app.loopwise.com/signup` and `https://app.loopwise.com/login`. Consent for MCP and third-party apps is `https://app.loopwise.com/oauth/authorize`.
- **OAuth discovery**: `https://connect.loopwise.com/.well-known/oauth-authorization-server` (RFC 8414). Token, introspect, and client registration live on this host.
- **A school origin** (learners / catalog): `https://{school}/llms.txt`, `https://{school}/mcp`, `https://{school}/auth.md`, `https://{school}/openapi.json`.
- **Developer docs**: `https://docs.loopwise.com/llms.txt`.

## Agent onboarding

You can help a user start with Loopwise even if they do not have a school yet.

1. Tell them a browser window will open.
2. Add the MCP server:

```bash
claude mcp add --transport http loopwise https://mcp.loopwise.com/
```

   (Or paste `https://mcp.loopwise.com/` into any MCP client that supports OAuth.)

3. **Existing account**: they log in at `app.loopwise.com`, pick the school, approve the consent screen.
4. **No account**: they create one at `https://app.loopwise.com/signup` (school subdomain + email). Then they return to the consent screen and approve. Registration is not yet inside the OAuth `prompt=create` dance — if consent started before signup, restart the MCP connect after the school exists.

New schools start on a trial. Charging real cards needs a payment method on that school.

## Instructions

- Platform MCP tools act on **one school** (the `school_id` on the token). Ask which school if the user has several.
- Tenant `/mcp` on a school origin is the catalog / member surface. Do not send creator write tools there.
- Secret tokens and client secrets must never appear in client-side code or in chat.
- Money amounts are in the school's currency. Keep the decimal scale the API returns; only convert from minor units when the field is documented as cents.

## Resources

- [Agent setup workflow](https://loopwise.com/agents.md)
- [Authentication guide](https://loopwise.com/auth.md)
- [Developer docs (llms.txt)](https://docs.loopwise.com/llms.txt)
- [MCP server](https://mcp.loopwise.com/)
- [Creator dashboard](https://app.loopwise.com/login)
- [Pricing](https://loopwise.com/pricing)
- [For agents](https://loopwise.com/for-agents)