Can I use MailerLite as a CLI?

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

Can I expose MailerLite through MCP?

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

Where are MailerLite credentials stored?

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

Can I deny write access for MailerLite MCP tools?

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

MailerLite MCP Gateway for AI Agents

Expose MailerLite tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

8 functions 4 read 4 write API key auth

Submit MailerLite feedback View package source

MailerLite MCP Gateway

Expose MailerLite to MCP clients with `kosmokrator mcp:serve --integration=mailerlite`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.

curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

kosmokrator mcp:gateway:install --integration=mailerlite --write=deny --json

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

Serve Manually

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

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP tool	Source function	Type
`integration__mailerlite__mailerlite_list_subscribers`	`mailerlite.mailerlite_list_subscribers`	Read `read`
`integration__mailerlite__mailerlite_get_subscriber`	`mailerlite.mailerlite_get_subscriber`	Read `read`
`integration__mailerlite__mailerlite_create_subscriber`	`mailerlite.mailerlite_create_subscriber`	Write `write`
`integration__mailerlite__mailerlite_update_subscriber`	`mailerlite.mailerlite_update_subscriber`	Write `write`
`integration__mailerlite__mailerlite_delete_subscriber`	`mailerlite.mailerlite_delete_subscriber`	Write `write`
`integration__mailerlite__mailerlite_list_groups`	`mailerlite.mailerlite_list_groups`	Read `read`
`integration__mailerlite__mailerlite_add_subscriber_to_group`	`mailerlite.mailerlite_add_subscriber_to_group`	Write `write`
`integration__mailerlite__mailerlite_get_current_user`	`mailerlite.mailerlite_get_current_user`	Read `read`

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.