Model Context Protocol (MCP) server

Knock ships a remote MCP server at mcp.knock.app/mcp that exposes the primitives of Knock to LLMs and AI via the Model Context Protocol (MCP) so that your AI agents can discover and use Knock via tool calling.

Here are some examples of how you can use the MCP server in your workflow:

• Create workflows using natural language. "Create a welcome email workflow for my B2B SaaS app."
• Trigger a specific workflow to test your integration. "Trigger the comment-created workflow for Dennis Nedry."
• Create a set of test user and tenant data in your account. "Create a user called Dennis Nedry and a tenant called acme-corp."

The Knock MCP server is a remote server—no local installation or Node.js setup is required. You connect to https://mcp.knock.app/mcp directly from your MCP client and authenticate using your Knock account via OAuth. This means your Knock credentials are managed securely through the standard sign-in flow rather than requiring a service token.

We've added setup instructions below for both Cursor and Claude Desktop, but the same instructions apply to any other MCP client-compatible application.

1. Go to Settings > Cursor Settings and find the "Tools & Integrations" section.
2. Click "New MCP server" under MCP Tools.
3. Inside your mcp.json file under the mcpServers key, add the following:

4. When Cursor prompts you to authenticate, sign in with your Knock account.

1. Open the Claude Desktop settings and find the "Developer" section.
2. Click "Edit Config."
3. Open your claude_desktop_config.json file in your preferred text editor.
4. Add the following contents to the file (or add to the mcpServers section if it exists):

5. Restart Claude Desktop. When you first use a Knock tool, you'll be prompted to sign in with your Knock account.

When connecting to the Knock MCP server, you can choose exactly which groups of tools to enable. Limiting the active tool groups to only what you need keeps the tool list manageable and reduces the risk of unintended changes.

Group	Description
Manage resources	Create and manage notification workflows, channels, templates, email layouts, partials, and other configuration
Commits	Commit and promote changes across environments
Debug	Inspect environments and view sent message logs
Manage data	Manage users, tenants, and object data
Documentation	Search Knock documentation

The MCP server ships with tools to interact with all Knock resources. You can find the full list of available tools in the tools reference of the Knock Agent Toolkit, which the MCP server is built on top of.

Please note that at this time, the MCP server does not ship with any tools to delete resources. This is intentional to prevent the accidental deletion of resources in your Knock account.

The Knock MCP server exposes a full suite of tools for creating and managing workflows. Using the MCP server you can:

• Create a workflow with natural language: "create a workflow that sends a welcome email to new users"
• Create a delay or batch step within your workflow: "delay for 3 days" or "batch for 10 minutes"
• Create an email step within your workflow: "create a credit card expiring email with a link back to the dashboard"
• Create an SMS, push, or in-app feed step within your workflow

Using these tools you can create a complex prompt that describes one or more workflows that you'd like to create with natural language.

The Knock MCP server also supports exposing your workflows as individual tools. This gives the LLM a specific and precise interface for invoking workflow triggers, including describing the data trigger requirements for your workflows.

By default, the MCP server will not expose any workflows as tools. To opt into this behavior, contact us or refer to your MCP client's tool configuration options.

• Building with LLMs
• Knock Agent Toolkit