Can I use Knock as a CLI?

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

Can I expose Knock through MCP?

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

Where are Knock credentials stored?

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

Can I deny write access for Knock MCP tools?

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

communication

Knock MCP Integration for Claude Code

Connect Knock to Claude Code through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API key auth

Submit Knock feedback View package source

Connect Knock to Claude Code

Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry.

Add KosmoKrator as a stdio MCP server in the Claude Code project config and select the integrations that should be visible. The gateway is local, scoped to this integration, and starts with --write=deny so Claude Code can inspect read-capable tools without receiving write access by default.

Knock MCP Config for Claude Code

Claude Code can launch the local kosmo binary directly from the project MCP config.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Knock Tools Visible to Claude Code

Claude Code sees stable MCP tool names generated from the Knock integration catalog.

MCP tool	Source function	Type	Description
`integration__knock__knock_list_workflows`	`knock.knock_list_workflows`	Read	List notification workflows from Knock. Returns workflow IDs and details you can use to trigger or inspect workflows.
`integration__knock__knock_get_workflow`	`knock.knock_get_workflow`	Read	Get details of a specific notification workflow in Knock, including its steps and configuration.
`integration__knock__knock_trigger_workflow`	`knock.knock_trigger_workflow`	Write	Trigger a notification workflow in Knock for one or more recipients. The workflow will execute its configured steps (email, Slack, in-app, etc.) for each recipient.
`integration__knock__knock_list_messages`	`knock.knock_list_messages`	Read	List notification messages from Knock. Optionally filter by delivery status (e.g., sent, delivered, undelivered).
`integration__knock__knock_get_message`	`knock.knock_get_message`	Read	Get details of a specific notification message in Knock, including its content, delivery status, and channel.
`integration__knock__knock_list_recipients`	`knock.knock_list_recipients`	Read	List notification recipients from Knock. Returns recipient identifiers and their preferences.
`integration__knock__knock_get_current_user`	`knock.knock_get_current_user`	Read	Get the currently authenticated Knock user. Useful for verifying API credentials and inspecting account details.

Related Knock Pages

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