Barkme MCP Server
Enables sending iOS push notifications through the Bark service directly from Claude conversations. Supports device aliases, all Bark API parameters, and async delivery.
README
Barkme MCP Server
A Model Context Protocol (MCP) server that provides iOS push notifications through the Bark service. Send notifications directly from Claude conversations with a simple, intelligent interface.
Features
- Single Tool Interface: One
notifytool handles all notification scenarios - Device Aliases: Use friendly configurable aliases like "iPhone:key1", "macOS:key2" instead of exposing device keys to AI
- Async-First: Non-blocking notifications with background delivery and structured logging
- Complete Bark API Support: All 20+ parameters including encrypted messages and notification management
- Update/Delete Notifications: Modify or remove previously sent notifications using notification IDs
Quick Start
Prerequisites
- Node.js 20+
- A Bark device key from the iOS app (setup tutorial)
- A MCP Client like Claude Desktop or Claude Code
via npmjs
Claude Desktop Integration
Add to your Claude Desktop configuration file:
- macOS/Linux:
~/.config/claude-desktop/claude_desktop_config.json - Windows:
%AppData%\Claude\claude_desktop_config.json
{
"mcpServers": {
"barkme": {
"command": "npx",
"args": ["@vibeworks/barkme-mcp-server"],
"env": {
"LOG_LEVEL": "info",
"BARK_DEVICES": "iPhone:<your key>",
"BARK_SERVER": "https://api.day.app",
"BARK_GROUP": "Claude",
"BARK_RETRY": "2",
"BARK_ASYNC": "true"
}
}
}
}
Restart Claude Desktop after adding the configuration. The Barkme server will appear in the MCP tools section.
via Smithery
To install barkme-mcp-server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @vibeworks/barkme-mcp-server --client claude
From source
git clone https://github.com/thevibeworks/barkme-mcp-server
cd barkme-mcp-server
npm install
npm run build
{
"mcpServers": {
"barkme": {
"command": "node",
"args": ["/absolute/path/to/barkme-mcp-server/dist/index.js"],
"env": {
...
}
}
}
}
Usage Examples
Ask Claude:
- "Send me a notification saying 'Hello World'"
- "Send a notification to my iPhone and iPad saying 'Meeting in 10 minutes'"
- "Send a critical alert about server maintenance"
- "Update the notification with ID 'deploy-123' to say 'Deployment completed'"
Tool Reference
notify
Send push notifications to iOS devices via Bark service.
Key Parameters:
| Parameter | Type | Description |
|---|---|---|
message |
string | Main notification text |
title |
string | Bold title above message |
level |
enum | Urgency: passive, active, timeSensitive, critical |
targets |
array | Device aliases (e.g., ["iPhone", "iPad"]) |
icon |
URL | Custom icon image |
url |
URL | Link to open when tapped |
id |
string | For updating/deleting notifications |
delete |
boolean | Delete notification (requires id) |
Response Format:
Sending notification - queued for background delivery
To: `iPhone`, `iPad`
Level: timeSensitive
Delivery status will be logged to console:
2025-07-29T15:26:17.123Z [INFO] Notification delivered to iPhone in 0.234s
2025-07-29T15:26:17.145Z [INFO] Notification delivered to iPad in 0.267s
Environment Variables
| Variable | Default | Description |
|---|---|---|
BARK_DEVICES |
- | Required: Device keys: key1,key2 or aliases: iPhone:key1,iPad:key2 |
BARK_DEFAULT_DEVICE |
First device | Default device alias for fallback |
BARK_SERVER |
https://api.day.app |
Bark server URL |
BARK_GROUP |
Bark MCP Server |
Default notification group |
BARK_SOUND |
- | Default notification sound |
BARK_ICON |
- | Default icon URL |
BARK_LEVEL |
- | Default urgency level |
BARK_VOLUME |
- | Default volume (0-10) |
BARK_RETRY |
1 |
Retry count on failure (0-10) |
BARK_ASYNC |
true |
Async mode: true (fire-and-forget) or false (blocking) |
LOG_LEVEL |
info |
Logging level: debug, info, warn, error |
Development
Project Structure
barkme-mcp-server/
├── src/
│ ├── index.ts # Main MCP server implementation
│ └── logger.ts # Simple structured logging
├── dist/
│ ├── index.js # Compiled executable
│ ├── logger.js # Compiled logger
│ └── *.d.ts # Type definitions
├── references/ # Reference materials
├── package.json # Project configuration
├── tsconfig.json # TypeScript configuration
├── CLAUDE.md # Development guide
└── README.md # This file
Build Commands
npm run build # Compile TypeScript
npm run watch # Watch mode for development
npm start # Run the compiled server
License
MIT
Related Projects
- Bark - The original iOS notification service
- barkme-tools - Original shell script implementation
- Model Context Protocol - The MCP specification
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。