# How to connect Ntfy to OpenClaw (paste one key, 12 tools) > Connect Ntfy to OpenClaw with ClawLink: paste your Ntfy key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ntfy The usual route to Ntfy access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Ntfy setup: install one ClawHub skill, connect Ntfy in the browser, and OpenClaw can call real Ntfy actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Ntfy. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Ntfy** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect ntfy # connect Ntfy (browser OAuth) npx -y @useclawlink/cli actions ntfy # list available actions npx -y @useclawlink/cli run ntfy --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Ntfy in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ntfy API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Ntfy, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Ntfy is connected in the dashboard, that agent calls the same 12 Ntfy tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Ntfy MCP for OpenClaw Looking for a Ntfy MCP server for OpenClaw? ClawLink connects Ntfy to OpenClaw and exposes 12 Ntfy tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Ntfy integration](https://claw-link.dev/hermes/ntfy) works the same way. ## What the OpenClaw Ntfy integration can do 12 Ntfy tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 12. ### 11 of 12 Ntfy tools for OpenClaw | Tool | What it does | |---|---| | **Fetch scheduled messages** `ntfy_fetch_scheduled_messages` | Fetch messages scheduled for later delivery from a topic | | **Get account** `ntfy_get_account` | Retrieve account data for authenticated user or anonymous user | | **Get stats** `ntfy_get_stats` | Retrieve server statistics including message counts and publishing rates | | **Get tiers** `ntfy_get_tiers` | List all available ntfy service tiers with their limits and features | | **Head file** `ntfy_head_file` | Get file attachment metadata from a message without downloading the file content | | **Health check** `ntfy_health_check` | Check the health status of the ntfy service | | **Subscribe raw stream** `ntfy_subscribe_raw_stream` | Subscribe to a topic and receive message bodies as raw text stream | | **Create account** `ntfy_create_account` | Register a new user account on ntfy | | **Create webpush subscription** `ntfy_create_webpush_subscription` | Register a web push subscription for browser notifications | | **Publish message** `ntfy_publish_message` | Publish a message to a ntfy topic | | **Publish via get** `ntfy_publish_via_get` | Publish messages to ntfy via GET request with URL parameters | ## Example prompts **Fetch Scheduled Messages** > Pull the relevant data from Ntfy, summarize it in plain English, and point out anything that needs attention. **Get Account** > Pull the relevant data from Ntfy, summarize it in plain English, and point out anything that needs attention. **Get Stats** > Pull the relevant data from Ntfy, summarize it in plain English, and point out anything that needs attention. **Get Tiers** > Pull the relevant data from Ntfy, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Ntfy working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Ntfy API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ntfy account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Ntfy. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Ntfy actions to the runtime in a format your agent can reliably use. | 12 tools for Ntfy are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Ntfy to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Ntfy in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Ntfy key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Ntfy skill but can't call the tools The ClawHub skill teaches OpenClaw about Ntfy, but the calls run through the ClawLink plugin and your connected account. Make sure Ntfy is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Ntfy from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Ntfy tools Ntfy tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Ntfy call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Ntfy returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Ntfy has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Ntfy integration? Yes. ClawLink is the fastest way to connect OpenClaw to Ntfy: link your Ntfy account once in the browser and OpenClaw can call the Ntfy API through 12 ready-made tools — no custom code or token handling. ### How do I add Ntfy to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ntfy skill from ClawHub, then you click Connect in the dashboard to authorize Ntfy. OpenClaw calls the tools from the next message — no config files, and the Ntfy key you paste is stored server-side instead of in your environment. ### How long does it take to connect Ntfy to OpenClaw? About two minutes. Sign in, click Connect next to Ntfy in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Ntfy up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Ntfy working from chat. ### OpenClaw installed the Ntfy skill but can't call the tools The ClawHub skill teaches OpenClaw about Ntfy, but the calls run through the ClawLink plugin and your connected account. Make sure Ntfy is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.