Courier MCP integration for AI agents.
Connect AI agents to Courier through 11 structured actions, including add list subscribers, merge profile, and delete list. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 11
- 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 Courier integration exposes
The Courier Agent App exposes 11 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent add courier recipients to a subscription list without replacing existing members, merge values into a courier user profile or create it when missing, and delete a courier subscription list by list 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 Courier account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Courier capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
add_list_subscribersREADAdd Courier recipients to a subscription list without replacing existing members.
INPUTS: listId / recipients
merge_profileWRITEMerge values into a Courier user profile or create it when missing.
INPUTS: userId / profile
delete_listHIGH IMPACTDelete a Courier subscription list by list ID.
INPUTS: listId
delete_profileHIGH IMPACTDelete a Courier user profile by user ID.
INPUTS: userId
get_listREADReturn a Courier subscription list by list ID.
INPUTS: listId
get_profileREADReturn a Courier user profile and preferences by user ID.
INPUTS: userId
list_list_subscriptionsREADList subscriptions for a Courier subscription list.
INPUTS: listId / cursor
list_listsREADList Courier subscription lists with optional cursor and pattern filters.
INPUTS: cursor / pattern
send_messageWRITESend a Courier message to one or more recipients.
INPUTS: message / idempotencyKey
unsubscribe_list_subscriberREADUnsubscribe one Courier user profile from a subscription list.
INPUTS: listId / userId
upsert_listREADCreate or replace a Courier subscription list.
INPUTS: listId / name / preferences
INPUT CONTRACTS
Know what the action needs before it runs.
add_list_subscribers
listIdOPTIONAL- The Courier list ID.
recipientsOPTIONAL- The Courier recipients to subscribe.
merge_profile
userIdOPTIONAL- The Courier user ID associated with the profile.
profileOPTIONAL- The Courier profile object to merge into the user profile.
delete_list
listIdOPTIONAL- The Courier list ID.
delete_profile
userIdOPTIONAL- The Courier user ID associated with the profile.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Add List Subscribers
Add Courier recipients to a subscription list without replacing existing members. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
add_list_subscribersControl Merge Profile
Merge values into a Courier user profile or create it when missing. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
merge_profileVerify with Get List
Return a Courier subscription list by list ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_listSAFETY BOUNDARY
Operate Courier with explicit limits
- Authorize Courier with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_list` and `delete_profile` 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 Courier rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Courier task completed successfully.
CONNECTION MODEL
API key
Courier API key used with the Authorization Bearer header. Create or manage keys in the Courier dashboard API Keys page: https://app.courier.com/settings/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
- 7
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 2
- 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 Courier.