Your inbox, managed in conversation.
Knock speaks MCP — the open standard for connecting AI assistants to tools. Connect your assistant once, and from then on you can triage who's knocking, release or claim deposits, set your prices, and configure allow and block rules just by talking. No dashboard required.
Last updated July 2026
Your connection address
Every setup path below ends with pasting this server URL into your assistant, then signing in with your Knock account.
Knock MCP server URL
https://knock.email/mcpConnect your assistant
- 1In Claude’s connector settings, add Knock as a custom connector using the server URL above. The prefilled connector link fills in the name and URL for you; Anthropic’s custom connector documentation covers the current menu locations.
- 2Authorize with your Knock login when Claude opens the sign-in window.
- 3Enable the connector from the chat composer, then try a recipe below.
- 4Using Claude Code instead? Run
claude mcp add --scope user --transport http knock-attention-protocol 'https://knock.email/mcp'in a terminal, then/mcpto sign in.
Claude can also run the multi-connector recipes below if you have Google’s Gmail connector enabled alongside Knock — that’s what makes the allowlist harvest possible.
Recipes
Copy any of these into your assistant once Knock is connected. Everything here maps to a tool Knock actually exposes.
The morning knock
“Check my Knock queue — anything worth my attention? Summarize by signal and deposit.”
Your assistant reads the queue highest-deposit-first, including who paid, what category each message is, and which newsletter lists are still awaiting a decision.
Settle in a sentence
“Release the founder's deposit, claim the two sales pitches, and let the unpaid one from my accountant through.”
Release refunds the sender in full and vouches for them; claim keeps the deposit; let through delivers an unpaid message for free and allowlists that sender. Release and claim move real money.
The bouncer
“Block everything from that recruiting agency's domain, and allow anyone from intercoast.edu.”
Adds allow and block rules by email address or whole domain, so trusted senders skip the deposit entirely and known noise never reaches your queue.
Pricing concierge
“What am I charging per category? Raise sales to $10.”
Reads back your alias, per-category deposit prices, and current rules, then updates any category's price in place.
Guided inbox protection
“Help me protect my Gmail with Knock.”
The assistant checks your protection status, walks you through the two forwarding clicks at mail.google.com, and announces Google's verification code the moment Knock catches it. Later it flips monitor → protect once you've both reviewed the would-have-challenged summary.
The allowlist harvest
Claude + Gmail connector“Look through my Gmail for people I've actually corresponded with in the last 6 months and allow them all in Knock.”
With Google's Gmail connector enabled alongside Knock, the assistant pulls your real correspondents and writes them straight into your allowlist. This is the best way to pre-seed trust before flipping an alias from monitor to protect.
Security & trust
- The connection uses OAuth, scoped to your account only. Your assistant signs in as you — it never sees another user's queue.
- Money-moving actions run under exactly the same server-side rules as the dashboard: paid deposits can only be released or claimed once, and unpaid mail can only be let through, never claimed.
- You can revoke access at any time from your assistant's connector settings; the tools stop working immediately.
- We recommend telling your assistant to confirm with you before claiming a deposit. Claims and releases are real money and can't be undone.
Where to next
This page is for recipients answering the door; if you’re building an agent that knocks, see the API docs.
New to the protocol? Start with how Knock works or protecting the inbox you already use.