Circle MCP integration for AI agents.
Connect AI agents to Circle through 8 structured actions, including get community, get community member, and get post. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Circle integration exposes
The Circle Agent App exposes 8 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent get details about the circle community associated with the current api token, get a circle community member by id, and get a circle basic post by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Circle account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Circle capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_communityREADGet details about the Circle community associated with the current API token.
get_community_memberREADGet a Circle community member by ID.
INPUTS: id
get_postREADGet a Circle basic post by ID.
INPUTS: id
get_space_groupREADGet a Circle space group by ID.
INPUTS: id
list_community_membersREADList Circle community members with optional status and tag filters.
INPUTS: page / per_page / status / member_tag_ids
list_postsREADList Circle basic posts with optional space, status, search, and sort filters.
INPUTS: page / per_page / space_id / space_group_id / status
list_space_groupsREADList Circle space groups with optional name filtering.
INPUTS: page / per_page / name
list_space_membersREADList Circle members in a specific space.
INPUTS: page / per_page / space_id / status
INPUT CONTRACTS
Know what the action needs before it runs.
get_community_member
idREQUIRED- The Circle community member ID.
get_post
idREQUIRED- The Circle post ID.
get_space_group
idREQUIRED- The Circle space group ID.
list_community_members
pageOPTIONAL- The page number to request from Circle.
per_pageOPTIONAL- The number of records to request per page.
statusOPTIONAL- The community member status filter.
member_tag_idsOPTIONAL- Member tag IDs used by Circle to filter community members.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Community
Get details about the Circle community associated with the current API token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_communityVerify with Get Community Member
Get a Circle community member by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_community_memberSAFETY BOUNDARY
Operate Circle with explicit limits
- Authorize Circle with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Circle data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Circle rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Circle task completed successfully.
CONNECTION MODEL
API key
Circle Admin API token used with the Authorization Bearer header.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Circle.