MCP server talking to Bark notification server for iOS
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"bark-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# bark-mcp A Model Context Protocol (MCP) server that connects to [Bark](https://github.com/Finb/bark-server), a notification server for iOS. This allows LLM applications to send notifications to iOS devices through the MCP standard. ## Features - Simple MCP server implementation using FastMCP - Single tool: `notify` to send notifications to iOS devices - Configurable via environment variables - Easy to use command-line interface ## Installation ```bash # Install from PyPI pip install bark-mcp # Or install from source git clone https://github.com/yourusername/bark-mcp.git cd bark-mcp pip install -e . ``` ## Configuration The server requires the following environment variables: - `BARK_SERVER_URL`: URL of the Bark server (e.g., `https://api.day.app`) - `BARK_API_KEY`: Your Bark API key/device key You can set these variables in your environment or create a `.env` file: ``` BARK_SERVER_URL=https://api.day.app BARK_API_KEY=your_api_key_here ``` ### Bark API Format The server uses the Bark API with the following URL formats: - `GET /{bark-key}/{title}/{content}?url={url}` (when title and URL are provided) - `GET /{bark-key}/{title}/{content}` (when only title is provided) - `GET /{bark-key}/{content}` (when only content is provided) ## Usage ### Command Line Start the MCP server using either of these commands: ```bash # Using the standard command (after installing the package) bark-mcp # Using uvx (runs without installing the package) uvx bark-mcp ``` Both commands support the same options: ```bash # Specify a .env file bark-mcp --env-file /path/to/.env # or uvx bark-mcp --env-file /path/to/.env # Enable debug logging bark-mcp --debug # or uvx bark-mcp --debug ``` > **Note**: `uvx` is a command from the `uv` package manager that runs Python tools in temporary, isolated environments without installing them permanently. Install it with `pip install uv`. > > **Important**: Make sure to use `uvx bark-mcp` with a hyphen, not `uvx bark_mcp` with an unde…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.