Can I use ClickSend as a CLI?

Yes. KosmoKrator exposes a ClickSend CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose ClickSend through MCP?

Yes. The KosmoKrator MCP gateway can expose selected ClickSend tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are ClickSend credentials stored?

ClickSend credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for ClickSend MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

communication

ClickSend CLI for Shell Scripts

Use the ClickSend CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

10 functions 6 read 4 write API key auth

Submit ClickSend feedback View package source

ClickSend CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The ClickSend CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# ClickSend CLI for Shell Scripts
kosmokrator integrations:configure clicksend --set username="$CLICKSEND_USERNAME" --set api_key="$CLICKSEND_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call clicksend.clicksend_get_account_balance '{}' --json

Discovery Before Execution

Agents and scripts can inspect ClickSend docs and schemas before choosing a function.

kosmo integrations:docs clicksend --json
kosmo integrations:docs clicksend.clicksend_get_account_balance --json
kosmo integrations:schema clicksend.clicksend_get_account_balance --json
kosmo integrations:search "ClickSend" --json
kosmo integrations:list --json

Useful ClickSend CLI Functions

Function	Type	Parameters	Description
`clicksend.clicksend_get_account_balance`	Read	none	Get the current ClickSend account balance.
`clicksend.clicksend_get_email_history`	Read	limit, page	Get email message history from ClickSend with pagination.
`clicksend.clicksend_get_sms_history`	Read	date_from, date_to, limit, page	Get SMS message history from ClickSend. Supports date range filtering and pagination.
`clicksend.clicksend_get_sms_price`	Read	messages	Get pricing for SMS messages before sending. Uses the same message format as send SMS but returns cost estimates only.
`clicksend.clicksend_get_voice_history`	Read	limit, page	Get voice message history from ClickSend with pagination.
`clicksend.clicksend_list_contact_lists`	Read	limit, page	List all contact lists from ClickSend with pagination.
`clicksend.clicksend_send_email`	Write	to, subject, body, from_email_address, from_name	Send an email message via ClickSend. Requires recipient, subject, and body.
`clicksend.clicksend_send_post_letter`	Write	file_url, template_id, recipients, duplex	Send a post letter via ClickSend. Provide a file URL or template ID with recipient details.
`clicksend.clicksend_send_sms`	Write	messages	Send one or more SMS messages via ClickSend. Each message requires a "to" phone number and "body" text.
`clicksend.clicksend_send_voice`	Write	messages	Send one or more voice messages via ClickSend. Each message requires a "to" phone number and "body" text.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related ClickSend CLI Pages

CI ClickSend CLI for CI. Cron Jobs ClickSend CLI for cron jobs. Headless Automation ClickSend CLI for headless automation. Coding Agents ClickSend CLI for coding agents.