Can I use Zapier as a CLI?

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

Can I expose Zapier through MCP?

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

Where are Zapier credentials stored?

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

Can I deny write access for Zapier MCP tools?

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

productivity

Zapier MCP Integration for Generic MCP Clients

Connect Zapier to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write Bearer token auth

Submit Zapier feedback View package source

Connect Zapier to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

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

Zapier MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Zapier Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the Zapier integration catalog.

MCP tool	Source function	Type	Description
`integration__zapier__zapier_list_zaps`	`zapier.zapier_list_zaps`	Read	List zaps in Zapier with optional filters.
`integration__zapier__zapier_get_zap`	`zapier.zapier_get_zap`	Read	Get detailed information about a Zapier zap.
`integration__zapier__zapier_list_executions`	`zapier.zapier_list_executions`	Read	List zap executions in Zapier with optional filters.
`integration__zapier__zapier_get_execution`	`zapier.zapier_get_execution`	Read	Get detailed information about a Zapier execution.
`integration__zapier__zapier_list_connections`	`zapier.zapier_list_connections`	Read	List connections in Zapier with optional filters.
`integration__zapier__zapier_get_connection`	`zapier.zapier_get_connection`	Read	Get detailed information about a Zapier connection.
`integration__zapier__zapier_get_current_user`	`zapier.zapier_get_current_user`	Read	Get the currently authenticated Zapier user.

Related Zapier Pages

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