Can I use EmailOctopus as a CLI?

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

Can I expose EmailOctopus through MCP?

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

Where are EmailOctopus credentials stored?

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

Can I deny write access for EmailOctopus MCP tools?

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

EmailOctopus MCP Gateway for AI Agents

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

6 functions 5 read 1 write API key auth

Submit EmailOctopus feedback View package source

EmailOctopus MCP Gateway

Expose EmailOctopus to MCP clients with `kosmokrator mcp:serve --integration=email-octopus`.

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=email-octopus --write=deny --json

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

Serve Manually

kosmokrator mcp:serve --integration=email-octopus --write=deny

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP tool	Source function	Type
`integration__email_octopus__emailoctopus_list_contacts`	`email-octopus.emailoctopus_list_contacts`	Read `read`
`integration__email_octopus__emailoctopus_get_contact`	`email-octopus.emailoctopus_get_contact`	Read `read`
`integration__email_octopus__emailoctopus_create_contact`	`email-octopus.emailoctopus_create_contact`	Write `write`
`integration__email_octopus__emailoctopus_list_campaigns`	`email-octopus.emailoctopus_list_campaigns`	Read `read`
`integration__email_octopus__emailoctopus_get_campaign`	`email-octopus.emailoctopus_get_campaign`	Read `read`
`integration__email_octopus__emailoctopus_get_current_user`	`email-octopus.emailoctopus_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.