Can I use Make.com as a CLI?

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

Can I expose Make.com through MCP?

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

Where are Make.com credentials stored?

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

Can I deny write access for Make.com MCP tools?

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

productivity

Make.com CLI for Coding Agents

Use the Make.com CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write API token auth

Submit Make.com feedback View package source

Make.com CLI for Coding Agents

Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

Use this pattern when another coding agent needs exact commands and schema discovery. The Make.com CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Make.com CLI for Coding Agents
kosmokrator integrations:configure make-com --set api_token="$MAKE_COM_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call make-com.make_com_list_scenarios '{"organization_id":"example_organization_id","team_id":"example_team_id","folder_id":"example_folder_id","limit":1,"offset":1}' --json

Discovery Before Execution

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

kosmo integrations:docs make-com --json
kosmo integrations:docs make-com.make_com_list_scenarios --json
kosmo integrations:schema make-com.make_com_list_scenarios --json
kosmo integrations:search "Make.com" --json
kosmo integrations:list --json

Useful Make.com CLI Functions

Function	Type	Parameters	Description
`make-com.make_com_list_scenarios`	Read	organization_id, team_id, folder_id, limit, offset	List Make.com scenarios the authenticated user has access to. Supports filtering by organization, team, or folder. Use this to discover scenario IDs needed for other tools.
`make-com.make_com_get_scenario`	Read	id	Get detailed information about a Make.com scenario by ID, including its blueprint, scheduling, and status.
`make-com.make_com_list_executions`	Read	scenario_id, status, limit, offset	List Make.com scenario executions (runs) with optional filters. Filter by scenario ID or execution status. Useful for monitoring scenario health and debugging failed runs.
`make-com.make_com_get_execution`	Read	id	Get detailed information about a Make.com scenario execution (run) by ID, including status, duration, input/output for each module, and any errors.
`make-com.make_com_list_connections`	Read	team_id, limit, offset	List Make.com connections the authenticated user has access to. Supports filtering by team. Use this to inspect connected services and their status.
`make-com.make_com_list_teams`	Read	limit, offset	List Make.com teams (organizations) the authenticated user has access to. Use this to discover team IDs needed for filtering scenarios and connections.
`make-com.make_com_get_current_user`	Read	none	Get the currently authenticated Make.com user's profile, including ID, name, email, and team memberships.

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 Make.com CLI Pages

CI Make.com CLI for CI. Cron Jobs Make.com CLI for cron jobs. Shell Scripts Make.com CLI for shell scripts. Headless Automation Make.com CLI for headless automation.