Ship your notification layer from a prompt.
Connect Notiflows to Claude, Cursor, or any agent over MCP. Build notiflows, write templates, publish, and trigger sends — just by asking. Plus a CLI, an agent toolkit, and skills, all on your own model and keys.
One server. Works with every MCP client your team already uses.
Up and running in one command
The Notiflows MCP server is hosted. Point your editor at it, and your assistant can manage notifications in seconds.
Add the server
One command in Claude Code, or a small JSON snippet for Cursor and Claude Desktop.
Discover the tools
Your assistant instantly sees all 17 Notiflows tools, authenticated with your account token.
Just ask
Describe the outcome. The agent builds the notiflow, publishes it, and sends it for you.
$ claude mcp add notiflows -- \
npx -y mcp-remote \
https://api.notiflows.com/mcp \
--header "Authorization: Bearer nf_at_…"
✓ notiflows connected · 17 tools availableWorks with Claude Code, Cursor, Claude Desktop, Windsurf, VS Code, and any MCP client.
17 tools. Everything an agent needs to run notifications.
Every tool is backed by a real Notiflows API endpoint. No destructive deletes, and channels stay read-only, so it’s safe to hand to an agent from day one.
Notiflows
The full lifecycle, from draft to live.
list_notiflowsList notiflows in a project.get_notiflowFetch a notiflow and its steps.upsert_notiflowCreate or update a draft.validate_notiflowValidate the current draft.publish_notiflowPublish so it goes live.activate_notiflowToggle whether it can trigger.rollback_notiflowRevert to the published version.run_notiflowTrigger a run for recipients.
Templates
Author the message on any channel step.
get_templateRead a channel step template.upsert_templateCreate or update a template.
Versions
Walk the copy-on-write history.
list_versionsList version history.get_versionFetch a version with steps.
Channels
Read-only — agents never reconfigure delivery.
list_channelsList the delivery channels.get_channelFetch a channel by handle.
Identity
Know which account and projects you can reach.
whoamiVerify the token and account.list_projectsList accessible projects.
Docs
Ground answers in the real documentation.
search_docsSearch the Notiflows docs.
MCP is just the start
Prefer the terminal, your own runtime, or teaching your assistant directly? Every path to Notiflows is first-class.
Build from the terminal
Create, validate, and trigger notiflows from the command line. Pull them down as JSON, version them in git, push them back. Your whole notification layer, in code.
Agent toolkitTools for your own agents
Turn published notiflows into typed tools for the Vercel AI SDK, OpenAI, or LangChain: a trigger tool per notiflow, a generic trigger, and requireHumanInput for approvals.
SkillsTeach your assistant Notiflows
Installable agent skills give your coding assistant deep, current Notiflows know-how, so it scaffolds and edits notiflows correctly the first time.
Safe to put in front of an agent
The AI is yours. Notiflows just gives it typed, scoped, auditable access to your notifications — nothing runs on our keys, and nothing happens you can’t see.
Your model, your keys
Notiflows never calls an LLM for you
Every surface runs on your AI and your tokens. No hidden inference costs, no model lock-in, no surprise bill.
Scoped by design
Expose only what you choose
Your account token authorizes calls server-side and is never handed to the model. Show only the projects and published notiflows you want.
Schema-safe
Typed inputs, validated before send
Every tool advertises a JSON schema. Recipients, topics, and data are checked first, so an agent can’t fire a malformed notification.
Fully auditable
Same API as everything else
Every trigger lands in the dashboard, attributed and reviewable. Nothing an agent does happens off the record.
Bring your own agent.
Wire Notiflows into your AI stack in minutes, on your model and your keys.
Free tier includes 10,000 deliveries/month. No credit card required.