by yuki-yano
Get native macOS notifications with tmux integration. Instantly navigate to sessions, windows, and panes with seamless t
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.
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.
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.
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.
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
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
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
Share your MCP server with the developer community
According to our notes, macOS Notifications with tmux benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We evaluated macOS Notifications with tmux against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: macOS Notifications with tmux surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired macOS Notifications with tmux into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: macOS Notifications with tmux is the kind of server we cite when onboarding engineers to host + tool permissions.
macOS Notifications with tmux reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
macOS Notifications with tmux is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
According to our notes, macOS Notifications with tmux benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
macOS Notifications with tmux is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated macOS Notifications with tmux against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 26
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.
npm install -g macos-notify-mcp
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)
First, install the package globally:
npm install -g macos-notify-mcp
Use the claude mcp add command:
claude mcp add macos-notify -s user -- macos-notify-mcp
Then restart Claude Code.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"macos-notify": {
"command": "macos-notify-mcp"
}
}
}
send_notification - Send a macOS notification
message (required): Notification messagetitle: Notification title (default: "Claude Code")sound: Notification sound (default: "Glass")session: tmux session namewindow: tmux window numberpane: tmux pane numberuseCurrent: Use current tmux locationlist_tmux_sessions - List available tmux sessions
get_current_tmux_info - Get current tmux session information
# 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
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
The tool detects terminals using various methods:
CURSOR_TRACE_ID environment variableVSCODE_IPC_HOOK_CLI or VSCODE_REMOTE environment variablesALACRITTY_WINDOW_ID or ALACRITTY_SOCKET environment variablesTERM_PROGRAM=iTerm.appTERM_PROGRAM=Apple_TerminalWhen running inside tmux, the tool attempts to detect which terminal emulator the active tmux client is using:
For advanced tmux client tracking, see examples/tmux-client-tracking.sh.
The project consists of two main components:
MCP Server/CLI (TypeScript/Node.js)
MacOSNotifyMCP.app (Swift/macOS)
The MacOSNotifyMCP.app is bundled with the npm package and is automatically available after installation. No additional setup is required.
macos-notify-mcp -m "test" to verifymacos-notify-mcp --list-sessions# 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
MIT
Yuki Yano
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ 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.