1. Conduid
  2. Developer Tools
  3. Notification
MCP server · Developer Tools

Notification

by · github.com/angelcervera/mcp-notification

Control and read Android phone notifications via a local MCP server on-device.

Unclaimed last commit 8 months ago comms
InstallView source
50Fair

Scored 2 months ago · breakdown

About Notification

Notification is an MCP server published by angelcervera in the Developer Tools category: control and read Android phone notifications via a local MCP server on-device. It has been installed 0 times through Conduid.

The repository has 1 stars and 0 forks, with the last commit 8 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx mcp-notification

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Notification

Powered by Claude · Grounded in docs

I know everything about Notification. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

mcp-notifications

MCP server (stdio, JSON-RPC) to send local desktop notifications from Codex or other agents.

OS requirements

  • Linux (GNOME/KDE/etc): notify-send on PATH (typically libnotify-bin). If no DISPLAY/WAYLAND is available or notify-send fails, the server falls back to gdbus (from glib2.0-bin) and uses the session bus (DBUS_SESSION_BUS_ADDRESS or /run/user/<uid>/bus).
  • macOS: osascript (preinstalled).
  • Windows: powershell.exe or pwsh on PATH (requires an interactive desktop session for toasts).
  • WSL (optional): if Linux notification paths fail, the server falls back to Windows toasts via powershell.exe.

Build

go build -o mcp-notifications ./cmd/mcp-notifications

Configure in Codex

Add an MCP server entry in ~/.codex/config.toml pointing at the built binary:

[mcp_servers.notifications]
command = "/ABSOLUTE/PATH/TO/mcp-notifications"

If it is available on your PATH (e.g. ~/.local/bin), you can use:

[mcp_servers.notifications]
command = "mcp-notifications"

Exposed tool

  • notify
    • Input: { "title": string, "message": string, "urgency"?: "low"|"normal"|"critical", "timeoutMs"?: number }
    • Notes:
      • urgency and timeoutMs apply only on Linux (via notify-send).

Release

Releases are produced by GitHub Actions via GoReleaser. They build binaries for Linux, macOS, and Windows (amd64 + arm64).

Create a release

git tag v0.1.0
git push origin v0.1.0

Manual trigger

You can also trigger the release workflow manually from the GitHub Actions UI.

README mirrored from the source repository 2 months ago. The original is authoritative.

Questions

About Notification

How do I install Notification?

Run npx mcp-notification, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Notification safe to use with an AI agent?

Its trust score is 50 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Notification still maintained?

The last commit was 8 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.