Can I use Constant Contact as a CLI?

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

Can I expose Constant Contact through MCP?

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

Where are Constant Contact credentials stored?

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

Can I deny write access for Constant Contact MCP tools?

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

Constant Contact CLI for Headless Automation

Use the Constant Contact CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

6 functions 5 read 1 write Manual OAuth token auth

Submit Constant Contact feedback View package source

Constant Contact CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Constant Contact CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Constant Contact CLI for Headless Automation
kosmokrator integrations:configure constant_contact --set access_token="$CONSTANT_CONTACT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call constant_contact.constantcontact_list_contacts '{"limit":1,"cursor":"example_cursor","status":"example_status"}' --json

Discovery Before Execution

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

kosmo integrations:docs constant_contact --json
kosmo integrations:docs constant_contact.constantcontact_list_contacts --json
kosmo integrations:schema constant_contact.constantcontact_list_contacts --json
kosmo integrations:search "Constant Contact" --json
kosmo integrations:list --json

Useful Constant Contact CLI Functions

Function	Type	Parameters	Description
`constant_contact.constantcontact_list_contacts`	Read	limit, cursor, status	List contacts from Constant Contact. Supports pagination and filtering by status (active, unconfirmed, opted_out, non_subscriber).
`constant_contact.constantcontact_get_contact`	Read	contact_id	Get detailed information for a single Constant Contact contact by ID, including email, name, phone, address, and list memberships.
`constant_contact.constantcontact_create_contact`	Write	email, first_name, last_name, list_ids	Create a new contact in Constant Contact. Requires an email address. Optionally set first name, last name, and assign to lists.
`constant_contact.constantcontact_list_campaigns`	Read	limit, cursor	List email campaigns from Constant Contact. Supports cursor-based pagination.
`constant_contact.constantcontact_list_lists`	Read	none	List all contact lists in Constant Contact. Returns list IDs, names, and membership counts. Use list IDs when creating contacts.
`constant_contact.constantcontact_get_current_user`	Read	none	Get the authenticated user's Constant Contact account information, including name, email, and organization details.

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 Constant Contact CLI Pages

CI Constant Contact CLI for CI. Cron Jobs Constant Contact CLI for cron jobs. Shell Scripts Constant Contact CLI for shell scripts. Coding Agents Constant Contact CLI for coding agents.