Circle.so AI: What's Plan-Gated and What MCP Won't Do
If you searched “Circle.so AI,” you have probably seen three different things called AI inside the same product and want to know which one you actually get. Circle has shipped real AI — more of it, and further along, than most community platforms — and it has also put the best pieces behind the most expensive tiers.
What follows is what each piece does, which plan it sits on, and what a creator running a paid community can wire up around it.
Circle’s AI is three products sharing one word
AI Agents are the member-facing ones. Circle’s pitch: they “guide, support, and coach your members 24/7,” to “automate engagement, provide instant answers, and scale your community without losing the human touch.” Under the hood it’s retrieval-augmented generation over a knowledge engine you control — you point an agent at specific spaces, course lessons, uploaded files, and video transcripts, and it answers from those. You get up to 10 agents, each scoped to a different job, plus an AI Inbox to watch what they said. Circle added an agent analytics dashboard and profile-field personalization in its April 2026 release, so an agent can factor in a member’s stated profession or location when it replies.
Circle is also explicit that “your data is completely secure, and won’t be used by AI/LLM platforms (or by Circle) for training models.” For a paid community where members post revenue numbers and half-finished work, that matters.
Circle AI is the admin-facing one, launched with the Eclipse release: “an AI partner that builds, runs, and grows your community business with you,” shipping “50+ specialized skills across 12 domains” spanning community setup, member management, content, monetization, and growth, plus a daily briefing on activity. It builds structure from a description and tells you what needs attention.
Circle MCP is the interesting one, and it’s below.
The plan wall is the real answer
This is where most write-ups get vague, so here it is plainly, from Circle’s own pricing page:
- Professional, $89/month — no API, no Workflows, no AI Agents, no MCP. The AI you searched for is not on this plan.
- Business, $199/month — Workflows, Admin API, Headless Member API, and Circle MCP.
- Circle Plus, custom — everything above plus “AI Agents & AI workflows.”
So the headline feature, the member-facing AI Agents, is a Circle Plus conversation with a salesperson. The automation-relevant capabilities — API, webhooks, MCP — all land on Business. If you are on Professional and evaluating Circle’s AI, you are evaluating a $199/month upgrade at minimum and a custom quote for the agents.
Circle MCP is genuinely good, and it is not automation
Give Circle credit: it shipped a hosted, remote MCP server before almost anyone in its category. You add https://app.circle.so/api/mcp as a custom connector in Claude, ChatGPT, or Gemini, select your community, and authorize. Circle’s framing: “No code, no API keys,” and “if it’s available in Circle’s Admin API, it’s available through Circle MCP.” Members can’t touch it — only admins can connect, which means the LLM is holding admin-level access to your community.
That is real and useful. “Which spaces have had no new posts in the last seven days?” is now a question you ask instead of a dashboard you dig through. Inviting members, creating spaces, posting, managing access groups, pulling engagement data — all reachable from chat.
But notice the shape of it. Every one of those is something you start by typing.
There is no such thing as an MCP trigger. The protocol's own working group states plainly that clients find out about server-side changes by polling for them, and a real event mechanism remains unshipped.
Circle’s own guidance points at this without naming it: the recommendation is to set read tools to always-allow and keep write and delete tools on approval, because the assistant “tells you what it’s going to do and waits for your confirmation.” That is a design for a conversation, not for a community that keeps running at 11pm on a Saturday when you’re not in the chat.
Both ChatGPT and Claude will now do work on a schedule, unattended. Neither reacts to events. A task that runs hourly still finds out an hour late, and one that runs each morning finds out tomorrow — the trigger is the clock, never the thing you actually care about.
For a membership business that gap is expensive in a specific way. “Every Monday, summarize last week’s activity” is achievable today. “A paying member posted a question in the core space and nobody has replied in 18 hours — surface it” is not, unless something is watching for the event.
The Admin API is real and self-serve, once you’re on Business
Circle publishes proper developer documentation at api.circle.so. There are three surfaces worth knowing:
- Admin API (v1 and v2) — “designed for community admins to build automations, migration scripts, and administrative integrations.” Business plan and above.
- Headless — a Member API plus an Auth API for building your own member-side experience against Circle’s data. Business plan and above.
- Data API — event-stream ETL into your own warehouse. Circle Plus Platform only.
Getting a token is refreshingly ordinary: a community admin goes to Developers → Tokens in the community and generates one. No application form, no five-day review, no partner program. Requests authenticate with a standard Authorization: Bearer <API_Token> header. That is a much better story than most vertical SaaS, where individual customers are structurally locked out.
Watch the quota, because it is monthly rather than per-second and it is not large: Business gets 5,000 requests/month, Circle Plus 30,000, and Circle Plus Platform 250,000, against a burst ceiling of 2,000 requests per 5 minutes per IP. Five thousand a month is roughly 160 a day — plenty for event-driven work, nowhere near enough to poll every space every few minutes. Design around events, not sweeps. Circle also notes that Zapier usage does not count toward these limits.
Once you have that token, you paste it into Carly at carlyassistant.com/integrations as a bring-your-own-key connection. Circle isn’t a prebuilt Carly connector, and BYO-key is the supported path for exactly this.
Workflows and webhooks are the part that actually fires
Circle’s automation Workflows — Business plan and above — include a webhook action. You pick a trigger event in your community, and Circle posts the event data to an endpoint you specify. Triggers include a new member joining, a new post being published, and a tag being added to a member.
That is an event trigger, and it is precisely the thing Circle MCP, ChatGPT’s scheduled tasks, and Claude’s Cowork tasks all lack. Something happens in the community, Circle fires, and work begins in the same minute rather than at next Monday’s recap.
Concretely, for a paid community: a new-member webhook fires, and instead of a templated welcome DM, a workflow reads that member’s onboarding answers, picks the two spaces and the one lesson that match what they said they’re here for, and sends a message that names them. A tag-added webhook fires when someone completes module three, and the cohort call invitation goes out at the moment they’re ready for it rather than on the generic drip.
In Carly, that trigger-and-branch scaffolding is the free, unlimited Zapier-style workflow layer; the AI agents that read the context and write the message start at $35/month. The point isn’t that Circle’s own agents are bad — it’s that they answer when spoken to, and the highest-leverage moments in a membership business are ones nobody is present for.
The churn signal Circle’s AI doesn’t chase
Circle’s AI Agents are inbound. A member asks, an agent answers, and the analytics dashboard tells you how many members started conversations and how many came back.
None of that is: this member logged in four times a week for three months, hasn’t posted in 19 days, and renews on the 8th. Silent disengagement before a renewal date is the single most valuable signal a paid community has, it never announces itself, and no agent will surface it because the member has by definition stopped talking. Circle’s API will hand you the activity data. Deciding to look, on the right cadence, against the renewal calendar, and drafting the message that goes out — that is outbound work Circle leaves to you.
What to set up before you upgrade
None of the following needs a Circle token, and all of it works on Professional:
- Inbox triage on the address your Circle notifications, Stripe receipts, and member replies land in, so the ones needing a human answer surface and the noise doesn’t.
- A morning brief from your calendar covering today’s cohort calls, office hours, and guest sessions, with who’s new since yesterday.
- Renewal and launch-date reminders driven off dates rather than off remembering.
- Draft follow-ups to members who emailed you directly, written from your own notes and ready to send.
That covers email, calendar, and tasks — the three surfaces that work regardless of your Circle tier. The webhook layer goes on top the day you land on Business.
FAQ
What is Circle AI? Circle uses the name for three things: AI Agents (member-facing assistants trained on your spaces, courses, posts, and files, up to 10 per community), Circle AI (an admin-facing partner with 50+ skills across 12 domains, shipped in the Eclipse release), and Circle MCP (a hosted MCP server that connects your community to Claude, ChatGPT, or Gemini).
Which Circle plan do I need for AI? Circle MCP, Workflows, and the Admin API are on Business ($199/month) and above. AI Agents and AI workflows are Circle Plus, which is custom-priced. Professional ($89/month) includes none of them.
Does Circle have an MCP server?
Yes. Circle MCP is a remote connector at https://app.circle.so/api/mcp. You add it as a custom connector in your LLM and authorize your community — no API key needed. Admin-only, Business plan and above.
How do I get a Circle API token?
A community admin generates one from Developers → Tokens inside the community, on the Business plan or higher. Requests use an Authorization: Bearer <API_Token> header. Business plans are capped at 5,000 requests per month.
Does Circle support webhooks? Yes, as an action inside automation Workflows on Business and above. Trigger events include a new member joining, a new post being published, and a tag being added to a member.
Can Circle’s AI Agents win back members who’ve gone quiet? Not on their own. Agents respond to members who engage with them. A member drifting toward a non-renewal has stopped engaging, which is exactly why an inbound agent never sees them.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
