Skool MCP Server
Related Servers
Alternatives to Skool MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server for Skool.com communities. Enables listing/approving members, posting, commenting, and managing courses.14-
- AlicenseNot gradedqualityBmaintenanceMCP server to read and operate your Skool community (calendar, feed, posts, members) and publish posts/comments with confirmation, using your own authenticated session.1MIT
- AlicenseAqualityAmaintenanceSelf-hosted MCP server that lets AI agents work with a Skool community through your own Chrome session, offering 69 tools for members, membership requests, posts, comments, polls, classroom, calendar, chat and stats. It runs locally over stdio or HTTP and also exposes a REST API for scripting.2713PolyForm Noncommercial 1.0.0
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes Discord API as tools, enabling users to manage servers, channels, messages, and roles through natural language.-
- AlicenseBqualityAmaintenanceMCP server for managing Coolify instances, enabling control of applications, databases, services, servers, and more via natural language.13684 npmMIT
- FlicenseNot gradedqualityCmaintenanceComprehensive Discord server management through MCP, enabling channel, role, permission, message, moderation, and automation tasks via natural language.4-
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.