bark

MCP server from metrovoc/bark-mcp-server

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio metrovoc-bark-mcp-server npx -y @metrovoc/bark-mcp-server \
  --env BARK_KEY="your-device-key" \
  --env BARK_SERVER_URL="https://api.day.app"

How to use

This MCP server enables AI assistants to send iOS push notifications to Bark-enabled devices. It exposes three core tools: send_bark_notification for sending a single notification, send_bark_batch_notifications for sending multiple notifications in one call, and check_bark_server_health to verify that the Bark service is reachable and healthy. The server is designed to work with Bark features such as custom icons, sounds, URL redirection, notification grouping, and badge management, while supporting encrypted (ciphertext) content if needed. To use it, configure the Bark MCP server in your Claude/CLAUDE environment or within your MCP management setup using npx @metrovoc/bark-mcp-server, and provide your Bark device key and server URL via environment variables or Claude/OpenAI integration steps. When sending notifications, you can specify fields like body, title, subtitle, url, group, icon, sound, level, badge, and ciphertext to tailor how Bark renders the notification on iOS devices.

How to install

Prerequisites:

Node.js (recommended: LTS, e.g., 18.x) and npm installed
Network access to pull npm packages

Installation options:

Quick Start (recommended): use npx to run without a global install

npx @metrovoc/bark-mcp-server

Global Installation:

npm install -g @metrovoc/bark-mcp-server
bark-mcp-server

Local Installation (project-level):

npm install @metrovoc/bark-mcp-server
npx @metrovoc/bark-mcp-server

Configuration notes:

Ensure you have a Bark device key (BARK_KEY) and optional Bark server URL (BARK_SERVER_URL) if you customize the endpoint.
The MCP server expects to be run in an environment where the Bark API is reachable.
You can integrate the server into Claude/CLAUDE workflows as shown in the examples in the README ( Claude Code ); the server can also be wrapped with inspector tooling for debugging.

Additional notes

Tips and common considerations:

Environment variables: BARK_KEY is required for automatic usage; BARK_SERVER_URL defaults to https://api.day.app if not provided.
When testing, use the check_bark_server_health tool to ensure Bark is reachable before sending notifications.
For batch notifications, ensure each entry in the notifications array conforms to the same field names as a single notification (body is required).
If you leverage encryption, ensure ciphertext is provided and that your environment supports encryption handling.
If running locally, you can use npx for quick experiments or install globally for a persistent CLI experience.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.