Can I use IFTTT as a CLI?

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

Can I expose IFTTT through MCP?

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

Where are IFTTT credentials stored?

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

Can I deny write access for IFTTT MCP tools?

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

productivity

IFTTT MCP Integration for Codex

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

7 functions 7 read 0 write Bearer token auth

Submit IFTTT feedback View package source

Connect IFTTT 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.

IFTTT MCP Config for Codex

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

IFTTT Tools Visible to Codex

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

MCP tool	Source function	Type	Description
`integration__ifttt__ifttt_list_services`	`ifttt.ifttt_list_services`	Read	List services in IFTTT with optional filters.
`integration__ifttt__ifttt_get_service`	`ifttt.ifttt_get_service`	Read	Get detailed information about an IFTTT service.
`integration__ifttt__ifttt_list_applets`	`ifttt.ifttt_list_applets`	Read	List applets in IFTTT with optional filters.
`integration__ifttt__ifttt_get_applet`	`ifttt.ifttt_get_applet`	Read	Get detailed information about an IFTTT applet.
`integration__ifttt__ifttt_list_connections`	`ifttt.ifttt_list_connections`	Read	List connections in IFTTT with optional filters.
`integration__ifttt__ifttt_get_connection`	`ifttt.ifttt_get_connection`	Read	Get detailed information about an IFTTT connection.
`integration__ifttt__ifttt_get_current_user`	`ifttt.ifttt_get_current_user`	Read	Get the currently authenticated IFTTT user.

Related IFTTT Pages

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