MCP Server for iOS Bark push notifications - Send notifications to iOS devices via Bark app
If you already use Bark, the bark mcp server is the piece that lets your assistant work with it directly. MCP Server for iOS Bark push notifications - Send notifications to iOS devices via Bark app.
A Model Context Protocol (MCP) server for sending iOS push notifications via Bark.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
send_bark_notification — Send a single push notification to an iOS device. **AI assistants should use this to notify users when tasks complete, errors occur, or input issend_bark_batch_notifications — Send multiple notifications in a single batch operation. Use for notifying multiple team members or sending different priority updates.check_bark_server_health — Check if a Bark server is running and healthy. AI should call this proactively to ensure reliable user communication.Configuration is passed through the environment: BARK_KEY, BARK_SERVER_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Bark's toolset — send_bark_notification, send_bark_batch_notifications, check_bark_server_health — is a fair guide to whether it matches your workflow. It is maintained by metrovoc; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Bark's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| send_bark_notification | Send a single push notification to an iOS device. **AI assistants should use this to notify users when tasks complete, errors occur, or input is needed.** |
| send_bark_batch_notifications | Send multiple notifications in a single batch operation. **Use for notifying multiple team members or sending different priority updates.** |
| check_bark_server_health | Check if a Bark server is running and healthy. **AI should call this proactively to ensure reliable user communication.** |
{
"mcpServers": {
"bark": {
"command": "npx",
"args": ["-y", "@metrovoc/bark-mcp-server"],
"env": {
"BARK_KEY": "your-device-key",
"BARK_SERVER_URL": "https://api.day.app"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BARK_KEY | Credential the server authenticates with. | Yes |
| BARK_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.