Skip to main content
Glama
cotletdev

Skool MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Skool MCP Server

No user-submitted related servers found.

    Related Servers

    • byob

      rezende5823
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive your own already-logged-in Chrome through a browser extension, rather than a headless or cookie-copied instance. It exposes 25 tools for snapshotting pages, clicking, typing, reading content, taking screenshots, recording network traffic, and reading cookies or storage, so agents can act on authenticated sites without triggering bot detection.
      1 npm
      ISC

    • byob

      Panagiotisu0227
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the real Chrome browser you already have open, so agents can read logged-in pages, click, fill forms, take screenshots, and inspect tabs, cookies, and network traffic. All communication stays on your machine, with no debugging port or manual cookie copying required.
      1 npm
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 69 tools

    Disambiguation4/5

    Despite 69 tools, most target a clearly distinct resource+action (create_event vs update_event vs delete_event, list_group_rules vs update_group_rule), and descriptions proactively disambiguate near-pairs like ban_member vs remove_member and search_members vs list_members. A few boundaries still blur: ban_member/remove_member overlap semantically (one tool both unbanning and removing), and list_members vs list_membership_requests vs list_reported_posts all surface member-ish data that an agent could pick wrongly.

    Naming Consistency4/5

    Nearly every name is snake_case verb_noun with a predictable verb set (list_, get_, create_, update_, delete_, set_, mark_, pin_, add_). The main deviation is create_/add_ used interchangeably for creation (create_category/create_course vs add_group_link/add_group_rule/add_membership_question), plus set_course_published standing in for an update operation, but the pattern stays readable.

    Tool Count2/5

    69 tools is far past a well-scoped surface and exposes every granular settings toggle (links, rules, categories, questions, levels, AutoDM, notifications) as its own tool. Substantial consolidation is feasible — e.g. one links tool with an action parameter, or merging the ten-plus membership-admin tools — so the count is heavy relative to the domain's core workflows.

    Completeness4/5

    Coverage is unusually broad: full CRUD-ish lifecycles for posts, comments, categories, events, sidebar links, rules, membership questions and members, plus Classroom, chat, notifications and discovery reads. The notable gaps are course and lesson deletion (create/get/list/update/publish exist but no delete), no conversation-level read-marking or message deletion, and no group creation, all of which agents can mostly work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources