Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Knock MCP Server for Claude

Manage your Knock notification infrastructure from Claude — create and edit workflows, channels, templates, and email layouts, manage users and tenants, commit changes across environments, and debug message logs — with the official Knock remote MCP server.

by Knock·added 2026-06-18·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • The server is hosted by Knock on Cloudflare Workers and authenticated via OAuth 2.1 + PKCE — no API keys required, but write access to your Knock environment is granted after login.
  • Knock's MCP server has no deletion tools by design, reducing destructive-action risk; all changes are staged and require explicit commit/promote steps.
  • Committing and promoting changes across environments is irreversible — review diffs before asking Claude to promote to production.

Privacy notes

  • Requests include your notification workflow definitions, template content, user/tenant identifiers, and message logs — all processed by Knock's servers.
  • Knock's OAuth flow stores session credentials securely; avoid sharing MCP session tokens.

Prerequisites

  • A Knock account — authenticate via OAuth when prompted on first tool use.
  • Node.js 18+ for `mcp-remote` (Claude Desktop); Claude Code supports `--transport http` natively.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "knock": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.knock.app/mcp"]
    }
  }
}

About this resource

Overview

The Knock MCP Server is the official remote Model Context Protocol server from Knock. It exposes the full Knock notification platform to Claude — workflows, channels, templates, email layouts, user data, and environment management — so you can build and manage your notification infrastructure through natural language. Authentication is via OAuth 2.1 (sign in with your Knock account); no local installation or API keys are required.

The server is deployed on Cloudflare Workers with Durable Objects for stateful MCP sessions, and is licensed under MIT.

Key capabilities

  • Workflow management — create and edit notification workflows via natural language.
  • Channel & template management — manage email, push, SMS, and in-app channels; edit templates and email layouts.
  • Commit & promote — stage resource changes and promote them across environments.
  • User & tenant data — create, update, and inspect Knock users, tenants, and objects.
  • Message log inspection — view sent message logs and debug delivery issues.
  • Documentation search — search Knock docs from within your AI assistant.
  • Management API access — explore Knock's OpenAPI spec and call the Management API via sandboxed JavaScript execution.

How it compares

Server Notification workflows Multi-channel Environment promotion OAuth auth Hosted
Knock MCP Yes Email, push, SMS, in-app Yes Yes Yes (CF Workers)
SendGrid MCP Email only No No API key No
Courier MCP Yes Email, push, SMS Limited API key No
Resend MCP Email only No No API key No

Knock's MCP is unique in offering full workflow lifecycle management (create → edit → commit → promote) across multiple channels without a local install.

Installation

Claude Code

claude mcp add --transport http knock https://mcp.knock.app/mcp

Start Claude Code and run /mcp to authenticate via OAuth.

Claude Desktop

{
  "mcpServers": {
    "knock": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.knock.app/mcp"]
    }
  }
}

Restart Claude Desktop; you will be prompted to authenticate with your Knock account on first use.

Requirements

  • A Knock account.
  • Node.js 18+ (for mcp-remote with Claude Desktop).
  • An MCP client (Claude Code or Claude Desktop).

Security

  • OAuth 2.1 + PKCE authentication — no long-lived API keys to manage.
  • No deletion tools in the MCP server by design — changes require explicit commit and promotion.
  • Review all environment promotions before executing to avoid unintended changes in production.

Source Verification Notes

Verified on 2026-06-18:

  • The official repository github.com/knocklabs/knock-mcp (MIT) confirms the remote endpoint https://mcp.knock.app/mcp, OAuth 2.1 + PKCE auth, Cloudflare Workers deployment, and the no-deletion-by-design policy.
  • Knock's developer documentation at docs.knock.app/developer-tools/mcp-server documents the Claude Code and Claude Desktop installation commands, OAuth authentication flow, and the full capability set.
  • Claude Code's MCP documentation describes the --transport http flag used in the installation command.
#knock#notifications#email#push#sms#workflow#transactional

Source citations

Add this badge to your README

Show that Knock MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/knock-mcp-server.svg)](https://heyclau.de/entry/mcp/knock-mcp-server)

How it compares

Knock MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldKnock MCP Server for Claude

Manage your Knock notification infrastructure from Claude — create and edit workflows, channels, templates, and email layouts, manage users and tenants, commit changes across environments, and debug message logs — with the official Knock remote MCP server.

Open dossier 		Courier MCP Server for Claude

Manage Courier notifications from Claude — send messages and templates, manage user profiles and preferences, configure notification routing, handle automations and journeys, and manage subscriber lists — with the official Courier remote MCP server.

Open dossier 		Fly.io MCP Server for Claude

Manage Fly.io applications, machines, volumes, secrets, certificates, and organizations from Claude — with the official Fly.io MCP server built into the flyctl CLI.

Open dossier 		Postmark MCP Server for Claude

Connect Claude to Postmark — send transactional email, manage templates, search messages, and diagnose delivery, bounces, and suppressions — with the official ActiveCampaign Postmark MCP server.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorKnockCourierFly.ioActiveCampaign
Added2026-06-182026-06-182026-06-182026-06-17
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓The server is hosted by Knock on Cloudflare Workers and authenticated via OAuth 2.1 + PKCE — no API keys required, but write access to your Knock environment is granted after login. Knock's MCP server has no deletion tools by design, reducing destructive-action risk; all changes are staged and require explicit commit/promote steps. Committing and promoting changes across environments is irreversible — review diffs before asking Claude to promote to production.✓The server is hosted by Courier and authenticated via API key — it can send real notifications to real users and modify account data. With 109 tools covering sends, user data, and automations, the blast radius is significant — scope your API key to the minimum required permissions and test in a Courier sandbox environment first. Bulk operations and automation invocations are available — review Claude's proposed actions before executing in production.✓The Fly.io MCP server runs locally with full access to your authenticated Fly.io account — it can create, delete, and modify apps, machines, and secrets. Fly.io warns that running the server remotely can give others access to run commands on your behalf; keep it bound to localhost unless you intend remote access. Destructive operations (machine deletion, secret updates) are available — review Claude's proposed commands before executing in production environments.✓Send tools dispatch real transactional email; restrict the server token and confirm recipients before sending through Claude. Template, webhook, and suppression tools change live Postmark configuration; review before running them.
Privacy notes✓Requests include your notification workflow definitions, template content, user/tenant identifiers, and message logs — all processed by Knock's servers. Knock's OAuth flow stores session credentials securely; avoid sharing MCP session tokens.✓User profile data, notification content, recipient identifiers, and audience lists are sent to Courier's servers when executing tools. Courier API keys are secrets — store them in your environment or MCP client config headers, never in repositories.✓App names, machine IDs, secret names (not values unless explicitly requested), and log content may be surfaced into Claude's context. Fly.io API tokens (`FLY_ACCESS_TOKEN`) grant full account access — store them in your environment, not in repositories.✓Email content, recipient addresses, message search results, and delivery stats enter the MCP client context and the model's prompt. The POSTMARK_SERVER_TOKEN is a secret — keep it in the client config or environment, never in shared repositories.
Prerequisites
  • A Knock account — authenticate via OAuth when prompted on first tool use.
  • Node.js 18+ for `mcp-remote` (Claude Desktop); Claude Code supports `--transport http` natively.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Courier account and an API key from app.courier.com/settings/api-keys.
  • An MCP client such as Claude Code or Claude Desktop.
  • flyctl installed — see fly.io/docs/flyctl/install/ (Homebrew: `brew install flyctl`)
  • Logged in to Fly.io: `fly auth login`
  • Or set `FLY_ACCESS_TOKEN` environment variable for headless/CI use.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Postmark account and a server API token (POSTMARK_SERVER_TOKEN).
  • A verified sender signature/email (DEFAULT_SENDER_EMAIL) and a message stream (DEFAULT_MESSAGE_STREAM).
  • Node.js to clone and run the server.
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add --transport http knock https://mcp.knock.app/mcp
claude mcp add Courier --transport http --header "api_key: YOUR_COURIER_API_KEY" https://mcp.courier.com
fly mcp server --claude
git clone https://github.com/ActiveCampaign/postmark-mcp && cd postmark-mcp && npm install
Config
{
  "mcpServers": {
    "knock": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.knock.app/mcp"]
    }
  }
}
{
  "mcpServers": {
    "courier": {
      "type": "http",
      "url": "https://mcp.courier.com",
      "headers": {
        "api_key": "YOUR_COURIER_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "fly": {
      "command": "fly",
      "args": ["mcp", "server"]
    }
  }
}
{
  "mcpServers": {
    "postmark": {
      "command": "node",
      "args": ["path/to/postmark-mcp/index.js"],
      "env": {
        "POSTMARK_SERVER_TOKEN": "<your-server-token>",
        "DEFAULT_SENDER_EMAIL": "<your-sender@example.com>",
        "DEFAULT_MESSAGE_STREAM": "outbound"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.