01 · Records and state owned
Community members, spaces and content, events and courses, messages, tags and access controls, analytics, form submissions, live-room transcripts, and uploaded media.
Circle
Circle
A community platform whose official MCP runs on the Admin API and can query live data or perform supported administrative actions, making it a strong example of a community system exposed beyond its native UI.
Publishing, newsletters & creator platformsSystem of engagementAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Browse and search members, spaces, posts, events, courses and tags; view analytics, form submissions and live-room transcripts; and summarize space activity.
03 · Actions and write paths
With Full access, invite, update or remove members; create, edit or delete community content and events; manage courses and access groups; send messages; and upload files or images.
04 · Authentication and permissions
Each community admin signs in through OAuth and selects Read only or Full access. Read only hides write tools; Full access exposes supported administrative actions. Changing level requires disconnecting and reconnecting, which revokes the old connection.
05 · Monitoring, approval, and recovery
Start with Read only. Grant Full access only for defined workflows and require review before member invitations or removal, moderation, public content changes, event changes, messages, access-control changes, or uploads.
06 · Limits and caveats
Every tool call consumes one Admin API v2 request. Current monthly allowances are 5,000 on Business, 30,000 on Enterprise or Circle Plus, and 250,000 on Circle Plus Platform, with a 2,000-request-per-five-minute rate limit.
Agent access
MCP support
Official MCP serverCircle-hosted remote MCP built on Admin API v2Current documented service
Support: Official MCP server
Read scope: Browse and search community members and content; view analytics, forms and live-room transcripts; and summarize space activity under Read only or Full access.
Write scope: Full access can manage members, community content, events, courses, messages, access groups, and uploads.
Authentication: OAuth sign-in to the Circle-hosted remote MCP, using the connecting community admin's account.
Approval boundary: Default to Read only; require explicit approval before enabling Full access and before member removal, moderation, messaging, publication, access-control changes, or uploads.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity2
Governance3
Agent access4
UI extensibility3
Portability4
Observability3
Documentation5
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Circle ships them.
Single-platform patterns
- Community health and operations room
- Publication operator cockpit
- Editorial planning room
- Audience and membership explorer
Multi-platform compositions
- Circle + video or creative platform: publication operator cockpit
- Circle + social or distribution system + analytics or commerce system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCPRepresentative source
https://api.circle.so/mcp ↗Official Circle developer and product documentation confirms broad admin capability and states every MCP action counts against monthly Admin API limits. Because member and administrative actions can be consequential,…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://api.circle.so/ ↗First-party developer platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Data APISource inventory
https://api.circle.so/apis/data-api ↗First-party community event stream.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://circle.so/ ↗Product overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP use casesSource inventory
https://circle.so/blog/circle-mcp-use-cases ↗First-party operational examples.
- Publisher updated
- Jun 12, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.