Skool MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| baseUrl | No | Base URL for Skool | https://www.skool.com |
| cookies | Yes | Your Skool session cookies (e.g., auth_token=YOUR_JWT_HERE) | |
| defaultCommunity | No | Default community ID | ai-agent-academy-6994 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| skool_requestA | Make an arbitrary authenticated HTTP request to any Skool URL. Useful for API discovery and debugging. Cookies and User-Agent are injected automatically. |
| skool_community_infoB | Get community details including name, description, member count, and settings. Uses Next.js data route for read access. |
| skool_community_labelsB | Get category labels for a community from api2.skool.com. |
| skool_members_listB | List community members with pagination. Returns member info including name, bio, role, and online status. |
| skool_members_pendingA | List pending membership requests. Requires auth cookies with admin/moderator access. |
| skool_members_approveA | Approve a pending member by their membership request ID. Requires admin/moderator auth. |
| skool_members_rejectA | Reject a pending member by their membership request ID. Requires admin/moderator auth. |
| skool_posts_listA | List posts in a community feed. Supports category filtering and pagination. Returns post title, content preview, author, likes, and comment count. |
| skool_posts_getA | Get a single post with its full content and comments. Provide the post slug (name field from posts list). |
| skool_posts_createA | Create a new post in a community. Requires auth cookies. Posts to api2.skool.com. |
| skool_posts_commentA | Add a comment to a post. Requires auth cookies. Posts to api2.skool.com. |
| skool_courses_listB | List courses in a community classroom. Returns course names and metadata. |
| skool_lessons_listC | List lessons/modules in a specific course. Uses the Next.js classroom data route with course parameter. |
| skool_notificationsB | Get recent notifications. Tries the Next.js notifications page data route. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a distinct resource and action: community info vs labels, member management actions are clearly separated (list, pending, approve, reject), posts have list/get/create/comment, and courses/lessons/notifications are separate. The generic skool_request is the only outlier but serves a clearly different purpose as a catch-all.
All tools follow the skool_<resource>_<action> pattern consistently, e.g., skool_members_list, skool_posts_create, skool_courses_list. Even the generic request tool fits the prefix convention. No mixed casing or verb style deviations.
14 tools is well within the ideal 3-15 range for a platform-specific server. The count covers the major areas (community, members, posts, courses, lessons, notifications) without being bloated or sparse.
The surface covers core read and some write operations, but there are notable gaps: no post update/delete, no member removal, no course creation/management, and lesson content is not fetched. The generic skool_request can fill some gaps but is not a substitute for dedicated tools.