Skip to main content
Glama
toolprint

MCPing

by toolprint
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

MCPing - macOS Notification MCP Server

License: MIT npm version Node.js Version

I got a notification! 🎉

MCPing is a Model Context Protocol (MCP) server that enables AI assistants to send desktop notifications on macOS. Finally, your AI can tap you on the shoulder instead of just sitting there quietly being brilliant.

Installation

Prerequisites: Node.js 18+ and macOS (for notifications)

Quick Start (Recommended)

Add to your MCP client settings:

{
  "mcpServers": {
    "toolprint-mcping": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@toolprint/mcping-mcp@latest"]
    }
  }
}

Manual Installation

npm install -g @toolprint/mcping-mcp@latest
mcping-mcp

Related MCP server: Notifications MCP Server

Configuration

For Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "mcping": {
      "command": "npx",
      "args": ["-y", "@toolprint/mcping-mcp@latest"]
    }
  }
}

For Development (HTTP Mode)

# Run in HTTP mode for testing
npx @toolprint/mcping-mcp@latest --transport http --port 3000

# Test with curl
curl -X POST http://localhost:3000/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "send-notification",
      "arguments": {
        "title": "Hello World",
        "message": "This is a test notification"
      }
    }
  }'

Usage

Once configured, ask your AI assistant:

  • "Send a notification saying the build is complete"

  • "Send a critical alert that the server is down"

  • "Send a quiet reminder to take a break"

  • "Notify me with title 'Tests Passed' and message 'All 127 tests passed'"

Tool: send-notification

Send desktop notifications on macOS with rich formatting options.

Parameters:

  • title (required): Notification title (1-100 characters)

  • message (required): Notification message (1-500 characters)

  • subtitle (optional): Additional context (max 100 characters)

  • urgency (optional): "low" | "normal" | "critical" (default: "normal")

  • sound (optional): Play notification sound (default: true)

  • timeout (optional): Display duration in seconds, 1-60 (default: 10)

Examples:

// Basic notification
{
  "title": "Task Complete",
  "message": "Your build finished successfully"
}

// Critical alert with subtitle
{
  "title": "Server Down",
  "message": "Production server is not responding",
  "subtitle": "api.example.com",
  "urgency": "critical",
  "sound": true,
  "timeout": 60
}

// Quiet reminder
{
  "title": "Break Time",
  "message": "You've been coding for 2 hours",
  "urgency": "low",
  "sound": false,
  "timeout": 10
}

Troubleshooting

Notifications Not Appearing?

  1. Check Permissions: System Preferences → Notifications → Terminal (allow notifications)

  2. Do Not Disturb: Ensure DND is disabled or use urgency: "critical"

  3. Verbose Mode: Run with --verbose flag for detailed logs

Common Issues

  • "Permission denied": Grant Terminal notification permissions in System Preferences

  • "Not available": Ensure you're running on macOS

  • "Rate limited": Wait between sending multiple notifications

Development

# Clone repository
git clone https://github.com/toolprint/mcping-mcp.git
cd mcping-mcp

# Install dependencies
npm install

# Run tests
npm test

# Build
npm run build

# Development mode
npm run dev

License

MIT © Toolprint

Usage

When using, forking, or distributing this software, the MIT License requires that you include the original copyright notice ("Copyright © OneGrep, Inc.") and license text in all copies or substantial portions of the software. This attribution requirement ensures proper credit to the original authors while allowing you to freely use, modify, and distribute the code.

About Toolprint

Building tools for the AI agent ecosystem. Visit toolprint.ai to explore our suite of MCP servers and developer tools.

Available Tools

1 tool
send-notificationB

Send a desktop notification on macOS with icon, image, and sound customization

ParametersJSON Schema
NameRequiredDescriptionDefault
titleYesThe notification title
messageYesThe notification message body
subtitleNoOptional subtitle text displayed below the title
urgencyNoNotification urgency levelnormal
soundNoSound setting: boolean, built-in sound name, or path to custom sound
timeoutNoNotification timeout in seconds (1-60)
iconNoAbsolute path to notification icon image
contentImageNoAbsolute path to image to attach to notification
openNoURL to open when notification is clicked

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only mentions sending a notification with customization but does not disclose behavioral traits such as blocking behavior, permission requirements, error handling, or side effects beyond the action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the action. It is appropriately sized but could include a bit more context without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 9 parameters and no output schema, the description is too brief. It does not explain the return value, error conditions, or behavioral aspects, leaving the agent with incomplete understanding for a mutation tool with many options.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description mentions icon, image, and sound customization, which is already evident from the schema. It does not add significant meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool sends a desktop notification on macOS with customization options. It specifies a specific verb and resource, and while there are no sibling tools to differentiate, the description is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. There is no explicit context for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.0.4
    • First observedsend-notification
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

Only one tool exists, so there is no risk of confusion with other tools.

Naming Consistency5/5

With a single tool, naming consistency is inherently maintained; the verb_noun pattern is clear.

Tool Count3/5

A single tool is minimal but acceptable for a focused notification server; however, it feels thin for broader use.

Completeness3/5

The tool covers sending notifications with customization, but lacks operations like cancellation or listing, leaving minor gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP Notifications Server

    konstzv
    F
    license
    B
    quality
    D
    maintenance
    Enables Claude and other MCP clients to display native macOS notifications with customizable titles, messages, icons, and sounds through the macOS Notification Center.
    1
    16
    -

  • Notifications MCP Server

    ohqay
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to send native macOS notifications for task completion alerts and reminders. Supports interactive features like custom system sounds, action buttons, and user replies directly from the notification center.
    201
    MIT

  • BotBell MCP Server

    qq418716640
    A
    license
    A
    quality
    C
    maintenance
    Enables AI assistants to send push notifications and interactive alerts to iPhone and Mac devices via the BotBell app. It allows AI to receive user replies and manage notification bots for tasks like alerts, reminders, and remote approvals.
    2
    19
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/toolprint/mcping-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server