Can I use Moosend as a CLI?

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

Can I expose Moosend through MCP?

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

Where are Moosend credentials stored?

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

Can I deny write access for Moosend MCP tools?

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

other

Moosend MCP Integration for LangChain

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

7 functions 5 read 2 write API key auth

Submit Moosend feedback View package source

Connect Moosend to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Moosend MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Moosend Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Moosend integration catalog.

MCP tool	Source function	Type	Description
`integration__moosend__moosend_list_mailing_lists`	`moosend.moosend_list_mailing_lists`	Read	List all mailing lists in your Moosend account. Returns list IDs, names, and subscriber counts.
`integration__moosend__moosend_get_mailing_list`	`moosend.moosend_get_mailing_list`	Read	Get detailed information about a specific mailing list in Moosend, including subscriber counts and settings.
`integration__moosend__moosend_create_mailing_list`	`moosend.moosend_create_mailing_list`	Write	Create a new mailing list in Moosend. Returns the newly created list with its ID.
`integration__moosend__moosend_list_subscribers`	`moosend.moosend_list_subscribers`	Read	List subscribers for a specific mailing list in Moosend. Supports filtering by status and pagination.
`integration__moosend__moosend_add_subscriber`	`moosend.moosend_add_subscriber`	Write	Add a new subscriber to a Moosend mailing list. Requires an email address; name is optional.
`integration__moosend__moosend_list_campaigns`	`moosend.moosend_list_campaigns`	Read	List all email campaigns in your Moosend account. Supports filtering by status and pagination.
`integration__moosend__moosend_get_current_user`	`moosend.moosend_get_current_user`	Read	Get the current authenticated Moosend user. Useful as a health check to verify API connectivity.

Related Moosend Pages

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