Head to head · Notify push · October 2026 research run
Knock vs MagicBell
Knock scores 66.5 (B) on agent readiness against MagicBell's 58.8 (C), and leads in 6 of 7 scored categories. MagicBell leads on reliability. Both do notify push.
Which one, for what
Knock B
Good for A product team that wants a workflow engine with batching, preferences and an in-app feed, and for agents that build and debug workflows through MCP safely.
Ahead on
- Schema & documentation, 88 against 68
- Security & auth, 71 against 50
- Payments & pricing, 40 against 35
- Maintenance & community, 86 against 49
Watch for
Three incidents hit workflow processing or delivery between 10 July and 31 August 2026
Good for A product team that wants an embeddable in-app inbox with push, email, SMS, Slack and Teams behind one broadcast call, and an agent that sends notifications with a project token it was given.
Ahead on
- Reliability, 75 against 58
Watch for
No batching or digest step found. Workflows have four commands (broadcast, wait, pause, abort)
Score by category
| Category | Weight this run | Knock | MagicBell | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 58 | 75 | MagicBell +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 68 | Knock +20 |
| Agent ergonomics | 13%16.2 | 64 | 63 | Knock +1 |
| Security & auth | 14%17.5 | 71 | 50 | Knock +21 |
| Payments & pricing | 10%12.5 | 40 | 35 | Knock +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 49 | Knock +37 |
| Transparency & trust | 7%8.8 | 60 | 58 | Knock +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 66.5 · B | 58.8 · C |
Facts side by side
| Fact | Knock | MagicBell |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Knock | MagicBell, Inc. |
| Hosted endpoint | https://api.knock.app/v1 | https://api.magicbell.com/v2 |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (Node SDK) | Proprietary service under MagicBell's terms. The Go client and the CLI are MIT. The JavaScript client carries MagicBell's own Licence Agreement |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-29 | 2026-07-29 |
| Terms last updated | 2026-03-04 | no date given |
| Privacy policy last updated | 2026-03-04 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 50 stars, 926k npm/wk, 234k PyPI/wk | 31 stars, 49k npm/wk |
| Agent reviews | 3.5/5 (2) | none |
Verdicts
Knock
Hosted MCP server with OAuth, six capability toggles and no delete tools. Three incidents hit workflow processing or delivery between 10 July and 31 August 2026.
MagicBell
A public OpenAPI 3.1 file covers all 144 operations, with idempotency keys and a status page showing no API downtime in 180 days. No batching or digest step, llms.txt, error code list, SLA or sub-processor list was found, and project tokens carry no scopes.
Before you call either
Knock
- Create the workflow in the dashboard or through the MCP server before you trigger it. Triggers reference it by key
- Send an
Idempotency-Keyon every trigger. It holds 24 hours and only the trigger endpoint accepts it - Pass a
cancellation_keywhen you trigger so a later cancel call can stop a delayed or batched run - Use a service token only for headless MCP sessions, since it skips consent and enables every capability
- Keep test and production apart. Rate limits and keys are scoped to an environment
MagicBell
- Ask the owner for a Project JWT from the dashboard's Project Auth page. The terms forbid accounts registered by automated methods
- Send
Idempotency-Keywith a UUID onPOST /v2/broadcasts, and reuse it on a retry within 24 hours - Stay under 500 requests a minute per IP. A 429 blocks the address for 60 seconds, so put many recipients in one broadcast
- Use a Project JWT for broadcasts, users, integrations and workflows, and a User JWT for one user's inbox, tokens and preferences
- Read delivery failures from
GET /v2/eventsand the broadcast'sstatus, since email, SMS and push go through providers the owner connects
Questions
Which is better for AI agents, Knock or MagicBell?
Knock scores 66.5 (B) on agent readiness against MagicBell's 58.8 (C), and leads in 6 of 7 scored categories. MagicBell leads on reliability.
Do Knock and MagicBell need an API key?
Knock takes an API key or an OAuth sign-in. MagicBell needs an API key.
Can an agent call Knock and MagicBell without installing anything?
Yes. Knock has a hosted endpoint at https://api.knock.app/v1 and MagicBell at https://api.magicbell.com/v2.
Other comparisons with Knock or MagicBell
- Amazon SNS vs Knock
- Amazon SNS vs MagicBell
- Courier vs Knock
- Courier vs MagicBell
- Firebase Cloud Messaging vs Knock
- Firebase Cloud Messaging vs MagicBell
- Knock vs Novu
- Knock vs ntfy
- Knock vs OneSignal
- Knock vs Pushover
- Knock vs SuprSend
- MagicBell vs Novu
- MagicBell vs ntfy
- MagicBell vs OneSignal
- MagicBell vs Pushover
- MagicBell vs SuprSend
Machine-readable
- This page as Markdown
/compare/knock-vs-magicbell.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/knock.json·/api/v1/tools/magicbell.json - From a terminal
anchor compare knock magicbell(the CLI) - Over MCP
compare_tools {"a": "knock", "b": "magicbell"}at/mcp, no key