Can I use Intercom as a CLI?

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

Can I expose Intercom through MCP?

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

Where are Intercom credentials stored?

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

Can I deny write access for Intercom MCP tools?

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

communication

Intercom CLI for Shell Scripts

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

7 functions 6 read 1 write Bearer token auth

Submit Intercom feedback View package source

Intercom 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 Intercom CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Intercom CLI for Shell Scripts
kosmokrator integrations:configure intercom --set access_token="$INTERCOM_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call intercom.intercom_list_conversations '{"limit":1,"starting_after":"example_starting_after","sort_order":"example_sort_order","status":"example_status"}' --json

Discovery Before Execution

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

kosmo integrations:docs intercom --json
kosmo integrations:docs intercom.intercom_list_conversations --json
kosmo integrations:schema intercom.intercom_list_conversations --json
kosmo integrations:search "Intercom" --json
kosmo integrations:list --json

Useful Intercom CLI Functions

Function	Type	Parameters	Description
`intercom.intercom_list_conversations`	Read	limit, starting_after, sort_order, status	List Intercom conversations with pagination and sorting. Returns conversation IDs, created dates, and state. Use limit, starting_after, and sort_order for pagination and ordering.
`intercom.intercom_get_conversation`	Read	conversation_id	Retrieve an Intercom conversation by its ID. Returns the full conversation including message parts, contacts, and metadata.
`intercom.intercom_create_conversation`	Write	user_id, body	Create a new conversation in Intercom. Requires a user_id (Intercom contact ID) and a message body. Returns the created conversation with its ID.
`intercom.intercom_list_contacts`	Read	limit, starting_after	List Intercom contacts with pagination. Returns contact IDs, emails, names, and roles. Use limit and starting_after for pagination.
`intercom.intercom_get_contact`	Read	contact_id	Retrieve an Intercom contact by its ID. Returns the contact's ID, email, name, phone, role, and custom attributes.
`intercom.intercom_list_companies`	Read	limit, starting_after	List Intercom companies with pagination. Returns company IDs, names, and employee counts. Use limit and starting_after for pagination.
`intercom.intercom_get_current_user`	Read	none	Retrieve the currently authenticated Intercom admin user. Returns the admin's ID, name, email, and avatar. Useful for identifying which workspace or token is in use.

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 Intercom CLI Pages

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