How to integrate Ntfy MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Ntfy logo
OpenCode logo
divider

How to integrate Ntfy MCP with OpenCode

This guide explains how to connect Ntfy MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Ntfy with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Ntfy with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Ntfy

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Ntfy Composio".
  3. Complete the authentication and authorization flow, and your Ntfy integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Ntfy to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Ntfy with OpenCode

Now, in the chat, ask the agent to connect to Ntfy or give it any Ntfy-related task.

For example, ask it to:

  • "Send push notification for build failures"
  • "Notify me of high-priority alerts"
  • "Broadcast message to all devices"

It will prompt you to authenticate and authorize access to Ntfy.

That is it. Composio tools are now available in OpenCode, and your Ntfy account is ready to use.

Supported Tools & Triggers

Tools
Create NTFY AccountTool to register a new user account on ntfy.
Create Web Push SubscriptionTool to register a web push subscription for browser notifications.
Delete Web Push SubscriptionTool to unregister a web push subscription from the ntfy server.
Fetch Cached MessagesTool to fetch cached messages from a ntfy topic.
Fetch Latest Message from TopicTool to fetch the most recent message from a topic's cache.
Fetch Scheduled MessagesTool to fetch messages scheduled for later delivery from a topic.
Get Account InformationTool to retrieve account data for authenticated user or anonymous user.
Get Server StatisticsTool to retrieve server statistics including message counts and publishing rates.
Get Service TiersTool to list all available ntfy service tiers with their limits and features.
Get File Attachment MetadataTool to get file attachment metadata from a message without downloading the file content.
Check NTFY Service HealthTool to check the health status of the ntfy service.
Poll Messages from TopicTool to poll for messages from an ntfy topic without maintaining a long-standing connection.
Publish Message as JSON to NTFYTool to publish messages as JSON to ntfy.
Publish Message to TopicTool to publish a message to a ntfy topic.
Publish Message to Topic (PUT)Tool to publish a message to a topic using PUT method.
Publish Message via GETTool to publish messages to ntfy via GET request with URL parameters.
Send Message via WebhookTool to send messages via webhook endpoint using simple GET request.
Subscribe to NTFY Topic with FiltersTool to subscribe to a ntfy topic with filters based on message fields (id, message, title, priority, tags).
Subscribe to Topic (JSON Stream)Tool to subscribe to a ntfy topic and receive messages as JSON stream.
Subscribe to Multiple NTFY TopicsTool to subscribe to multiple ntfy topics simultaneously using comma-separated topic list.
Subscribe to Topic (Raw Stream)Tool to subscribe to a topic and receive message bodies as raw text stream.
Trigger NTFY WebhookTool to trigger a webhook to publish a message to an ntfy topic via simple HTTP GET request.

Way Forward

Now that Ntfy is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Ntfy MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Ntfy MCP?

With a standalone Ntfy MCP server, the agents and LLMs can only access a fixed set of Ntfy tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ntfy and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with OpenCode?

Yes, you can. OpenCode fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Ntfy tools.

Can I manage the permissions and scopes for Ntfy while using Tool Router?

Yes, absolutely. You can configure which Ntfy scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Ntfy data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.