Can I use Elastic Email as a CLI?

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

Can I expose Elastic Email through MCP?

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

Where are Elastic Email credentials stored?

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

Can I deny write access for Elastic Email MCP tools?

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

Elastic Email MCP Integration for Codex

Connect Elastic Email to Codex through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 4 read 2 write API key auth

Submit Elastic Email feedback View package source

Connect Elastic Email to Codex

Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy.

Register kosmo mcp:serve as a local stdio server and choose the integration allowlist. The gateway is local, scoped to this integration, and starts with --write=deny so Codex can inspect read-capable tools without receiving write access by default.

Elastic Email MCP Config for Codex

Keep write access denied or ask-based unless the workspace is trusted.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Elastic Email 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.

Elastic Email Tools Visible to Codex

Codex sees stable MCP tool names generated from the Elastic Email integration catalog.

MCP tool	Source function	Type	Description
`integration__elastic_email__elasticemail_send_email`	`elastic-email.elasticemail_send_email`	Write	Send a transactional email via Elastic Email. Provide the recipient address, subject, and HTML body.
`integration__elastic_email__elasticemail_list_templates`	`elastic-email.elasticemail_list_templates`	Read	List email templates available in your Elastic Email account.
`integration__elastic_email__elasticemail_get_template`	`elastic-email.elasticemail_get_template`	Read	Get details of a specific email template by its ID from Elastic Email.
`integration__elastic_email__elasticemail_list_contacts`	`elastic-email.elasticemail_list_contacts`	Read	List contacts from your Elastic Email account.
`integration__elastic_email__elasticemail_create_contact`	`elastic-email.elasticemail_create_contact`	Write	Create or add a contact in Elastic Email. Optionally assign the contact to an existing list.
`integration__elastic_email__elasticemail_get_current_user`	`elastic-email.elasticemail_get_current_user`	Read	Get information about the currently authenticated Elastic Email user account.

Related Elastic Email Pages

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