Creators & communities
Skool
Posts, members, courses, events and DMs for your Skool community.
71 endpoints
Hopper.so publishes no API and no MCP server (checked 15 Nov 2026). Cotlet runs a hosted Hopper MCP server with 4 tools that ChatGPT and Claude use in your own Hopper account. Every post, message and share waits for your OK before members see it.
4 tools Read and write
Hopper.so publishes no public API. hopper.so/api and hopper.so/developers lead back to the home page, and no developer documentation, API key page or MCP server was found. No official ChatGPT or Claude connector exists either.
| What you need | Hopper API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No API or MCP server | Copy and paste | Hosted MCP server |
| Posts, chats, courses and resources | Not available | One screen at a time | 4 tools, writes after your OK |
| Run on a schedule from n8n or a script | Not available | Manual only | REST, same key |
Checked 15 Nov 2026. Sources: Hopper.so home page · Hopper.so on the App Store · Hopper sign-in · Hopper support
Once, in a browser we host for you.
One address in its settings.
It drafts the post, you approve it.
Your agent works in your own signed-in Cloud Browser. Every post, chat message and share waits for your OK. Who can see your session
Sign in to Hopper in a Cloud Browser. Open hopper.so/c/login in your Cotlet Cloud Browser and sign in with your own Hopper account, by email, Google or Apple.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Hopper sits on the shared address https://cotlet.dev/mcp/v1 with every other app you enable, so one connector covers them all. Turned Hopper on after connecting? Refresh the connector and the 4 Hopper tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: hopper_so_read One tool per owner feature on Hopper's App Store listing. Each takes an `action`: `list` only reads, the other action writes and asks first.
What members read every day. Read the feed or a chat, then post or reply after your OK.
Hopper's listing describes interactive feeds with rich media. A post appears in the feed for every member, so it waits for your OK; the agent writes your words and adds nothing you did not ask for. `list` returns recent posts, newest first. By default you confirm each call; you can switch that off for this tool.
MCP callhopper_so_write → publish_community_post
REST endpointPOST https://cotlet.dev/api/v1/hopper-so/community-post/publish
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `publish`. `list` only reads. |
| community string | string | Community name, as Hopper shows it. Leave empty when your account runs one community. |
| text string | string | The post, for `publish`. |
| media_url string | string | Optional image or video for `publish`, as a link the Cloud Browser can download. |
| limit integer | integer | For `list`: how many recent posts to return. |
{
"action": "action"
} {
"community": "Morning Pages Club",
"posts": [
{
"author": "You",
"text": "Week two starts Monday. Share one page from this week.",
"posted": "2026-11-15"
},
{
"author": "Member",
"text": "Day nine done, harder than day one.",
"posted": "2026-11-15"
}
]
} A message reaches everyone in the chat at once, so every send waits for your OK. `list` returns the latest messages, so the agent can answer a question members asked while you were away. By default you confirm each call; you can switch that off for this tool.
MCP callhopper_so_write → send_group_chat_message
REST endpointPOST https://cotlet.dev/api/v1/hopper-so/group-chat-messages
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `send`. `list` only reads. |
| community string | string | Community name, as Hopper shows it. Leave empty when your account runs one community. |
| chat string required | string | Group chat name, as Hopper shows it. |
| text string | string | The message, for `send`. |
{
"action": "send",
"community": "Morning Pages Club",
"chat": "Cohort November",
"text": "Live call moves to Thursday 7 pm, same link."
} {
"chat": "Cohort November",
"sent": true,
"text": "Live call moves to Thursday 7 pm, same link."
} Set up a course with its title and description, and share files or links with members. Lessons and prices stay yours to add in Hopper.
Hopper's listing describes it as a place to host courses for your members. `list` returns the courses your account already hosts, so the agent does not create a second one with the same title. `create` sets up the course with the title and description you give; lessons and pricing stay yours to add in Hopper. By default you confirm each call; you can switch that off for this tool.
MCP callhopper_so_write → create_course
REST endpointPOST https://cotlet.dev/api/v1/hopper-so/courses
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` only reads. |
| community string | string | Community name, as Hopper shows it. Leave empty when your account runs one community. |
| title string | string | Course title, for `create`. |
| description string | string | What members learn, in your words, for `create`. |
{
"action": "action"
} {
"community": "Morning Pages Club",
"course": "Thirty days of journaling",
"created": true
} Your signed-in Hopper browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 4 Hopper tools. The session cookie stays in the Cloud Browser.
The communities, courses and chats your Hopper account can open, and nothing more.
Your Hopper plan and billing, shop prices, payouts, member removals and account settings.
You sign in again yourself, in the same Cloud Browser.
Disable Hopper for agents, reset the browser, or sign out of Hopper there.
Cotlet never sees or stores your password: you sign in to Hopper yourself, by email, Google or Apple, and the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Hopper's App Store version history lists eight updates between 2 October and 5 November. Cotlet watches the apps it serves and updates the Hopper server when its web screens change, so your agent keeps working without a change on your side.
The agent sees only what your own Hopper account sees. A course or community you cannot open in Hopper stays closed to the agent too.
If Hopper signs you out, one click in the Cotlet console reopens the Cloud Browser so you can sign in again.
list. | Action | How to put it right |
|---|---|
| Community post | Edit or delete it in Hopper; members may have read it already |
| Group chat message | Already with the chat: send a correction |
| Shared resource | Remove it in Hopper; members may have downloaded it |
| New course | Rename or delete it in Hopper before you add lessons |
All 4 tools write, and all 4 ask first: by default you confirm each call, and you can switch that off per tool. Their list action only reads, but confirmation is per tool, so it asks too until you switch it off.
{
"name": "send_group_chat_message",
"arguments": {
"action": "send",
"community": "Morning Pages Club",
"chat": "Cohort November",
"text": "Live call moves to Thursday 7 pm, same link."
}
} curl -X POST https://cotlet.dev/api/v1/hopper-so/group-chat-messages \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"send","community":"Morning Pages Club","chat":"Cohort November","text":"Live call moves to Thursday 7 pm, same link."}' {
"chat": "Cohort November",
"sent": true,
"text": "Live call moves to Thursday 7 pm, same link."
} The example moves a live call and tells the cohort chat. A cron job or n8n flow can make the same call over REST at /api/v1/hopper-so with the same key and price, in JSON. Failed calls are free.
About $14 a monthfor a coach with one community and a running cohort, 2,460 credits. Your Hopper plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Read the cohort chat and reply | 2 × 30 | 600 |
| Weekly community post | 2 × 4 | 80 |
| Worksheets and links shared | 2 × 8 | 160 |
| Announcements in chat and feed | 2 × 4 | 80 |
| New course set up | 2 × 2 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 96 calls | 2,460 |
The smallest pack, 5,000 credits for $29, covers this month with room to spare.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Hopper on the web | Everything, signed in as you. | One screen at a time, only while you are at it. |
| Hopper phone apps | Posts, chats and courses on iPhone and Android. | Still by hand; no agent can work there. |
| Your own browser script | Clicks through Hopper for you. | You write, host and fix it whenever Hopper changes. |
Hopper has no API, so there is no official route for an agent today. Cotlet fits when you want ChatGPT, Claude or a script to draft and post in Hopper from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Hopper tools.
Sign up free at https://cotlet.dev/signup?app=hopper-so, turn on Hopper under Integrations in the console and sign in at https://hopper.so/c/login in your Cloud Browser. Then connect your AI agent and ask it to read your feed. The trial needs no card.
Hopper.so publishes no public API: hopper.so/api and hopper.so/developers lead to its home page, and no developer documentation was found (checked 15 Nov 2026). There is no Hopper MCP server and no official ChatGPT or Claude connector. Cotlet does not need one: it works in your own signed-in Hopper account.
It works in Hopper on the web, in your Cloud Browser. Posts, chats, courses and resources it creates show up in the iOS and Android apps too, because they are the same account.
Yes. Hopper offers email, Google and Apple sign-in, and you complete whichever you use yourself in the Cloud Browser. Cotlet keeps the session, never the password.
Only in how it is called. Both carry the same 4 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Hopper.so or Hopper Pte. Ltd.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy