Can I use Lemlist as a CLI?

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

Can I expose Lemlist through MCP?

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

Where are Lemlist credentials stored?

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

Can I deny write access for Lemlist MCP tools?

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

sales

Lemlist MCP Integration for CrewAI

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

7 functions 6 read 1 write Username and password auth

Submit Lemlist feedback View package source

Connect Lemlist 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.

Lemlist MCP Config for CrewAI

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Lemlist 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.

Lemlist Tools Visible to CrewAI

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

MCP tool	Source function	Type	Description
`integration__lemlist__lemlist_list_campaigns`	`lemlist.lemlist_list_campaigns`	Read	List all outreach campaigns in Lemlist. Returns campaign IDs, names, statuses, and other metadata.
`integration__lemlist__lemlist_get_campaign`	`lemlist.lemlist_get_campaign`	Read	Get details of a specific Lemlist campaign by ID. Returns the full campaign configuration and statistics.
`integration__lemlist__lemlist_list_leads`	`lemlist.lemlist_list_leads`	Read	List leads in a specific Lemlist campaign. Returns lead contact information, email status, and campaign progress.
`integration__lemlist__lemlist_add_lead`	`lemlist.lemlist_add_lead`	Write	Add a lead to a Lemlist campaign. The lead will be queued for outreach according to the campaign schedule.
`integration__lemlist__lemlist_list_teams`	`lemlist.lemlist_list_teams`	Read	List all teams in the Lemlist account. Returns team names, member lists, and configuration.
`integration__lemlist__lemlist_list_subaccounts`	`lemlist.lemlist_list_subaccounts`	Read	List all sub-accounts in Lemlist. Returns sub-account names, statuses, and usage details.
`integration__lemlist__lemlist_get_current_user`	`lemlist.lemlist_get_current_user`	Read	Get the profile of the currently authenticated Lemlist user. Returns name, email, plan, and account details.

Related Lemlist Pages

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