Can I use Lasso CRM as a CLI?

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

Can I expose Lasso CRM through MCP?

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

Where are Lasso CRM credentials stored?

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

Can I deny write access for Lasso CRM MCP tools?

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

sales

Lasso CRM CLI for CI

Use the Lasso CRM CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API token auth

Submit Lasso CRM feedback View package source

Lasso CRM CLI for CI

Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.

Use this shape when a pipeline needs to read or update an external service. The Lasso CRM CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Lasso CRM CLI for CI
kosmokrator integrations:configure lasso --set token="$LASSO_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call lasso.lasso_list_contacts '{"project_id":"example_project_id","limit":1,"page":1}' --json

Discovery Before Execution

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

kosmo integrations:docs lasso --json
kosmo integrations:docs lasso.lasso_list_contacts --json
kosmo integrations:schema lasso.lasso_list_contacts --json
kosmo integrations:search "Lasso CRM" --json
kosmo integrations:list --json

Useful Lasso CRM CLI Functions

Function	Type	Parameters	Description
`lasso.lasso_list_contacts`	Read	project_id, limit, page	List contacts (registrants) in Lasso CRM. Optionally filter by project ID or other criteria. Supports pagination.
`lasso.lasso_get_contact`	Read	id	Get full details for a single contact (registrant) in Lasso CRM, including emails, phone numbers, and associated information.
`lasso.lasso_create_contact`	Write	first_name, last_name, email, phone, project_id, source, notes	Create a new contact (registrant) in Lasso CRM. Provide at least a first name or last name, and optionally email, phone, and other details.
`lasso.lasso_list_deals`	Read	project_id, status, limit, page	List deals (sales) in Lasso CRM. Optionally filter by project ID or status. Supports pagination.
`lasso.lasso_get_deal`	Read	id	Get full details for a single deal (sale) in Lasso CRM, including pricing, unit details, and associated contacts.
`lasso.lasso_list_inventory`	Read	project_id, status, limit, page	List available inventory (units/lots) in Lasso CRM. Optionally filter by project ID or status. Supports pagination.
`lasso.lasso_get_current_user`	Read	none	Get the profile of the currently authenticated Lasso CRM user — name, email, organization, and other account 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 Lasso CRM CLI Pages

Cron Jobs Lasso CRM CLI for cron jobs. Shell Scripts Lasso CRM CLI for shell scripts. Headless Automation Lasso CRM CLI for headless automation. Coding Agents Lasso CRM CLI for coding agents.