KosmoKrator

productivity

Elastic Email MCP Gateway for AI Agents

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

Elastic Email MCP Gateway

Expose Elastic Email to MCP clients with `kosmokrator mcp:serve --integration=elastic-email`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server.

Install KosmoKrator
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash
Install gateway entry
kosmokrator mcp:gateway:install --integration=elastic-email --write=deny --json
MCP configuration
{
  "mcpServers": {
    "kosmokrator-elastic-email": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=elastic-email",
        "--write=deny"
      ]
    }
  }
}
Serve manually
kosmokrator mcp:serve --integration=elastic-email --write=deny

Client Notes

Use one scoped MCP gateway entry, then adapt the config location to the client or framework.

Claude Code Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry. Claude Code can launch the local kosmo binary directly from the project MCP config.
Cursor Expose selected local integrations to Cursor through KosmoKrator without configuring each service as its own MCP server. Use the same KosmoKrator install and integration credentials that power terminal and headless runs.
Codex Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy. Keep write access denied or ask-based unless the workspace is trusted.
OpenAI Agents SDK Attach KosmoKrator integration tools to OpenAI Agents SDK workflows through a local MCP gateway. Use headless JSON commands for CI-style execution and MCP for agent tool discovery.
Claude Agent SDK Give Claude Agent SDK workflows access to KosmoKrator integrations through a local MCP server. Use a narrow integration list so the agent does not load unrelated tools.
Vercel AI SDK Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts. Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.
LangChain Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls. Keep the gateway scoped to the integration and operation class needed by the chain.
LangGraph Run KosmoKrator integration calls from LangGraph nodes while preserving local credentials and permissions. Headless CLI calls fit repeatable graph edges; MCP fits exploratory agent nodes.
CrewAI Expose KosmoKrator integrations to CrewAI workers as scoped local tools. Use per-worker integration scopes to avoid giving every worker every tool.
Generic MCP Clients Connect any stdio-compatible MCP client to local KosmoKrator integration tools. Start with read-only write policy and expand only for trusted projects.

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names.

MCP toolSource functionType
integration__elastic_email__elasticemail_add_contacts_to_list elastic-email.elasticemail_add_contacts_to_list Write write
integration__elastic_email__elasticemail_api_get elastic-email.elasticemail_api_get Read read
integration__elastic_email__elasticemail_api_post elastic-email.elasticemail_api_post Read read
integration__elastic_email__elasticemail_create_contact elastic-email.elasticemail_create_contact Write write
integration__elastic_email__elasticemail_delete_contact elastic-email.elasticemail_delete_contact Write write
integration__elastic_email__elasticemail_get_campaign elastic-email.elasticemail_get_campaign Read read
integration__elastic_email__elasticemail_get_campaign_statistics elastic-email.elasticemail_get_campaign_statistics Read read
integration__elastic_email__elasticemail_get_contact elastic-email.elasticemail_get_contact Read read
integration__elastic_email__elasticemail_get_email_status elastic-email.elasticemail_get_email_status Read read
integration__elastic_email__elasticemail_get_list elastic-email.elasticemail_get_list Read read
integration__elastic_email__elasticemail_get_statistics elastic-email.elasticemail_get_statistics Read read
integration__elastic_email__elasticemail_get_template elastic-email.elasticemail_get_template Read read
integration__elastic_email__elasticemail_list_campaigns elastic-email.elasticemail_list_campaigns Read read
integration__elastic_email__elasticemail_list_contacts elastic-email.elasticemail_list_contacts Read read
integration__elastic_email__elasticemail_list_email_events elastic-email.elasticemail_list_email_events Read read
integration__elastic_email__elasticemail_list_events elastic-email.elasticemail_list_events Read read
integration__elastic_email__elasticemail_list_files elastic-email.elasticemail_list_files Read read
integration__elastic_email__elasticemail_list_list_contacts elastic-email.elasticemail_list_list_contacts Read read
integration__elastic_email__elasticemail_list_lists elastic-email.elasticemail_list_lists Read read
integration__elastic_email__elasticemail_list_suppressions elastic-email.elasticemail_list_suppressions Read read
integration__elastic_email__elasticemail_list_templates elastic-email.elasticemail_list_templates Read read
integration__elastic_email__elasticemail_pause_campaign elastic-email.elasticemail_pause_campaign Write write
integration__elastic_email__elasticemail_remove_contacts_from_list elastic-email.elasticemail_remove_contacts_from_list Write write
integration__elastic_email__elasticemail_send_bulk_email elastic-email.elasticemail_send_bulk_email Write write
integration__elastic_email__elasticemail_send_email elastic-email.elasticemail_send_email Write write
integration__elastic_email__elasticemail_update_contact elastic-email.elasticemail_update_contact Write write

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.