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 MCP Integration for CrewAI

Connect Lasso CRM to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API token auth

Submit Lasso CRM feedback View package source

Connect Lasso CRM to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Lasso CRM MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-lasso": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=lasso",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=lasso --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Lasso CRM instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Lasso CRM Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Lasso CRM integration catalog.

MCP tool	Source function	Type	Description
`integration__lasso__lasso_list_contacts`	`lasso.lasso_list_contacts`	Read	List contacts (registrants) in Lasso CRM. Optionally filter by project ID or other criteria. Supports pagination.
`integration__lasso__lasso_get_contact`	`lasso.lasso_get_contact`	Read	Get full details for a single contact (registrant) in Lasso CRM, including emails, phone numbers, and associated information.
`integration__lasso__lasso_create_contact`	`lasso.lasso_create_contact`	Write	Create a new contact (registrant) in Lasso CRM. Provide at least a first name or last name, and optionally email, phone, and other details.
`integration__lasso__lasso_list_deals`	`lasso.lasso_list_deals`	Read	List deals (sales) in Lasso CRM. Optionally filter by project ID or status. Supports pagination.
`integration__lasso__lasso_get_deal`	`lasso.lasso_get_deal`	Read	Get full details for a single deal (sale) in Lasso CRM, including pricing, unit details, and associated contacts.
`integration__lasso__lasso_list_inventory`	`lasso.lasso_list_inventory`	Read	List available inventory (units/lots) in Lasso CRM. Optionally filter by project ID or status. Supports pagination.
`integration__lasso__lasso_get_current_user`	`lasso.lasso_get_current_user`	Read	Get the profile of the currently authenticated Lasso CRM user — name, email, organization, and other account details.

Related Lasso CRM Pages

Lasso CRM CLIUse direct JSON commands instead of MCP discovery. Lasso CRM MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.