skool-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| baseUrl | No | Base URL of Skool (default: https://www.skool.com) | https://www.skool.com |
| cookies | Yes | Your Skool session cookies (e.g., auth_token=JWT) | |
| defaultCommunity | No | Default community ID or slug (e.g., 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, labels, member management, posts, courses, lessons, and notifications are clearly separated. The generic skool_request tool is explicitly positioned as a debugging/discovery escape hatch rather than overlapping with the specific operations.
Most tools follow a consistent skool_<resource>_<action> pattern, e.g., skool_members_list, skool_members_approve, skool_posts_create. Minor deviations like skool_request, skool_community_info, and skool_notifications lack a clear verb-resource structure but are still readable and predictable.
14 tools is well within the ideal range for a platform integration covering communities, members, posts, courses, lessons, and notifications. Each tool corresponds to a meaningful operation without redundant or excessive surface area.
The toolset covers core reading and some writing flows, including member approvals and post commenting, but lacks obvious lifecycle operations such as updating or deleting posts, removing members, or fetching detailed lesson content. The generic skool_request tool can bridge some gaps, but the intentional surface is incomplete for full community management.