bark-mcp
by Delay-n-days
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BARK_KEY | Yes | Required. Bark device key, also used as the HTTP/MCP access token. | |
| BARK_HOST | No | Listen address; authentication is forced when binding to a non-loopback address. | 127.0.0.1 |
| BARK_PORT | No | Listen port. | 8787 |
| BARK_SERVER | No | Bark server URL; can be changed to a self-hosted service. | https://api.day.app |
| BARK_KEYS_FILE | No | Custom crypto key file; valid keys in this file take precedence over built-in defaults. | ./crypto_keys.json |
| BARK_MCP_TOKEN | No | Set this to use a different string as the access token instead of BARK_KEY. | |
| BARK_REQUIRE_AUTH | No | Set to 1 to require token verification even when listening only on localhost. | |
| BARK_ALLOW_CUSTOM_KEY | No | Set to 0 to prevent callers from supplying their own device_key. | 1 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues