Connect iGloo to your AI.

Connect in two steps

1. 1 · Get an API key

   Sign in and open Account → API keys → Create key. The igloo_… value is shown once — store it in your agent’s secrets. A key acts as you: it can only touch communities you own or admin.

2. 2 · Point your agent at the endpoint

   Endpoint https://app.iglooapp.com/api/mcp · transport streamable HTTP · auth Bearer igloo_…

   {
     "mcpServers": {
       "igloo": {
         "url": "https://app.iglooapp.com/api/mcp",
         "headers": { "Authorization": "Bearer igloo_YOUR_KEY" }
       }
     }
   }

   Any other client: JSON-RPC over HTTP with the Bearer header and Accept: application/json, text/event-stream. tools/list enumerates; tools/call runs one. A no-auth GET manifest and /llms.txt describe everything before you mint a key.

How to think about it

• Communities are the unit — each has a URL slug. Call list_communities first; almost every tool takes community_slug.
• Expedition is a 5-level progression. Attach a reward to a level — text (a promise), course (auto-enrol), chat (owner DMs the member) or webhook (signed POST). Rewards fire automatically on level-up.
• Onboarding = up to 5 joining questions + a member.joined webhook that captures every new member into a CRM/autoresponder.
• Payments stay in GoCushy — sell access by creating a GoCushy product for the community/course; iGloo grants entitlements from its webhook. The agent sets up the community and rewards, not checkout.

What the agent can do

Write tools are owner/admin-only and fail with a message that tells the agent exactly what to fix — a bad course_slug returns the list of valid slugs, so the agent retries without you babysitting.

Webhooks out (non-MCP integration)

Two events flow out of iGloo to your systems, both HMAC-signed (x-igloo-signature: sha256=<HMAC-SHA256 of body>):

• member.joined — { member: { email, name, handle }, answers } — fires when a new member becomes active. Map it into Kit/Mailchimp for autoresponders.
• reward.unlocked — fires when a member reaches a level with a webhook reward (coupons, swag, external systems).

There’s also a read-only embeddable community widget at /embed/<slug>.

Prompt recipes

Paste these into Claude (or any MCP-capable agent) and adjust. The agent calls the right tools; you approve the actions. Tip: start with “List my iGloo communities” so it knows your slugs.

Create an iGloo community called "Founder Fastlane" for indie SaaS founders. Then:
- Post a pinned welcome explaining it's a place to share launches and get feedback.
- Add a weekly "Launch Review" event every Thursday 9am NZT on Zoom (https://zoom.us/j/123).
- Invite alex@example.com and sam@example.com.
Give me the community link when you're done.

For my "founder-fastlane" community, configure onboarding:
- Ask three joining questions: "What are you building?", "What stage are you at?", "What's your #1 goal this quarter?"
- Send new members to my Zapier hook: https://hooks.zapier.com/hooks/catch/abc123
Then show me the current onboarding config to confirm.

Show me the Expedition reward ladder for "founder-fastlane". Then set:
- Level 2: give course access to the "getting-started" course.
- Level 3: a chat message from me — "Here's your 20% code: FAST20".
- Level 4: a webhook reward "Founder swag pack" → https://hooks.zapier.com/hooks/catch/def456
Confirm what each level now unlocks.

Every Monday, run our weekly update:
1. Pull community_stats for "founder-fastlane".
2. Draft and publish a broadcast celebrating the numbers and this week's focus (so everyone's notified).
3. Schedule this Thursday's Launch Review if it isn't already there.