bark-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BARK_KEY | No | Your Bark device key (required for automatic usage) | |
| BARK_SERVER_URL | No | Bark server URL (optional, defaults to https://api.day.app) | https://api.day.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_bark_notificationA | Send a push notification via Bark to an iOS device. Use this to notify the user when: (1) Tasks are completed and need user attention, (2) Errors occur requiring user intervention, (3) User input or decisions are needed, (4) Testing or verification is required, (5) Long-running operations finish. Choose appropriate 'level' based on urgency: 'critical' for urgent issues, 'timeSensitive' for important updates, 'active' for general notifications. |
| send_bark_batch_notificationsA | Send multiple push notifications via Bark to multiple iOS devices. Use this for batch operations like: (1) Notifying multiple team members about project completion, (2) Sending progress updates to different stakeholders, (3) Broadcasting important announcements. Each notification can have different priority levels based on recipient needs. |
| check_bark_server_healthA | Check the health status of a Bark server. Use this to: (1) Verify notification system is working before important operations, (2) Troubleshoot notification delivery issues, (3) Monitor system health during automated workflows. Call this proactively to ensure reliable user communication. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/metrovoc/bark-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server