Bark MCP integration for AI agents.
Connect AI agents to Bark through 4 structured actions, including get server info, send batch notifications, and send encrypted notification. Review authenti…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bark integration exposes
The Bark Agent App exposes 4 provider-backed actions for communication work. Its current contract lets an authorized agent fetch raw server information from the connected bark server, send the same notification to multiple explicit bark device keys through the rest push endpoint, and send a pre-encrypted bark notification ciphertext to the connected bark device. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bark account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bark capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_server_infoREADFetch raw server information from the connected Bark server.
send_batch_notificationsWRITESend the same notification to multiple explicit Bark device keys through the REST push endpoint.
INPUTS: device_keys / title / subtitle / body / level
send_encrypted_notificationWRITESend a pre-encrypted Bark notification ciphertext to the connected Bark device.
INPUTS: ciphertext
send_notificationWRITESend a notification to the connected Bark device through the REST push endpoint.
INPUTS: title / subtitle / body / level / volume
INPUT CONTRACTS
Know what the action needs before it runs.
send_batch_notifications
device_keysREQUIRED- The Bark device keys that should receive this notification.
titleOPTIONAL- Optional notification title shown above the body.
subtitleOPTIONAL- Optional notification subtitle.
bodyREQUIRED- Notification body text to send to the Bark device.
levelOPTIONAL- Optional iOS interruption level for the notification.
send_encrypted_notification
ciphertextOPTIONAL- The already-encrypted Bark ciphertext payload to forward.
send_notification
titleOPTIONAL- Optional notification title shown above the body.
subtitleOPTIONAL- Optional notification subtitle.
bodyREQUIRED- Notification body text to send to the Bark device.
levelOPTIONAL- Optional iOS interruption level for the notification.
volumeOPTIONAL- Optional ringtone volume for critical alert notifications.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Server Info
Fetch raw server information from the connected Bark server. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_server_infoControl Send Batch Notifications
Send the same notification to multiple explicit Bark device keys through the REST push endpoint. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
send_batch_notificationsVerify with Send Batch Notifications
Send the same notification to multiple explicit Bark device keys through the REST push endpoint. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
send_batch_notificationsSAFETY BOUNDARY
Operate Bark with explicit limits
- Authorize Bark with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bark rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bark task completed successfully.
CONNECTION MODEL
API key
Bark device key used as the device_key field for push requests. Open the Bark iOS app and copy the push URL shown in the tutorial, then paste either the key or full URL: https://bark.day.app/#/tutorial.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bark.