𝗦𝗸𝗼𝗼𝗹 𝗥𝗘𝗦𝗧 𝗔𝗣𝗜 — 𝗗𝗿𝗶𝘃𝗲 𝗬𝗼𝘂𝗿 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆 𝗙𝗿𝗼𝗺 𝗬𝗼𝘂𝗿 𝗢𝘄𝗻 𝗧𝗼𝗼𝗹𝘀 Everything you do by hand inside Skool — read posts, manage members, create events, pull the leaderboard — your own scripts and automations can now do too. The Skool REST API exposes your community data over plain HTTP, so n8n, Postman, a cron job or any tool that speaks REST can read and write to Skool without a person clicking through the UI. A new "Integration" section in Settings is where it lives. Flip one toggle and the API arms for your account; flip it off and every call stops answering at once — there's no half-on state to forget about. A built-in documentation view lists every available endpoint with its parameters, so you can wire up a request and see the shape of the response without leaving Skool or hunting through a separate doc site. The API speaks the same surface the Extension itself uses — posts, comments, members, events, categories, the leaderboard, community info and more — so anything you've watched a panel do, a script can do on a schedule. Premium-gated; the toggle and the docs view both sit in Settings → Integration. 𝗦𝗸𝗼𝗼𝗹 𝗠𝗖𝗣 — 𝗖𝗼𝗻𝗻𝗲𝗰𝘁 𝗮𝗻 𝗔𝗜 𝗔𝘀𝘀𝗶𝘀𝘁𝗮𝗻𝘁 𝗦𝘁𝗿𝗮𝗶𝗴𝗵𝘁 𝘁𝗼 𝗬𝗼𝘂𝗿 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆 The Model Context Protocol is how AI assistants like claude.ai, ChatGPT and Claude Code plug into outside tools. Skool MCP gives them a door into your community: connect the new MCP server once and an assistant can read and manage your Skool data in plain conversation — "summarize this week's posts", "tag every member who joined in March", "create an event for Friday" — without you scripting a single call. Setup lives next to the REST API in Settings → Integration and is built to be copy-paste simple. A guided panel hands you the server URL, lets you create an access key, and walks you through adding it as a custom connector in claude.ai. From there the assistant signs in once and receives its own short-lived token, so your key never has to live inside another app. You manage your own keys from the same panel. Give each key a label so you remember which tool it's for, see when it was last used, and revoke any of them the moment you stop needing it. Each key is shown exactly once at creation and never again — so it stays as private as your password. Premium-gated, and it rides on top of the same REST surface, so anything the API can do, the assistant can do through it.