# Skool API and MCP server

> Skool has no public API and no developer docs (checked 10 Oct 2026). The only official connection is the Zapier plugin on the Pro plan, which sends new paid members and Membership Questions answers out and can invite a member or unlock a course.

Community platform for creators and coaches: a discussion feed, courses in the Classroom, a Calendar, member chat and paid memberships in one group.

## What is the Skool API?

Cotlet's Skool API exposes 15 endpoints for your own Skool account: list groups, list members, list membership requests, list posts, get post, list courses, list conversations, get conversation, get group stats, approve membership request, decline membership request, create post, comment on post, send message and pin post. The list_groups endpoint returns Skool groups you belong to, with your role and member count. Each endpoint takes simple JSON inputs like group, limit or cursor and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities)
- **Endpoints:** 15 (9 read, 6 write)
- **Updated:** 2026-10-10

Skool has no public API and no developer docs (checked 10 Oct 2026). Cotlet is a hosted MCP server and REST API for Skool with 15 endpoints (9 read, 6 write): your AI agent signs in as you and does the work.

## Does Skool have an official API?

Skool has no public API and no developer docs (checked 10 Oct 2026). The only official connection is the Zapier plugin on the Pro plan, which sends new paid members and Membership Questions answers out and can invite a member or unlock a course.

| Task | Skool official | Cotlet |
|---|---|---|
| List members | Partly: Zapier only sends new paid members as they join | Yes |
| Read Membership Questions answers | Partly: Zapier sends answers when submitted, Pro plan | Yes |
| Approve or decline membership requests | No | Yes |
| Create posts | No | Yes |
| Comment on posts | No | Yes |
| Send DMs in Skool Chat | No | Yes |
| Pin posts | No | Yes |
| Members, churn and MRR stats | No | Yes |

Sources: [Skool Help: Zapier Integration](https://help.skool.com/article/56-zapier-integration), [Zapier Help: Get started with Skool on Zapier](https://help.zapier.com/hc/en-us/articles/10458381459341-How-to-get-started-with-Skool-on-Zapier), [Skool triggers and actions on Zapier](https://zapier.com/apps/skool/integrations), [Skool Help: How to use Plugins (Instant membership approval, AutoDM)](https://help.skool.com/article/176-how-to-use-plugins)

## For AI agents

```text
Skool has no public API and no developer docs (checked 10 Oct 2026). The only official connection is the Zapier plugin on the Pro plan, which sends new paid members and Membership Questions answers out and can invite a member or unlock a course.
Cotlet provides a hosted MCP server and REST API for Skool: 15 tools (9 read, 6 write).
Access       Request access at https://cotlet.dev/app/signup?app=skool; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/skool
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_groups, list_members, list_membership_requests, list_posts, get_post, list_courses, list_conversations, get_conversation, get_group_stats, approve_membership_request, decline_membership_request, create_post, comment_on_post, send_message, pin_post
Confirm      approve_membership_request, decline_membership_request, create_post, comment_on_post, send_message (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/skool-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=skool (Skool is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Skool once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Skool server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Skool MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Pricing: free 7-day trial with 5,000 credits (no card), then one plan from $29/month for 3,000 credits, each month's credits valid for 3 months; each successful call uses credits for the work it takes. Listing all your Skool courses and their modules with list_courses costs about $0.00001, a thousandth of a credit. Failed calls are free; nothing is charged until access is active.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Skool in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Skool's terms; Cotlet is not affiliated with Skool.
```

## What can an AI agent do in Skool?

Cotlet is best for Skool admins who are not developers and want their AI agent to handle membership requests, posts, member DMs and weekly stats without running or fixing a server.

- **[Auto-approve membership requests](https://cotlet.dev/integrations/skool-api-mcp-server/auto-approve-membership-requests)** (runs: daily): "Go through pending Skool membership requests in yourgroup. Approve applicants whose answers name a business they run, decline obvious spam, and leave everyone else for me with a one-line reason." → `list_membership_requests`, `approve_membership_request`, `decline_membership_request`
- **[Schedule a weekly post and pin it](https://cotlet.dev/integrations/skool-api-mcp-server/schedule-weekly-posts)** (runs: weekly): "Every Monday at 9:00, post this week's challenge in the Announcements category of yourgroup, pin it to the feed and unpin last week's challenge." → `list_posts`, `create_post`, `pin_post`
- **[Reply to posts nobody answered](https://cotlet.dev/integrations/skool-api-mcp-server/reply-to-unanswered-posts)** (runs: daily): "Find posts in yourgroup from the last 3 days with no comments, skip anything from admins, and draft a reply to each that answers the question or asks one follow-up." → `list_posts`, `get_post`, `comment_on_post`
- **[Send new members a personal welcome DM](https://cotlet.dev/integrations/skool-api-mcp-server/welcome-new-members)** (runs: weekly): "For everyone who joined yourgroup this week, send a short welcome DM in Skool Chat that links the first open lesson matching their goal. Skip anyone I already chat with." → `list_members`, `list_courses`, `list_conversations`, `send_message`
- **Answer Skool Chat messages** (runs: daily): "Summarize my unread Skool Chat messages and answer the simple ones." → `list_conversations`, `get_conversation`, `send_message`
- **Weekly members, churn and MRR report** (runs: weekly): "Every Monday, tell me new members, churn and MRR for last week." → `get_group_stats`

## Can Skool automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Skool connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to auto-approve membership requests, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/skool/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/skool/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/skool/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/skool/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Skool.

### list_groups

Skool groups you belong to, with your role and member count. Access: read. REST: `POST /api/v1/skool/list_groups`.

No parameters.

Returns every Skool group your account belongs to, both groups you own and groups you joined. Use the group field from each item as the group parameter of the other endpoints. Member count is the number Skool shows on the group page.

Example response:

```json
{
  "groups": [
    {
      "group": "yourgroup",
      "name": "Landing Page Lab",
      "role": "admin",
      "members": 1284,
      "price": "$49/month",
      "url": "https://www.skool.com/yourgroup"
    },
    {
      "group": "creator-club",
      "name": "Creator Club",
      "role": "member",
      "members": 9310,
      "price": "free",
      "url": "https://www.skool.com/creator-club"
    }
  ]
}
```

### list_members

Members of a group with name, role, level and join date, newest first. Access: read. REST: `POST /api/v1/skool/list_members`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `joined_since` | date | no | Only members who joined on or after this date. |
| `role` | enum | no | all, admin, moderator or member. Default: all. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists members of one group, newest first. Filter by role or by join date to find this week's new members. Level is the Skool gamification level (1 to 9) and points are the likes that count toward it. Pages hold up to 100 members; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "members": [
    {
      "member_id": "m_8c41d2",
      "name": "Ana Lopez",
      "role": "member",
      "level": 2,
      "points": 14,
      "joined_at": "2026-10-01T18:21:00Z",
      "profile_url": "https://www.skool.com/@ana-lopez"
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjUwfQ"
}
```

### list_membership_requests

Pending requests to join, with each applicant's Membership Questions answers. Admins and moderators only. Access: read. REST: `POST /api/v1/skool/list_membership_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists pending requests to join a private group, oldest first, with the answers each applicant gave to your Membership Questions. Only admins and moderators see requests; for other roles the call fails with a permission error. Pass request_id to approve_membership_request or decline_membership_request.

Example response:

```json
{
  "requests": [
    {
      "request_id": "r_51e0aa",
      "name": "Tom Becker",
      "requested_at": "2026-10-03T07:45:00Z",
      "answers": [
        {
          "question": "What are you building?",
          "answer": "A SaaS for dental clinics, launching in November."
        }
      ]
    }
  ],
  "next_cursor": null
}
```

### list_posts

Posts in the community feed, newest first, with author, category, likes and comment count. Access: read. REST: `POST /api/v1/skool/list_posts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `category` | string | no | Only posts in this category. |
| `since` | datetime | no | Only posts created after this time. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists posts in the community feed, newest first, the same order as the feed with the Newest sort. Filter by category or by creation time to see what came in since your last check. Body is a short preview; get_post returns the full text and comments.

Example response:

```json
{
  "posts": [
    {
      "post_id": "a3f9c2e1b7d84c06",
      "title": "Week 12 challenge: ship one landing page",
      "author": "You",
      "category": "Announcements",
      "likes": 23,
      "comments": 7,
      "pinned": true,
      "created_at": "2026-10-03T07:00:00Z",
      "preview": "Post your link below by Sunday..."
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjIwfQ"
}
```

### get_post

Full post with title, body, attachments and the comment tree. Access: read. REST: `POST /api/v1/skool/get_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `post_id` | string | yes | Post ID from list_posts. |

Returns one post with its full body, attachments (images, files, links) and the whole comment tree, replies nested under their parent comment. Use it before replying so your agent sees the full discussion.

Example response:

```json
{
  "post_id": "a3f9c2e1b7d84c06",
  "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.",
  "author": {
    "member_id": "m_0001",
    "name": "You"
  },
  "attachments": [],
  "comments": [
    {
      "comment_id": "c_77ab",
      "author": "Ana Lopez",
      "body": "Here's mine: ana.dev/launch",
      "likes": 3,
      "replies": [
        {
          "comment_id": "c_77b0",
          "author": "You",
          "body": "Love the headline!"
        }
      ]
    }
  ]
}
```

### list_courses

Courses in the Classroom with their modules, unlock rule (open, level or paid) and URL. Access: read. REST: `POST /api/v1/skool/list_courses`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |

Lists courses in the group's Classroom with their modules in order. Unlock rule says who can open each course: open to all members, unlocked at a level, or paid. Use the module URLs in welcome messages.

Example response:

```json
{
  "courses": [
    {
      "course_id": "co_12",
      "title": "Start Here",
      "unlock": "open",
      "modules": [
        {
          "title": "Welcome",
          "url": "https://www.skool.com/yourgroup/classroom/co_12?md=1"
        },
        {
          "title": "Your first week",
          "url": "https://www.skool.com/yourgroup/classroom/co_12?md=2"
        }
      ]
    },
    {
      "course_id": "co_19",
      "title": "Advanced Funnels",
      "unlock": "level 3",
      "modules": []
    }
  ]
}
```

### list_conversations

Your Skool Chat inbox: who, unread count and last message preview. Access: read. REST: `POST /api/v1/skool/list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unread_only` | boolean | no | Only conversations with unread messages. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists your Skool Chat conversations, most recent first, with the other person, unread count and a preview of the last message. Set unread_only to see only what needs an answer.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": "cv_93f1",
      "with": {
        "member_id": "m_8c41d2",
        "name": "Ana Lopez"
      },
      "unread": 2,
      "last_message": "Is the Thursday call recorded?",
      "updated_at": "2026-10-02T16:02:00Z"
    }
  ],
  "next_cursor": null
}
```

### get_conversation

Messages in one Skool Chat conversation, oldest first. Access: read. REST: `POST /api/v1/skool/get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_conversations. |
| `limit` | integer | no | 1 to 100. Default: 50. |

Returns the messages of one Skool Chat conversation, oldest first, so your agent reads the thread in order before answering.

Example response:

```json
{
  "conversation_id": "cv_93f1",
  "with": {
    "member_id": "m_8c41d2",
    "name": "Ana Lopez"
  },
  "messages": [
    {
      "from": "Ana Lopez",
      "body": "Hi! Quick question.",
      "sent_at": "2026-10-02T16:01:00Z"
    },
    {
      "from": "Ana Lopez",
      "body": "Is the Thursday call recorded?",
      "sent_at": "2026-10-02T16:02:00Z"
    }
  ]
}
```

### get_group_stats

Total, new and churned members and monthly recurring revenue for a period. Admins only. Access: read. REST: `POST /api/v1/skool/get_group_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `period` | enum | no | 7d, 30d or 90d. Default: 30d. |

Returns membership and revenue numbers for a period, the same figures as the group's admin dashboard: total members, new joins, churned members and monthly recurring revenue. Admins only.

Example response:

```json
{
  "group": "yourgroup",
  "period": "30d",
  "members_total": 1284,
  "members_new": 96,
  "members_churned": 31,
  "mrr": {
    "amount": 41230,
    "currency": "USD"
  }
}
```

### approve_membership_request

Let an applicant into the group. Your AutoDM, if set, goes out as usual. Access: write, asks the user first. REST: `POST /api/v1/skool/approve_membership_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `request_id` | string | yes | Request ID from list_membership_requests. |

Approves one pending request, so the applicant becomes a member. Your AutoDM, if you set one, goes out as usual. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "r_51e0aa",
  "status": "approved",
  "member_id": "m_9d02f7"
}
```

### decline_membership_request

Decline an applicant's request to join. Access: write, asks the user first. REST: `POST /api/v1/skool/decline_membership_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `request_id` | string | yes | Request ID from list_membership_requests. |

Declines one pending request. The applicant is not notified with a reason. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "r_51e0aa",
  "status": "declined"
}
```

### create_post

Publish a post to the community feed in a category, as you. Access: write, asks the user first. REST: `POST /api/v1/skool/create_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `title` | string | yes | Post title. |
| `body` | string | yes | Post text. Links and images by URL. |
| `category` | string | yes | Category name. Admin-only categories need an admin account. |

Publishes a post to the feed in a given category, under your name. Links and images go in the body as URLs. Admin-only categories need an admin account. By default you confirm each post; you can switch that off for this tool.

Example response:

```json
{
  "post_id": "a3f9c2e1b7d84c06",
  "status": "published",
  "category": "Announcements",
  "url": "https://www.skool.com/yourgroup/week-12-challenge-ship-one-landing-page",
  "created_at": "2026-10-03T09:00:00+02:00"
}
```

### comment_on_post

Comment on a post, or reply to a comment, as you. Access: write, asks the user first. REST: `POST /api/v1/skool/comment_on_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `post_id` | string | yes | Post ID from list_posts. |
| `body` | string | yes | Comment text. |
| `parent_comment_id` | string | no | Reply under this comment instead of the post. |

Adds a comment to a post, or a reply under an existing comment when parent_comment_id is set. The comment appears under your name. By default you confirm each comment; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "c_77c4",
  "post_id": "a3f9c2e1b7d84c06",
  "parent_comment_id": null,
  "status": "published"
}
```

### send_message

Send a direct message in Skool Chat to a member, starting a conversation if needed. Access: write, asks the user first. REST: `POST /api/v1/skool/send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `member_id` | string | yes | Member ID from list_members or list_conversations. |
| `body` | string | yes | Message text. |

Sends a direct message in Skool Chat to one member and starts a conversation if there is none yet. Messages go out under your name; by default you confirm each one, and you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": "cv_93f1",
  "message_id": "msg_4410",
  "status": "sent",
  "sent_at": "2026-10-03T09:05:00+02:00"
}
```

### pin_post

Pin a post to the top of the feed (up to 3) or to a Classroom page (up to 12). Admins only. Access: write. REST: `POST /api/v1/skool/pin_post`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `group` | string | yes | Group URL name, e.g. 'yourgroup' for skool.com/yourgroup. |
| `post_id` | string | yes | Post ID from list_posts. |
| `pinned` | boolean | no | false unpins. Default: true. |
| `course_page_id` | string | no | Pin to this Classroom page instead of the feed. |

Pins a post to the top of the feed, where Skool allows up to 3 pinned posts, or to a Classroom page, which allows up to 12. Set pinned to false to unpin. Admins only. pin_post runs without asking first: pinning sends nothing to anyone and is undone with one call.

Example response:

```json
{
  "post_id": "a3f9c2e1b7d84c06",
  "pinned": true,
  "location": "feed"
}
```

## How do I connect Skool to Claude Code, Codex or Cursor?

Connecting Skool takes three steps: request access, sign in to Skool once, then add one MCP server or call the REST API with the same key.

### Connect Skool to your agent.

1. **Create an account** Sign up and add Skool in the console. Your API key is there too.

2. **Sign in to Skool once** Open the connect page from the console and sign in to Skool the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Skool tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through pending Skool membership requests in yourgroup. Approve applicants whose answers name a business they run, decline obvious spam, and leave everyone else for me with a one-line reason.
```

### Call Skool from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/skool/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/skool/create_post \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"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"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "post_id": "a3f9c2e1b7d84c06",
  "status": "published",
  "category": "Announcements",
  "url": "https://www.skool.com/yourgroup/week-12-challenge-ship-one-landing-page",
  "created_at": "2026-10-03T09:00:00+02:00"
}
```

## Why use Cotlet for Skool?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Skool yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Skool changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Skool MCP server on GitHub?

Yes. Community Skool MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, sign it in to Skool, and keep it running yourself; when Skool changes its site, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, sign it in to Skool, add it to each MCP client | Request access, sign in to Skool once, add one MCP server or API key |
| When Skool changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Skool session | In a file on your computer, readable by any program you run | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | Tools fail until you sign in again by hand | We keep it alive; if Skool logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Skool changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Skool API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Skool API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up. Listing all your Skool courses and their modules with list_courses costs about $0.00001, a thousandth of a credit.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Skool account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Skool yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Skool tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Skool in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Skool's terms:** You use your own Skool account and stay responsible for following Skool's terms. Cotlet is independent and not affiliated with Skool. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Skool API and MCP server on GitHub

Prefer code? Our public repo has ready Python scripts for the Skool API and a config for the Skool MCP server. Clone it, add your Cotlet API key and run.

Repo: [cotletdev/skool-api-mcp-server](https://github.com/cotletdev/skool-api-mcp-server)

- One script per job, Python standard library only
- Export to CSV or JSON, pagination handled for you
- MCP config for Claude, Cursor and Codex
- MIT licensed, runs on cron or GitHub Actions

## Frequently asked questions

**How do I get access?**

Request access and pick Skool. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Skool once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Skool session would leave my computer.**

Cotlet keeps your Skool session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Can my agent approve a whole queue of membership requests?**

Yes. list_membership_requests returns every pending request with the applicant's answers, your agent picks the ones that match your rules, and you confirm each approval with one click, or switch confirmation off for approvals and let it run every day on its own. Skool's AutoDM, if you set one, goes out on every approval, so the welcome message needs no extra call.

**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. Approving requests needs an admin or moderator role, and group stats need an admin.

**Can my agent post or send messages in Skool without asking me?**

No. Every call to approve_membership_request, decline_membership_request, create_post, comment_on_post or send_message waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. pin_post runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Skool API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/skool/{tool} from the HTTP Request node.