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.

productivity

Knock MCP, CLI, and Lua Integration for AI Agents

Knock integration docs for AI agents: MCP gateway setup, Knock CLI commands, Lua API reference, credentials, and function schemas.

Knock for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Agent Surfaces

Knock CLIHeadless setup, JSON output, direct function calls. Knock MCPExpose selected tools to local MCP clients. Knock LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: knock
route_slug: knock
package: knock
auth_strategy: api_key
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

Function Catalog

Function	Type	Parameters	Description
`knock.knock_list_workflows`	Read `read`	2	List notification workflows from Knock. Returns workflow IDs and details you can use to trigger or inspect workflows.
`knock.knock_get_workflow`	Read `read`	1	Get details of a specific notification workflow in Knock, including its steps and configuration.
`knock.knock_trigger_workflow`	Write `write`	4	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.
`knock.knock_list_messages`	Read `read`	3	List notification messages from Knock. Optionally filter by delivery status (e.g., sent, delivered, undelivered).
`knock.knock_get_message`	Read `read`	1	Get details of a specific notification message in Knock, including its content, delivery status, and channel.
`knock.knock_list_recipients`	Read `read`	2	List notification recipients from Knock. Returns recipient identifiers and their preferences.
`knock.knock_get_current_user`	Read `read`	0	Get the currently authenticated Knock user. Useful for verifying API credentials and inspecting account details.