Barkme Mcp Server

Created By
thevibeworks10 months ago
Overview

what is Barkme MCP Server?

Barkme MCP Server is a Model Context Protocol (MCP) server that facilitates sending iOS push notifications through the Bark service, allowing users to send notifications directly from Claude conversations.

how to use Barkme MCP Server?

To use Barkme MCP Server, you need to set it up with a Bark device key and integrate it with a MCP Client like Claude Desktop. You can install it via npm or from source, and configure it to send notifications.

key features of Barkme MCP Server?

  • Single tool interface for all notification scenarios.
  • Device aliases for user-friendly notification management.
  • Non-blocking notifications with structured logging.
  • Complete support for Bark API parameters, including encrypted messages.
  • Ability to update or delete notifications using notification IDs.

use cases of Barkme MCP Server?

  1. Sending reminders and alerts to iOS devices.
  2. Managing notifications for server maintenance or updates.
  3. Integrating with AI tools to automate notification sending.

FAQ from Barkme MCP Server?

  • What is required to use Barkme MCP Server?

You need Node.js 20+, a Bark device key, and a compatible MCP Client like Claude.

  • Can I customize notifications?

Yes! You can customize notification messages, titles, and urgency levels.

  • Is there a way to track notification delivery?

Yes, delivery status is logged to the console for monitoring.

Server Config

{
  "mcpServers": {
    "barkme": {
      "command": "node",
      "args": [
        "/your/path/to/barkme-mcp-server/dist/index.js"
      ],
      "env": {
        "LOG_LEVEL": "info",
        "BARK_DEVICES": "iPhone:<your device key>",
        "BARK_SERVER": "https://api.day.app",
        "BARK_GROUP": "Claude",
        "BARK_RETRY": "2",
        "BARK_ASYNC": "true"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
thevibeworks
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago