Appcues MCP integration for AI agents.
Connect AI agents to Appcues through 6 structured actions, including get flow, publish flow, and unpublish flow. Review authentication, inputs, workflows, an…
- ACTION CONTRACTS
- 6
- 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 Appcues integration exposes
The Appcues Agent App exposes 6 provider-backed actions for marketing and data work. Its current contract lets an authorized agent get one appcues flow 2.0 experience by identifier, publish one appcues flow 2.0 experience, and unpublish one appcues flow 2.0 experience. 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 Appcues account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Appcues capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_flowREADGet one Appcues Flow 2.0 experience by identifier.
INPUTS: flow_id
publish_flowHIGH IMPACTPublish one Appcues Flow 2.0 experience.
INPUTS: flow_id
unpublish_flowREVIEWUnpublish one Appcues Flow 2.0 experience.
INPUTS: flow_id
get_tagREADGet one Appcues content tag by identifier.
INPUTS: tag_id
list_flowsREADList Appcues Flow 2.0 experiences for the connected account.
list_tagsREADList content tags for the connected Appcues account.
INPUT CONTRACTS
Know what the action needs before it runs.
get_flow
flow_idOPTIONAL- The Appcues Flow 2.0 identifier.
publish_flow
flow_idOPTIONAL- The Appcues Flow 2.0 identifier.
unpublish_flow
flow_idOPTIONAL- The Appcues Flow 2.0 identifier.
get_tag
tag_idOPTIONAL- The Appcues tag identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Flow
Get one Appcues Flow 2.0 experience by identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_flowControl Publish Flow
Publish one Appcues Flow 2.0 experience. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
publish_flowVerify with Get Tag
Get one Appcues content tag by identifier. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_tagSAFETY BOUNDARY
Operate Appcues with explicit limits
- Authorize Appcues with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `publish_flow` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Appcues rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Appcues task completed successfully.
CONNECTION MODEL
API key
Appcues Public API key. Create it at https://studio.appcues.com/settings/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
- 1
- REVIEW SIGNALS
- 1
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 Appcues.