productivitydeveloper-tools

macOS Notifications with tmux

yuki-yano

by yuki-yano

Get native macOS notifications with tmux integration. Instantly navigate to sessions, windows, and panes with seamless t

Provides native macOS notifications with intelligent tmux session integration that automatically detects terminal environments and enables click-to-navigate functionality for returning to specific tmux sessions, windows, and panes.

github stars

13

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

Click notifications to jump to exact tmux locationWorks across multiple terminal emulatorsNo API key needed

best for

  • / Developers working in tmux terminal sessions
  • / Getting notified about long-running tasks in specific terminal panes
  • / AI assistants providing contextual terminal navigation

capabilities

  • / Send native macOS notifications with custom titles and sounds
  • / Navigate to specific tmux sessions via clickable notifications
  • / List active tmux sessions and panes
  • / Auto-detect terminal emulators (VSCode, iTerm2, Terminal)
  • / Focus tmux windows and panes with one click

what it does

Sends native macOS notifications from AI assistants with smart tmux integration that lets you click notifications to jump directly to specific terminal sessions, windows, and panes.

about

macOS Notifications with tmux is a community-built MCP server published by yuki-yano that provides AI assistants with tools and capabilities via the Model Context Protocol. Get native macOS notifications with tmux integration. Instantly navigate to sessions, windows, and panes with seamless t It is categorized under productivity, developer tools.

how to install

You can install macOS Notifications with tmux in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

MIT

macOS Notifications with tmux is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

macOS Notify MCP

A Model Context Protocol (MCP) server for macOS notifications with tmux integration. This tool allows AI assistants like Claude to send native macOS notifications that can focus specific tmux sessions when clicked.

Features

  • 🔔 Native macOS notifications using UserNotifications API
  • 🖱️ Clickable notifications that focus tmux sessions
  • 🎯 Direct navigation to specific tmux session, window, and pane
  • 🔊 Customizable notification sounds
  • 🚀 Support for multiple concurrent notifications
  • 🤖 MCP server for AI assistant integration
  • 🖥️ Terminal emulator detection (VSCode, Cursor, iTerm2, Terminal.app)

Installation

Prerequisites

  • macOS (required for notifications)
  • Node.js >= 18.0.0
  • tmux (optional, for tmux integration)

Install from npm

npm install -g macos-notify-mcp

Build from source

git clone https://github.com/yuki-yano/macos-notify-mcp.git
cd macos-notify-mcp
npm install
npm run build
npm run build-app  # Build the macOS app bundle (only needed for development)

Usage

As MCP Server

First, install the package globally:

npm install -g macos-notify-mcp

Quick Setup with Claude Code

Use the claude mcp add command:

claude mcp add macos-notify -s user -- macos-notify-mcp

Then restart Claude Code.

Manual Setup for Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "macos-notify": {
      "command": "macos-notify-mcp"
    }
  }
}

Available MCP Tools

  • send_notification - Send a macOS notification

    • message (required): Notification message
    • title: Notification title (default: "Claude Code")
    • sound: Notification sound (default: "Glass")
    • session: tmux session name
    • window: tmux window number
    • pane: tmux pane number
    • useCurrent: Use current tmux location
  • list_tmux_sessions - List available tmux sessions

  • get_current_tmux_info - Get current tmux session information

As CLI Tool

# Basic notification
macos-notify-cli -m "Build completed"

# With title
macos-notify-cli -t "Development" -m "Tests passed"

# With tmux integration
macos-notify-cli -m "Task finished" -s my-session -w 1 -p 0

# Use current tmux location
macos-notify-cli -m "Check this pane" --current-tmux

# Detect current terminal emulator
macos-notify-cli --detect-terminal

# List tmux sessions
macos-notify-cli --list-sessions

Terminal Detection

The tool automatically detects which terminal emulator you're using and uses this information when you click on notifications to focus the correct application. You can test terminal detection with:

# Test terminal detection
macos-notify-cli --detect-terminal

Supported Terminal Detection

The tool detects terminals using various methods:

  1. Cursor: Via CURSOR_TRACE_ID environment variable
  2. VSCode: Via VSCODE_IPC_HOOK_CLI or VSCODE_REMOTE environment variables
  3. alacritty: Via ALACRITTY_WINDOW_ID or ALACRITTY_SOCKET environment variables
  4. iTerm2: Via TERM_PROGRAM=iTerm.app
  5. Terminal.app: Via TERM_PROGRAM=Apple_Terminal

Terminal Detection in tmux

When running inside tmux, the tool attempts to detect which terminal emulator the active tmux client is using:

  1. Active Client Detection: Identifies the most recently active tmux client
  2. TTY Process Analysis: Traces processes using the client's TTY
  3. Environment Preservation: Checks preserved environment variables
  4. Process Tree Fallback: Analyzes the process tree as a last resort

For advanced tmux client tracking, see examples/tmux-client-tracking.sh.

How it Works

  1. Notification Delivery: Uses a native macOS app bundle (MacOSNotifyMCP.app) to send UserNotifications API notifications
  2. Click Handling: When a notification is clicked, the app activates the detected terminal emulator (VSCode, Cursor, iTerm2, alacritty, or Terminal.app) and switches to the specified tmux session
  3. Terminal Support: Automatically detects and activates the correct terminal application
  4. Multiple Instances: Each notification runs as a separate process, allowing multiple concurrent notifications

Architecture

The project consists of two main components:

  1. MCP Server/CLI (TypeScript/Node.js)

    • Implements the Model Context Protocol
    • Provides a command-line interface
    • Manages tmux session detection and validation
  2. MacOSNotifyMCP.app (Swift/macOS)

    • Native macOS application for notifications
    • Handles notification clicks to focus tmux sessions
    • Runs as a background process for each notification

MacOSNotifyMCP.app

The MacOSNotifyMCP.app is bundled with the npm package and is automatically available after installation. No additional setup is required.

Troubleshooting

Notifications not appearing

  1. Check System Settings → Notifications → MacOSNotifyMCP
  2. Ensure notifications are allowed
  3. Run macos-notify-mcp -m "test" to verify

tmux integration not working

  1. Ensure tmux is installed and running
  2. Check session names with macos-notify-mcp --list-sessions
  3. Verify terminal app is supported (Alacritty, iTerm2, WezTerm, or Terminal)

Development

# Install dependencies
npm install

# Build TypeScript
npm run build

# Run in development
npm run dev

# Lint and format code
npm run lint
npm run format

# Build macOS app (only if modifying Swift code)
npm run build-app

License

MIT

Author

Yuki Yano

FAQ

What is the macOS Notifications with tmux MCP server?
macOS Notifications with tmux is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for macOS Notifications with tmux?
This profile displays 26 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.526 reviews
  • Mateo Harris· Dec 28, 2024

    According to our notes, macOS Notifications with tmux benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Shikha Mishra· Dec 16, 2024

    We evaluated macOS Notifications with tmux against two servers with overlapping tools; this profile had the clearer scope statement.

  • Ganesh Mohane· Dec 12, 2024

    Strong directory entry: macOS Notifications with tmux surfaces stars and publisher context so we could sanity-check maintenance before adopting.

  • Amelia Nasser· Nov 19, 2024

    We wired macOS Notifications with tmux into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Yash Thakker· Nov 7, 2024

    Useful MCP listing: macOS Notifications with tmux is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Dhruvi Jain· Oct 26, 2024

    macOS Notifications with tmux reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Ren Jain· Oct 10, 2024

    macOS Notifications with tmux is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Diego Huang· Sep 17, 2024

    According to our notes, macOS Notifications with tmux benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Ishan Haddad· Sep 1, 2024

    macOS Notifications with tmux is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Ishan Sharma· Aug 20, 2024

    We evaluated macOS Notifications with tmux against two servers with overlapping tools; this profile had the clearer scope statement.

showing 1-10 of 26

1 / 3