ClickSend MCP integration for AI agents.
Connect AI agents to ClickSend through 13 structured actions, including create contact list, create contact, delete contact, and calculate sms price. Review…
- ACTION CONTRACTS
- 13
- 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 ClickSend integration exposes
The ClickSend Agent App exposes 13 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent create a clicksend contact list, create a contact in a clicksend contact list, and delete a clicksend contact by list id and contact 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 ClickSend account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ClickSend capabilities.
Showing 12 of 13 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
create_contact_listREADCreate a ClickSend contact list.
INPUTS: list_name
create_contactWRITECreate a contact in a ClickSend contact list.
INPUTS: list_id / contact
delete_contactHIGH IMPACTDelete a ClickSend contact by list ID and contact ID.
INPUTS: list_id / contact_id
calculate_sms_priceREVIEWCalculate the ClickSend price for one or more SMS messages without sending them.
INPUTS: messages / shorten_urls
delete_contact_listHIGH IMPACTDelete a ClickSend contact list by ID.
INPUTS: list_id
get_accountREADGet the ClickSend account profile associated with the configured credentials.
get_contactREADGet one ClickSend contact by list ID and contact ID.
INPUTS: list_id / contact_id
get_contact_listREADGet one ClickSend contact list by ID.
INPUTS: list_id
list_contact_listsREADList ClickSend contact lists with pagination controls.
INPUTS: page / limit
list_contactsREADList contacts in a ClickSend contact list.
INPUTS: list_id / page / limit
send_smsWRITESend one or more SMS messages through ClickSend.
INPUTS: messages / shorten_urls
update_contactWRITEUpdate a ClickSend contact by list ID and contact ID.
INPUTS: list_id / contact_id / contact
INPUT CONTRACTS
Know what the action needs before it runs.
create_contact_list
list_nameREQUIRED- The ClickSend contact list name.
create_contact
list_idREQUIRED- The ClickSend contact list ID.
contactREQUIRED- A ClickSend contact payload.
delete_contact
list_idREQUIRED- The ClickSend contact list ID.
contact_idREQUIRED- The ClickSend contact ID.
calculate_sms_price
messagesREQUIRED- SMS messages to send or price.
shorten_urlsOPTIONAL- Whether ClickSend should shorten URLs in the SMS body.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Create Contact List
Create a ClickSend contact list. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
create_contact_listControl Create Contact
Create a contact in a ClickSend contact list. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Account
Get the ClickSend account profile associated with the configured credentials. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_accountSAFETY BOUNDARY
Operate ClickSend with explicit limits
- Authorize ClickSend with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_contact` and `delete_contact_list` 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 ClickSend rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ClickSend task completed successfully.
CONNECTION MODEL
API key
ClickSend API key used as the Basic Auth password. Find or create it in the ClickSend Dashboard under Credentials: https://dashboard.clicksend.com/#/account/subaccount.
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
- 3
- HIGH IMPACT
- 2
- 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 ClickSend.