Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Posts, members, courses, events and DMs for your Skool community.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://cotlet.dev/mcp/v1/skool/connectÖffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"skool": {
"command": "uvx",
"args": [
"skool-api-mcp",
"mcp"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add --transport http skool https://cotlet.dev/mcp/v1/skool/connectclaude mcp add skool -- uvx skool-api-mcp mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"skool": {
"url": "https://cotlet.dev/mcp/v1/skool/connect"
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"skool": {
"command": "uvx",
"args": [
"skool-api-mcp",
"mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"skool": {
"type": "http",
"url": "https://cotlet.dev/mcp/v1/skool/connect"
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"skool": {
"type": "stdio",
"command": "uvx",
"args": [
"skool-api-mcp",
"mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://cotlet.dev/mcp/v1/skool/connectMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde über die Domain cotlet.dev bestätigt (die Registry prüft, wem die Domain gehört)
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.0.2) kam vor 13 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, AI Deprecations
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Yes, ChatGPT, Claude and other AI agents can work in your Skool account. That includes Cursor, Codex, OpenClaw and any MCP client, plus automations in n8n, Make and Zapier. Ask in plain words, and the AI approves membership requests, posts and comments, answers members, sets up Calendar events and reports new members, churn and MRR. It shows you what it will do first and sends nothing to other people until you say so.
As of November 2026, this repo is the missing piece: 71 Skool tools for AI assistants and scripts.
*Show me pending membership requests and approve the ones whose answers mention a business.*
*Which posts from the last 7 days have no comments yet? Draft a reply for each.*
*Create a Calendar event for Thursday 6pm CET with the Zoom link and pin an announcement about it.*
*Tell me new members, churn and MRR for the last 30 days.*
| Ready to use, at Cotlet | Run it yourself, this repo | |
|---|---|---|
| For | community owners and admins | developers |
| Setup | sign in to Skool once, about 5 minutes, nothing to install | Python and a terminal |
| Works in | ChatGPT and Claude apps, on your phone too, Cursor, Codex, OpenClaw, any MCP client, n8n, Make, Zapier, REST API | Claude Code, Claude Desktop, Cursor, Codex on your computer |
| Runs | 24/7, your computer can be off | while your computer is on |
| Price | 7 days free, no card | free |
Cotlet is best for community owners and admins who want ChatGPT, Claude or another AI agent to work in Skool for them, with nothing to install.
[Start free at cotlet.dev →](https://cotlet.dev/signup?app=skool&utm_source=github&utm_medium=readme&utm_campaign=skool&utm_content=top-button)
A Skool API and a Skool MCP server you run on your own computer, in Python, on the session of your own Google Chrome. All 71 Skool tools we run in production at Cotlet: members, membership requests, posts, comments, polls, Classroom, video transcripts, Calendar, group settings, Skool Chat and stats.
Skool has no public API and no official MCP server. This repo gives you both:
http://127.0.0.1:8787/api/v1/skool, with OpenAPI docs at /docs. Setupcall("list_members", group="yourgroup"), plus 16 ready scripts in examples/.Free for your own use, your own business included (license).
uv tool install skool-api-mcp # or: pip install skool-api-mcp
skool-mcp connect # reads your Skool session from Chrome skool-mcp call list_groups claude mcp add skool -- uvx skool-api-mcp mcp
Does Skool have an API? No. Skool has no public API and no developer docs. The only official connection is the Zapier plugin on the Pro plan, which sends new paid members and Membership Questions answers out, invites a member and unlocks a course. It cannot list all members, approve requests, post, comment, send DMs or read stats. This repo and Cotlet give you 71 Skool tools as a REST API and an MCP server.
Can I get a Skool API key? Not from Skool for your own account. With Cotlet you get your own API key that works with your Skool account, for scripts, n8n, Make, Zapier or any HTTP client. This repo needs no key: it runs on your computer, on your own Skool session.
Is there an official ChatGPT integration for Skool? No. Skool has no official ChatGPT or Claude connector. Cotlet is an unofficial one that works today, in the ChatGPT and Claude apps and in any AI agent that takes an MCP server.
How do I connect Skool to ChatGPT? Sign up at cotlet.dev, sign in to Skool once in your Cloud Browser there, and add Cotlet to ChatGPT, following the steps in your account. Then ask ChatGPT about your Skool like you would ask an assistant. ChatGPT needs a server on the internet, so this repo alone, running on your computer, does not connect to ChatGPT.
Can ChatGPT manage my Skool community? Yes, with Cotlet. It reads new posts and comments, drafts replies, approves membership requests by your rules, pins announcements and creates Calendar events. Anything posted in your group waits for your OK.
Can I get my Skool members and stats out of Skool? Yes, with Cotlet: the full member list with join dates and answers, membership requests, churn and MRR, as answers in chat or JSON.
Can I automate Skool with Zapier, Make or n8n? Skool's own Zapier plugin, on the Pro plan, only sends new paid members and membership answers out, invites a member and unlocks a course. With Cotlet, n8n, Make and Zapier can also list members, approve requests, post, comment and read stats.
Can I use it from my phone? Yes, with Cotlet: once it is set up, the ChatGPT and Claude apps on your phone can use Skool for you.
Do I need to be technical? For Cotlet, no: you sign in to Skool and add Cotlet to ChatGPT or Claude, with step-by-step instructions in your account. This repo is for people who are fine with Python and a terminal.
Is my Skool account safe? Yes. Neither Cotlet nor this repo sees or stores your Skool password. You sign in yourself, the way you always do, and the AI works on that signed-in session. Anything that reaches other people asks for your OK first: in Cotlet by default, here through your MCP client.
Is it free? This repo is free, also in your own business. Cotlet is free for 7 days with no card, then one-time credit packs from $29, no subscription. Pricing.
I manage Skool for several accounts or clients. Does that work? Yes, with Cotlet. Each Skool login gets its own connection. Write to contact@cotlet.dev and tell us how many accounts you manage.
AI agent (MCP) / script (REST, Python) ──▶ skool-mcp on your computer ──your Skool cookies──▶ skool.com
▲ skool-mcp connect ───────┘ reads them once from your Chrome (DevTools Protocol)
skool-mcp connect attaches to that Chrome through the Chrome DevTools Protocol, reads the skool.com cookies and saves them to ~/.config/skool-api-mcp/session.json, readable by your user only. It never sees or stores your password.api2.skool.com and the page data of www.skool.com) with those cookies, sent with curl_cffi, which copies Chrome's TLS fingerprint. No headless browser runs.Skool's session cookie lasts about a year. When Skool signs you out, the server reads the cookies from Chrome again, if Chrome is open with remote debugging on.
From PyPI:
uv tool install skool-api-mcp # or: pipx install skool-api-mcp, or: pip install skool-api-mcp
skool-mcp --version
MCP clients can also run it with no install: uvx skool-api-mcp mcp.
From source:
git clone https://github.com/cotletdev/skool-api-mcp-server.git
cd skool-api-mcp-server python3 -m venv .venv . .venv/bin/activate # Windows: .venv\Scripts\activate pip install -e . skool-mcp --version
With uv: uv venv && uv pip install -e ., then uv run skool-mcp ....
Setting it up with an AI agent (Claude Code, Codex, Cursor)? Open it in this folder and ask it to set up the repo: AGENTS.md tells it every step, and it asks you only for the steps in Chrome.
To update: uv tool upgrade skool-api-mcp (or pip install -U skool-api-mcp), from source git pull && pip install -e .. We copy every change of the hosted Skool tools into this repo.
chrome://inspect/#remote-debugging in Chrome and switch remote debugging on. Chrome then accepts DevTools connections from programs on this computer, and asks you before each one. skool-mcp connect
Saved 15 skool.com cookies to /Users/you/.config/skool-api-mcp/session.json
Signed in to Skool as Ana Lopez (ana-lopez-4127)
You can switch remote debugging off again afterwards. Leave it on if you want the server to pick up a new session by itself after Skool signs you out.
connect looks for Chrome's DevToolsActivePort file in the default profile folder. For Chrome Beta, Canary or a custom profile folder, pass --profile-dir " ".
Chrome does not open a debugging port on your default profile, so start a separate one, sign in to Skool there once, and connect to it:
# macOS
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --remote-debugging-port=9222 --user-data-dir="$HOME/.chrome-skool"
google-chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.chrome-skool"
"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="%USERPROFILE%\.chrome-skool"
skool-mcp connect --cdp http://127.0.0.1:9222
--cdp also takes a ws:// DevTools URL, for example of a Chrome on another machine reached over an SSH tunnel.
For a server with no Chrome: in Chrome open DevTools on skool.com, **Application
Nur der Anfang wird gezeigt; den Rest findest du im Repo