Skool API and MCP server: connect Skool to ChatGPT and Claude
Yes, ChatGPT, Claude and other AI agents can work in your Skool account. That includes Cursor, Codex, OpenClaw and any MCP client, plus automations in n8n, Make and Zapier. Ask in plain words, and the AI approves membership requests, posts and comments, answers members, sets up Calendar events and reports new members, churn and MRR. It shows you what it will do first and sends nothing to other people until you say so.
As of November 2026, this repo is the missing piece: 71 Skool tools for AI assistants and scripts.
What you can ask
Show me pending membership requests and approve the ones whose answers mention a business.
Which posts from the last 7 days have no comments yet? Draft a reply for each.
Create a Calendar event for Thursday 6pm CET with the Zoom link and pin an announcement about it.
Tell me new members, churn and MRR for the last 30 days.
Two ways to get it
Cotlet is best for community owners and admins who want ChatGPT, Claude or another AI agent to work in Skool for them, with nothing to install.
Start free at cotlet.dev →
Run it yourself
A Skool API and a Skool MCP server you run on your own computer, in Python, on the session of your own Google Chrome. All 71 Skool tools we run in production at Cotlet: members, membership requests, posts, comments, polls, Classroom, video transcripts, Calendar, group settings, Skool Chat and stats.
Skool has no public API and no official MCP server. This repo gives you both:
- MCP server for Claude Code, Claude Desktop, Cursor, Codex and any MCP client, over stdio or HTTP. Setup
- REST API on
http://127.0.0.1:8787/api/v1/skool, with OpenAPI docs at /docs. Setup
- Python:
call("list_members", group="yourgroup"), plus 16 ready scripts in examples/.
Free for your own use, your own business included (license).
[Skool MCP server]
[Python 3.11+]
[License: Elastic 2.0]
[MCP Badge]
Contents
Questions from Skool users
Does Skool have an API?
No. Skool has no public API and no developer docs. The only official connection is the Zapier plugin on the Pro plan, which sends new paid members and Membership Questions answers out, invites a member and unlocks a course. It cannot list all members, approve requests, post, comment, send DMs or read stats. This repo and Cotlet give you 71 Skool tools as a REST API and an MCP server.
Can I get a Skool API key?
Not from Skool for your own account. With Cotlet you get your own API key that works with your Skool account, for scripts, n8n, Make, Zapier or any HTTP client. This repo needs no key: it runs on your computer, on your own Skool session.
Is there an official ChatGPT integration for Skool?
No. Skool has no official ChatGPT or Claude connector. Cotlet is an unofficial one that works today, in the ChatGPT and Claude apps and in any AI agent that takes an MCP server.
How do I connect Skool to ChatGPT?
Sign up at cotlet.dev, sign in to Skool once in your Cloud Browser there, and add Cotlet to ChatGPT, following the steps in your account. Then ask ChatGPT about your Skool like you would ask an assistant. ChatGPT needs a server on the internet, so this repo alone, running on your computer, does not connect to ChatGPT.
Can ChatGPT manage my Skool community?
Yes, with Cotlet. It reads new posts and comments, drafts replies, approves membership requests by your rules, pins announcements and creates Calendar events. Anything posted in your group waits for your OK.
Can I get my Skool members and stats out of Skool?
Yes, with Cotlet: the full member list with join dates and answers, membership requests, churn and MRR, as answers in chat or JSON.
Can I automate Skool with Zapier, Make or n8n?
Skool's own Zapier plugin, on the Pro plan, only sends new paid members and membership answers out, invites a member and unlocks a course. With Cotlet, n8n, Make and Zapier can also list members, approve requests, post, comment and read stats.
Can I use it from my phone?
Yes, with Cotlet: once it is set up, the ChatGPT and Claude apps on your phone can use Skool for you.
Do I need to be technical?
For Cotlet, no: you sign in to Skool and add Cotlet to ChatGPT or Claude, with step-by-step instructions in your account. This repo is for people who are fine with Python and a terminal.
Is my Skool account safe?
Yes. Neither Cotlet nor this repo sees or stores your Skool password. You sign in yourself, the way you always do, and the AI works on that signed-in session. Anything that reaches other people asks for your OK first: in Cotlet by default, here through your MCP client.
Is it free?
This repo is free, also in your own business. Cotlet is free for 7 days with no card, then one-time credit packs from $29, no subscription. Pricing.
I manage Skool for several accounts or clients. Does that work?
Yes, with Cotlet. Each Skool login gets its own connection. Write to [email protected] and tell us how many accounts you manage.
How it works
- You sign in to Skool in your own Chrome, the way you always do.
skool-mcp connect attaches to that Chrome through the Chrome DevTools Protocol, reads the skool.com cookies and saves them to ~/.config/skool-api-mcp/session.json, readable by your user only. It never sees or stores your password.
- Every tool call is a request to Skool's own web app endpoints (
api2.skool.com and the page data of www.skool.com) with those cookies, sent with curl_cffi, which copies Chrome's TLS fingerprint. No headless browser runs.
Skool's session cookie lasts about a year. When Skool signs you out, the server reads the cookies from Chrome again, if Chrome is open with remote debugging on.
Requirements
- Python 3.11 or newer.
- Google Chrome 144 or newer, signed in to Skool. Any Chrome or Chromium works with a debugging port.
- macOS, Linux or Windows.
- The Skool role a tool needs: membership requests need admin or moderator, stats and group settings need admin. Reading members, posts, courses and chat works with any role in groups you belong to.
Install
From PyPI:
MCP clients can also run it with no install: uvx skool-api-mcp mcp.
From source:
With uv: uv venv && uv pip install -e ., then uv run skool-mcp ....
Setting it up with an AI agent (Claude Code, Codex, Cursor)? Open it in this folder and ask it to set up the repo: AGENTS.md tells it every step, and it asks you only for the steps in Chrome.
To update: uv tool upgrade skool-api-mcp (or pip install -U skool-api-mcp), from source git pull && pip install -e .. We copy every change of the hosted Skool tools into this repo.
Connect your Chrome
Option A: your everyday Chrome (recommended)
-
Open chrome://inspect/#remote-debugging in Chrome and switch remote debugging on. Chrome then accepts DevTools connections from programs on this computer, and asks you before each one.
-
Make sure you are signed in at skool.com.
-
Run:
-
Chrome asks whether to allow the connection. Click Allow.
You can switch remote debugging off again afterwards. Leave it on if you want the server to pick up a new session by itself after Skool signs you out.
connect looks for Chrome's DevToolsActivePort file in the default profile folder. For Chrome Beta, Canary or a custom profile folder, pass --profile-dir "<folder>".
Option B: a Chrome with a debugging port
Chrome does not open a debugging port on your default profile, so start a separate one, sign in to Skool there once, and connect to it:
--cdp also takes a ws:// DevTools URL, for example of a Chrome on another machine reached over an SSH tunnel.
Option C: paste the cookie by hand
For a server with no Chrome: in Chrome open DevTools on skool.com, Application > Cookies > https://www.skool.com, copy the value of auth_token, then:
A pasted token is not refreshed on its own. Paste a new one when Skool signs you out.
Check the session at any time:
MCP server
The MCP server lists every tool with its input schema, a description written for agents, and hints: read tools are marked read-only, and tools that post, message or delete are marked so your client asks before running them.
Claude Code
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Cursor
~/.cursor/mcp.json, the same block as Claude Desktop. A ready copy is in mcp.json.
Codex
~/.codex/config.toml:
Over HTTP
skool-mcp serve also serves MCP over streamable HTTP at http://127.0.0.1:8787/mcp, for clients that take a URL:
Then ask your agent things like:
Show me pending membership requests and approve the ones whose answers mention a business.
Which posts from the last 7 days have no comments yet? Draft a reply for each.
Create a Calendar event for Thursday 6pm CET with the Zoom link and pin an announcement about it.
Tell me new members, churn and MRR for the last 30 days.
REST API
Each tool has its own route under /api/v1/skool, the same paths as the hosted API at cotlet.dev, so code written against one works with the other. Path parts and the query string are arguments, and a JSON body adds the rest.
Any tool by name, body as its arguments:
GET /api/v1/skool/tools: every tool with its route, input schema and an example answer.
GET /docs: interactive OpenAPI docs, GET /openapi.json the schema, for n8n, Postman or a generated client.
- Answers are JSON. Lists return
next_cursor; pass it back as cursor for the next page.
The server listens on 127.0.0.1 only. To reach it from another device of yours, set a token, and every request then needs Authorization: Bearer <token>:
Python and the example scripts
Straight from Python, no server needed:
Or one tool from the shell: skool-mcp call list_posts group=yourgroup limit=10, or with a JSON object.
Ready scripts in examples/. Each prints JSON, takes --out file.csv or --out file.json where it makes sense, and --help:
On a schedule, cron on your own computer works while it is on: 0 8 * * * cd ~/skool-api-mcp-server && .venv/bin/python examples/group_stats.py --group yourgroup.
All 71 tools
group is the URL name of a community: yourgroup for skool.com/yourgroup. skool-mcp tools prints this list, skool-mcp tools --json adds the input schemas.
Groups and search
Posts
Comments, likes, polls and moderation
Members
Membership requests
Classroom
Videos
Calendar
Group settings (admins)
Chat and notifications
Never built, on purpose: your Skool sign-in, email, password, name and profile settings, and anything that moves money (plans, payments, payouts, billing). Every request passes a guard that refuses those Skool paths.
Configuration
Security and your Skool account
- Your password never reaches this code. Only cookies are read, and only those of skool.com.
- The session file is yours.
session.json is created with mode 0600. Anyone who has it can act as you on Skool, so keep it out of git and shared folders.
- Local by default.
serve binds to 127.0.0.1 and refuses another address without SKOOL_MCP_TOKEN.
- skool.com only. Requests and redirects outside skool.com are refused.
- Read-only mode.
--read-only or SKOOL_MCP_READ_ONLY=1 exposes the 30 read tools only.
- Actions reach real people. Posts, comments, DMs, invitations and approvals go out under your name. MCP clients ask before running them; a script does not, so try it on a test group first.
- Do not spam. Mass DMs or invitations break Skool's rules and can get your account limited. You are responsible for what runs in your account.
Errors
The REST API answers {"error": "<code>", "message": "..."}. The MCP server returns the same code and message as a tool error.
Self-hosted or hosted
On the hosted version a successful call uses 10 credits for most tools, failed calls are free, and the Cloud Browser uses 50 credits a day while it has an app enabled for agents. Full pricing.
FAQ
Is there a Skool MCP server for Claude, ChatGPT or Cursor?
Yes, this one runs on your machine: skool-mcp mcp for Claude Code, Claude Desktop, Cursor and Codex. ChatGPT and Claude.ai connectors need a public HTTPS URL, which the hosted Skool MCP server gives you.
Is this a Skool scraper?
It does what people want a scraper for (export members, posts and courses to CSV) but does not parse HTML in a headless browser. It calls the same JSON endpoints the Skool web app calls, in your own account.
Can I export Skool members to CSV?
Yes: python examples/export_members.py --group yourgroup --out members.csv. Every member with role, level, points, join date and profile URL, across all pages.
Can I export members of a community I don't own?
Only of groups your account belongs to, and only what Skool shows to your role.
Do I need Skool's Pro plan or Zapier?
No. A few Skool features are Pro only, for example some member roles; the tool says so when Skool refuses.
Why does it need my Chrome?
To read your Skool session without your password. Chrome is used once per sign-in, not for each call.
What happens when Skool signs me out?
Calls fail with auth_expired. With Chrome remote debugging on, the server reads the new cookies on the next call (click Allow when Chrome asks); otherwise run skool-mcp connect again.
Can it run on a VPS or in Docker?
Technically yes, with SKOOL_AUTH_TOKEN. Skool then sees your session from a datacenter IP, which looks less like you. For an always-on setup the hosted version keeps your session in your own Cloud Browser on a fixed IP.
Will my Skool account get banned?
Requests carry Chrome's fingerprint and go out one at a time, as you would click. Nobody can promise a platform never acts. Keep to your normal use and do not send bulk DMs.
Can I use it at work or for my clients?
At work and in your own business, yes, free. You may not offer it to others as a hosted or managed service. For client work, use Cotlet or write to [email protected].
Is it open source?
The source is public under the Elastic License 2.0: free to use and change, also in your own business, but not to resell as a hosted service.
A tool broke or I need another one.
Open an issue with the tool name and the error message.
License
Elastic License 2.0. In short:
- Allowed: using it for yourself and in your own business, free. Changing the code and sharing it under the same license.
- Not allowed: offering it to others as a hosted or managed service, removing the license notices, getting around its limits.
Versions up to 1.x of this repo (the scripts for the hosted API) stay MIT.
[Cotlet]
Maintained by Cotlet (@cotletdev). Skool is a trademark of its owner. This project is unofficial and not affiliated with, endorsed or sponsored by Skool.