Appcircle MCP integration for AI agents.

Connect AI agents to Appcircle through 4 structured actions, including list build profiles, list distribution profiles, and list enterprise store profiles. R…

ACTION CONTRACTS
4
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 Appcircle integration exposes

The Appcircle Agent App exposes 4 provider-backed actions for developer tools work. Its current contract lets an authorized agent list appcircle build profiles for the connected organization, list appcircle testing distribution profiles for the connected organization, and list appcircle enterprise app store profiles for the connected organization. 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 Appcircle account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.

VERIFIED ACTION SAMPLE

Real Appcircle capabilities.

Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.

list_build_profilesREAD

List Appcircle Build profiles for the connected organization.

INPUTS: page / size / search

list_distribution_profilesREAD

List Appcircle Testing Distribution profiles for the connected organization.

INPUTS: page / size / search

list_enterprise_store_profilesREAD

List Appcircle Enterprise App Store profiles for the connected organization.

INPUTS: page / size / search

list_organizationsREAD

List Appcircle organizations available to the connected API key.

INPUTS: page / perPage / search

INPUT CONTRACTS

Know what the action needs before it runs.

list_build_profiles

pageOPTIONAL
The one-based result page.
sizeOPTIONAL
The number of profiles to request per page.
searchOPTIONAL
A profile name search term.

list_distribution_profiles

pageOPTIONAL
The one-based result page.
sizeOPTIONAL
The number of profiles to request per page.
searchOPTIONAL
A profile name search term.

list_enterprise_store_profiles

pageOPTIONAL
The one-based result page.
sizeOPTIONAL
The number of profiles to request per page.
searchOPTIONAL
A profile name search term.

list_organizations

pageOPTIONAL
The one-based result page.
perPageOPTIONAL
The number of organizations to request per page.
searchOPTIONAL
An organization name search term.

PROVIDER-SPECIFIC WORKFLOWS

Jobs this Agent App can support

Inspect List Build Profiles

List Appcircle Build profiles for the connected organization. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.

list_build_profiles

Verify with List Distribution Profiles

List Appcircle Testing Distribution profiles for the connected organization. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.

list_distribution_profiles

SAFETY BOUNDARY

Operate Appcircle with explicit limits

  • Authorize Appcircle with API key and grant only the provider access required by the selected actions.
  • The current action names appear read-oriented, but returned Appcircle 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 Appcircle rather than assuming unrestricted access.
  • After a call, inspect the structured result and execution record before reporting that the Appcircle task completed successfully.

CONNECTION MODEL

API key

Appcircle organization API key secret. Create one under My Organization > Security > API Keys: https://docs.appcircle.io/account/my-organization/security/api-keys.

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
4
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 Appcircle.

Official Appcircle website

ONE CONNECTION. REAL WORK.

Give your agent software it can use.

Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.

EXPLORE AGENT APPS