Skool MCP Server
Posts, members, courses, events and DMs for your Skool community.
เซิร์ฟเวอร์ MCP แบบโฮสต์
npx add-mcp 'https://cotlet.dev/mcp/v1/skool'ติดตั้งลง Claude Code, Codex, Cursor และอื่นๆ
เอกสาร
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Skool API and MCP server: Let your AI agent run your Skool community.
Skool has no official MCP server, no public API and no developer docs (checked 24 Oct 2026). Cotlet runs 71 Skool tools hosted, over MCP for agents and REST for scripts.
Manage Skool members, posts and reports with your AI agent, n8n, Make, Zapier or a script. Use MCP or the REST API after signing in once in your Cloud Browser.
Connect an AI agent Use the REST API
- Free 7-day trial, no card
- Unofficial, not affiliated with Skool
- Page: https://cotlet.dev/integrations/skool-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Skool. Skool is a trademark of its owner. If Skool's own integrations cover what you need, use them first.
What can you automate in Skool?
- Approve new members
- Post and pin the weekly challenge
- Reply to quiet posts
- Welcome new members
- Report members and MRR
- Clear reported posts
Does Skool have an official API or MCP server?
- The only official link is the Zapier plugin, on the $99 Pro plan, not the $9 Hobby plan: 2 triggers (a new paid member, a Membership Questions answer) and 2 actions (invite a member, unlock a course). One Zapier MCP call uses 2 Zapier tasks.
- The Webhook plugin only takes invitations in. Nothing official approves requests, posts, comments, sends DMs or reads stats.
- Community MCP servers on GitHub do part of it from your own computer, on a session cookie you copy from your browser.
| What you need | Skool + Zapier (Pro) | GitHub MCP server | Cotlet |
|---|---|---|---|
| Approve or decline membership requests | No | Some | Yes, by your rule |
| Post, comment, pin and send DMs | No | Some | Yes, 71 tools |
| Members, churn and MRR | No | Some | Yes, admins |
| Runs with your computer off | Yes | No | Yes, hosted |
| Fixed for you when Skool changes | Yes | No | Yes |
Checked 24 Oct 2026. Sources: Skool Help: Zapier Integration, Zapier Help: Get started with Skool on Zapier, Skool triggers and actions on Zapier, Skool Help: How to use Plugins (Instant membership approval, AutoDM), Skool pricing, Zapier MCP for Skool
How does Cotlet connect to Skool?
- Sign in to Skool. Once, in a browser we run for you.
- Choose MCP or REST. Connect your agent or create an API key.
- Run your Skool actions. Ask your agent or call the REST API.
We never save your password, and anything your members would see waits for your OK.
See it work
Milanote MCP server: automate Milanote with Claude, n8n, Make or Zapier: Sign in once in your Cloud Browser, connect your AI agent, and watch it work in the app, from the first prompt to the result.
Connect Skool to your AI agent or workflow
Connect ChatGPT, Claude, Cursor or Codex through MCP, or use Cotlet in an n8n, Make or Zapier workflow.
Step by step with screenshots for ChatGPT, Claude, Grok and other agents: How to connect Skool to ChatGPT, Claude and any AI agent.
- Enable Skool for agents. Sign up, sign in to Skool in its Cloud Browser and press Enable for agents.
- Add the Skool address. Paste https://cotlet.dev/mcp/v1/skool into your agent's MCP or connector settings.
- Sign in or paste a key. Chat apps sign you in to Cotlet; editors and scripts take an API key from the console.
https://cotlet.dev/mcp/v1 serves every app you connect, Skool included. Enabled Skool after connecting? Refresh the connector.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-skool \
https://cotlet.dev/mcp/v1/skool \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-skool": {
"url": "https://cotlet.dev/mcp/v1/skool",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-skool]
url = "https://cotlet.dev/mcp/v1/skool"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: skool_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: skool_write
How to use the Skool REST API
Create your Cotlet API key
Sign in to Skool in its Cloud Browser and enable it for agents, as in the setup above. In the Cotlet console, open API keys and create a key scoped to Skool; read only is enough for this request.
Save the key in your script environment as COTLET_API_KEY. This is your Cotlet key, not a Skool password or a cookie.
Make your first Skool API request
Replace yourgroup with the URL name from skool.com/yourgroup. This GET request reads one page of members without changing the group.
cURL: list Skool members:
curl "https://cotlet.dev/api/v1/skool/groups/yourgroup/members?limit=30" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read the response and fetch the next page
A successful REST call returns JSON with status: "success" and the tool output in result. This example shows the member data and cursor; call IDs, messages and credit details are omitted.
Example response excerpt:
{
"status": "success",
"app": "skool",
"tool": "list_members",
"result": {
"members": [
{
"name": "Ana Lopez",
"role": "member",
"level": 2,
"points": 14,
"on_trial": false,
"joined_at": "2026-10-01T18:21:00.000000Z",
"member_id": "5e1d7c2a9b8f4e3d6c0a1b2c3d4e5f60",
"profile_url": "https://www.skool.com/@ana-lopez-4127",
"membership_id": "7915f251cdf14c32a201bf1cf7b12c98"
}
],
"next_cursor": "2"
}
}
Read result.members, then pass result.next_cursor as the next request's cursor. Keep the same group and filters; stop when the cursor is null, even if a filtered page has no members.
cURL: next page:
curl "https://cotlet.dev/api/v1/skool/groups/yourgroup/members?limit=30&cursor=2" \
-H "Authorization: Bearer $COTLET_API_KEY"
Skool pages hold up to 30 members. Use limit=30 when reading the whole group: a smaller limit trims each page, and the next cursor still moves to the next Skool page.
Skool workflows with n8n, Make and Zapier
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request with your Cotlet API key; MCP Client Tool for AI Agent workflows. | Schedule a member export, then update your CRM using member_id to avoid duplicates. |
| Make | HTTP > Make a request with your Cotlet API key, or its MCP client. | Read group stats on a schedule and save members, churn and MRR to a reporting sheet. Requires a Skool admin role. |
| Zapier | Webhooks by Zapier > GET or Custom Request, or its MCP client. | Run a scheduled GET for Skool posts, then send the results to your email or Slack steps. |
| Python or Node.js | Call the same REST endpoints from your script. | Read all member pages and save a daily snapshot for your own reports. |
For REST, send Authorization: Bearer <your Cotlet API key> in the request headers and use the GET example above. Set the schedule and destination in your automation tool.
These are workflows you configure, not prebuilt templates or the official Skool connector. Cotlet does not send Skool event webhooks; check for new data on a schedule and keep track of records already handled.
The endpoint and tool reference below lists every REST method, path and input. The REST API guide covers the wider request format, errors and approvals.
Skool API endpoints and MCP tools
Membership requests and members
The request queue with Membership Questions answers, roles, invites and bans. Needs an admin or moderator.
- List membership requests (
list_membership_requests, read): Pending requests to join, with each applicant's Membership Questions answers. Admins and moderators only. - Approve membership request (
approve_membership_request, write, asks first): Let an applicant into the group. Your AutoDM, if set, goes out as usual. - Decline membership request (
decline_membership_request, write, asks first): Decline an applicant's request to join. - List members (
list_members, read): Members of a group with role, level, points and join date, newest first; also banned or churned. - Search members (
search_members, read): Find members of a group by name, as the @mention box does. - Get member (
get_member, read): One member's profile in a group: name, bio, role, level, points and when they were last online. - Invite members by email (
invite_members, write, asks first): Email people an invitation that lets them straight into the group. Admins only. - Remove member (
remove_member, write, asks first): Remove a member from the group, or lift a ban. Admins only. - Ban member (
ban_member, write, asks first): Ban a member from the group, optionally deleting their recent posts. Admins only. - Set member role (
set_member_role, write, asks first): Make a member an admin or moderator, or back to a member. Admins only. - Add membership question (
add_membership_question, write): Add a question people answer when they ask to join the group. Admins only. - Update membership question (
update_membership_question, write): Change a membership question. Admins only. - Delete membership question (
delete_membership_question, write): Remove a membership question. Admins only.
Posts, comments and polls
Text only, no image uploads. Skool keeps 3 pinned posts in the feed.
- List posts (
list_posts, read): Posts in a group's feed, pinned first, then newest, with author, category, likes and comment count. - Get post (
get_post, read): One post with its full text and comments, replies nested under their comment. - Search group (
search_group, read): Search a group's posts, members or courses, as its search box does. - Create post (
create_post, write, asks first): Publish a post to the community feed in a category, as you. - Update post (
update_post, write, asks first): Change the title, text or category of a post you wrote, or any post as an admin. - Delete post or comment (
delete_post, write, asks first): Delete a post or a comment for good: yours, or anyone's as an admin. - Comment on post (
comment_on_post, write, asks first): Comment on a post, or reply to a comment, as you. - Pin post (
pin_post, write): Pin a post to the top of the feed (up to 3) or to a Classroom page (up to 12). Admins only. - Pin comment (
pin_comment, write): Pin a comment to the top of a post's comments, or unpin it. - Turn comments on or off (
set_post_comments, write): Turn comments on a post off, or back on. - Like post or comment (
like_post, write): Like a post or a comment, or take the like back. - List post likes (
list_post_likes, read): Who liked a post or a comment. - Follow post (
follow_post, write): Get notified of new comments on a post, or stop. - Get poll results (
get_poll_results, read): Answers and vote counts of a post's poll, optionally with who voted for what. - Vote on poll (
vote_on_poll, write): Vote in a post's poll, change your vote, or take it back. - List reported posts (
list_reported_posts, read): Posts members reported to the admins, waiting for review. Admins and moderators only.
Skool Chat and notifications
DMs go out under your name and cannot be deleted, so each one asks first.
- List conversations (
list_conversations, read): Your Skool Chat inbox: who, unread count and last message preview. - Get conversation (
get_conversation, read): The latest messages of one Skool Chat conversation, oldest first. - Send message (
send_message, write, asks first): Send a direct message in Skool Chat to a member, starting a conversation if needed. - List notifications (
list_notifications, read): Your Skool notifications: new posts, comments, mentions, likes and approvals, newest first. - Mark notifications read (
mark_notifications_read, write): Mark all your notifications read, everywhere or in one group. - Get AutoDM (
get_auto_dm, read): The welcome message Skool sends every new member, and whether it is on. Admins only. - Set AutoDM (
set_auto_dm, write, asks first): Change the welcome message new members get, or turn it on or off. Admins only.
Classroom
Courses can be created, not deleted: Skool wants a code sent by email for that.
- List courses (
list_courses, read): Courses in the group's Classroom, open or locked for you, with the modules of open ones. - Get course (
get_course, read): One course with its lessons and folders in Classroom order; get_lesson reads a lesson. - Get lesson (
get_lesson, read): One lesson's text and video link. - Create course (
create_course, write): Add a course to the group's Classroom, as a draft or published. Admins only. - Create lesson (
create_lesson, write): Add a lesson at the end of a course, with text and a video link. Admins only. - Update lesson (
update_lesson, write): Change a lesson's title, text or video link. Admins only. - Publish course (
set_course_published, write, asks first): Publish a draft course to members, or turn it back into a draft. Admins only. - Mark lesson complete (
mark_lesson_complete, write): Mark a lesson done in your own course progress, or undo it.
Calendar
Group events by month.
- List events (
list_events, read): Events on a group's calendar, one month or the next ones: title, time, join link and access. - Get event (
get_event, read): One calendar event with its full description, place and access. - Create event (
create_event, write, asks first): Add an event to a group's calendar. Admins only. - Update event (
update_event, write, asks first): Change a calendar event's title, time, place or access. Admins only. - Delete event (
delete_event, write, asks first): Delete a calendar event. Admins only.
Group settings, levels and stats
About page, rules, links, categories, the 9 levels, and churn and MRR in US dollars for admins.
- List groups (
list_groups, read): Skool groups of your account, with your role (or pending), member count and price. - Get group (
get_group, read): A group's name, About text, privacy, price, counts, owner and membership questions. - Get group stats (
get_group_stats, read): Total, new and churned members and monthly recurring revenue for a period. Admins only. - Get leaderboard (
get_leaderboard, read): The group's top 10 members by points for the last 7 days, 30 days or all time, and your rank. - List levels (
list_levels, read): The group's 9 levels with their custom titles and how many members reached each. - Rename level (
rename_level, write): Give one of the group's 9 levels its own title. Admins only. - Update group About text (
update_group_about, write, asks first): Replace the text on the group's About page. Admins only. - List group rules (
list_group_rules, read): The rules of a group, numbered as the group shows them. - Add group rule (
add_group_rule, write): Add a rule at the end of the group rules. Admins only. - Update group rule (
update_group_rule, write): Change the title or text of a group rule. Admins only. - Delete group rule (
delete_group_rule, write, asks first): Delete a group rule. Admins only. - List group links (
list_group_links, read): The links on a group's sidebar, numbered as the group shows them. - Add group link (
add_group_link, write): Add a link to the group's sidebar. Admins only. - Update group link (
update_group_link, write): Change the text or address of a sidebar link. Admins only. - Delete group link (
delete_group_link, write, asks first): Remove a link from the group's sidebar. Admins only. - List categories (
list_categories, read): The feed categories of a group: name, who can post, sort order, post count. - Create category (
create_category, write): Add a category to a group's feed. Admins only. - Update category (
update_category, write): Rename a category or change who can post in it and how it sorts. Admins only. - Delete category (
delete_category, write, asks first): Delete a feed category and move its posts to another. Admins only. - Discover groups (
discover_groups, read): Search Skool's public directory of communities, with members, price and rating. - Get video transcript (
get_video_transcript, read): The spoken text of a video uploaded to a lesson or post, from Skool's captions. - List videos (
list_videos, read): Videos in the group's Classroom lessons and feed posts, uploaded or linked.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/skool-api-mcp-server#tools
Who can see my Skool session, and how do I revoke it?
- What we store. Your signed-in Skool profile, AES-256-GCM, in Finland. Never the password.
- What your agent gets. Skool tools only. No login, no cookie.
- What the session sees. What your Skool role sees: members, their answers, your DMs, MRR for admins.
- What we log. Time, tool and status of each call. No payloads.
- If Skool signs you out. You get an email and a sign-in link. We never log in for you.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call stops.
A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads the queue. Pending requests, 30 a page, with their answers.
- Judges each answer. Against your rule, quoting what it relied on.
- Waits for your OK. Each approval shows up in your Cotlet console.
- Reports back. Approved, declined and left for you, with reasons.
Screenshot: A comment your agent wrote, waiting for Approve and run.
20 of 71 tools ask first: everything members see and every delete. Turn the wait off per tool for scheduled runs, or enable Skool read only.
| Action | Undo |
|---|---|
| Delete a post | No, Skool keeps no trash |
| Send a DM | No |
| Create a course | Unpublish it, cannot delete |
| Pin, like, follow | Yes, same tool |
MCP call:
{
"name": "create_post",
"arguments": {
"group": "yourgroup",
"title": "Week 12 challenge: ship one landing page",
"body": "Post your link below by Sunday. Best three get a live review on Thursday's call.",
"category": "Announcements"
}
}
Response:
{
"post_id": "a3f9c2e1b7d84c06a3f9c2e1b7d84c06",
"status": "published",
"category": "Announcements",
"url": "https://www.skool.com/yourgroup/week-12-challenge-ship-one-landing-page",
"created_at": "2026-10-03T07:00:00.000000Z"
}
REST calls marked asks first wait too: HTTP 202 with status: pending includes an approval_url and a status_url. Approve in the console, then poll the status URL; see the REST API guide. A call your Skool role cannot make fails with APP_PERMISSION_DENIED and costs nothing.
How much do the Skool API and MCP server cost?
About $25 a month for a paid Skool community of about 350 members, 4,320 credits.
| Job | Calls | Credits |
|---|---|---|
| Approve membership requests, daily | 3 × 30 | 900 |
| Reply to quiet posts, daily | 4 × 30 | 1,200 |
| Welcome DMs to new members, weekly | 13 × 4 | 520 |
| Post and pin the weekly challenge | 4 × 4 | 160 |
| Members, churn and MRR report, weekly | 1 × 4 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 4,320 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- One-time packs, valid 12 months, no subscription
The example is the median paid group in Skool Discovery on 24 Oct 2026: 2 to 3 posts a day, about 11 new members a week. Dollars at the $29 pack rate.
Skool automation: Cotlet, GitHub or Zapier?
| Option | What it does | Where it stops |
|---|---|---|
| louiewoof2026/skool-mcp | The most starred community MCP server (52 stars), Node, about 13 tools, on your auth_token cookie. | Runs on your computer, no license, last commit 22 Mar 2026. |
| Other GitHub servers | About a dozen more, most for the Classroom or for reading, all on a session cookie you copy from your browser. | Yours to run and fix; several read Skool's page data, which changes with every Skool build. |
| StickyHive | Hosted MCP with 89 tools, scheduling and DM sequences, also for Circle and Mighty Networks. | Works through a Chrome extension on your session; $29 to $99 a month. |
| Tools4Skool | Member CRM, DM sequences and analytics in a Chrome extension. | API and MCP only on the $249 a month Agency plan. |
Use Skool's official Zapier connector when its built-in triggers and actions cover your workflow. For the broader Skool actions listed here, use Cotlet through your AI agent, n8n, Make, Zapier or a script. Run a GitHub server if you want to maintain the code yourself.
Run our Skool MCP server on your own computer
Our Skool tools are also public on GitHub, as an MCP server and REST API in Python. Run them on your own computer with your own Chrome, test them on your group and read how each tool talks to Skool. It is a trimmed version of what runs on cotlet.dev, free to use in your own business.
- Free for personal use, learning and testing
- Runs while your computer is on, signed in through your own Chrome
- You update it yourself when Skool changes
- License Elastic 2.0: free in your own business; ChatGPT, your phone and 24/7 runs need hosted Cotlet
- Code: https://github.com/cotletdev/skool-api-mcp-server
Who runs Cotlet
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), working since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Skool was the first app on Cotlet. Questions go to contact@cotlet.dev.
Skool API and MCP: frequently asked questions
How do I get access?
Sign up free at https://cotlet.dev, open Skool under Integrations in the console and sign in to Skool in its Cloud Browser. Your free trial starts when you sign up, no card needed.
How do I connect Skool to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Skool once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Skool account through Cotlet, in their phone apps too.
What can ChatGPT do in Skool?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Skool: auto-approve membership requests; schedule a weekly post and pin it; reply to posts nobody answered. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need Skool's Pro plan or Zapier?
No. Cotlet works in your own Skool account and does not use the Zapier plugin, which Skool limits to the Pro plan. Your role in the group still counts: approvals need admin or moderator, pins and group stats need admin, and a call without the role fails with APP_PERMISSION_DENIED. list_groups shows your role in each group.
What can it not do yet?
Posts, comments, lessons and DMs are text only: nothing uploads images, files or videos (a lesson takes a video link), and a chat message cannot be deleted once sent. Courses can be created but not deleted, because Skool asks for a code sent by email. Moderator roles and turning the AutoDM on or off need Skool's Pro plan. Nothing touches your Skool account itself: password, email, profile, payments and payouts stay in Skool. Not built yet: reordering categories, rules and links, group switches such as lockdown or minimum level to post, per-member course unlocks, reviews and live calls. get_group_stats gives MRR in US dollars, and for 90 days members_new comes from Skool's monthly members chart.
Does Skool have webhooks?
Only one way in. The Webhook plugin on the Pro plan takes invitations from an outside checkout; Skool sends no events out, and the 2 Zapier triggers are polled. To react to new requests or posts, run your agent on a schedule and read the queue or the feed.
Does it work on the Skool Hobby plan?
Yes. Cotlet works in your own account on Hobby or Pro and does not use the Zapier plugin. What Skool keeps for Pro stays Pro: AutoDM and moderator roles, for example.
Is the MCP server different from the REST API?
Only the way in. Both have the same 71 tools, inputs and answers, one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST.
Can I connect Skool to n8n, Make or Zapier through Cotlet?
Yes, through MCP or authenticated REST requests. This uses Cotlet, independently of the native Skool Zapier connector; the workflow examples above show where each route fits.
Can I use the Skool API without ChatGPT or Claude?
Yes. Any script or HTTP automation can call the REST endpoints directly. Use MCP when you want an AI agent to choose and run the actions.
Which key do I use for Skool API authentication?
Use a Cotlet API key, scoped to Skool. The REST setup above shows the bearer header; no Skool developer key is required.
Can an API key give my script more Skool permissions?
No. The key can narrow access, but it cannot expand your Skool role. Read-only keys cannot run writes.
What happens to my data if I leave?
Reset browser deletes your Skool profile from our side, and closing your Cotlet account deletes the browser too. Unused credits stay valid for 12 months from purchase.
Is Cotlet affiliated with Skool?
No. Cotlet is independent and not affiliated with Skool.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.