Bark MCP Server
Leads, responses and credits for Bark professionals.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/bark'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Bark API and MCP server: Let your AI agent work your Bark leads before the 5th pro does.
Bark has no public API, no developer keys and no MCP server for professionals (checked 27 Oct 2026). Its help centre lists two integrations, Zapier and HubSpot. Cotlet runs 14 Bark tools hosted, over MCP for agents and REST for scripts, in your own seller login.
Leads, responses and credits for Bark professionals. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Bark
- Page: https://cotlet.dev/integrations/bark-api-mcp-server
What can you automate in Bark?
- Shortlist leads worth the credits
- Buy a lead under your credit cap
- Text or email your first message
- Send the estimate while it is fresh
- Chase quiet buyers in My Responses
- Mark hired and ask for a review
Does Bark have an MCP server or an API?
- The Bark app on Zapier has 3 triggers and 9 actions and searches: buy, skip, quote, note, status, find a lead, credit balance. Zapier MCP offers them as tools at 2 Zapier tasks a call.
- Nothing official emails or texts a buyer, sends a review invitation, lists My Responses or invoices, or stops a purchase above a credit price.
- Bark's own help article says Zaps are "one-way workflows": a note or status changed elsewhere never comes back into Bark.
| What you need | Zapier and Zapier MCP | HubSpot app | Cotlet |
|---|---|---|---|
| Read new leads | Trigger and search | Bought leads only | By tab, service and credits |
| Buy a lead | Yes, no credit cap | No | Under your cap, after your OK |
| Quote, note, status | Yes | No | Yes |
| Email or text the buyer | No | No | Your templates, after your OK |
| Review invite, responses list, invoices | No | No | Yes |
| Price on top of Bark credits | 2 tasks per MCP call | A HubSpot account | Pay per call |
Checked 27 Oct 2026. Sources: Bark on Zapier: triggers and actions, Zapier MCP for Bark, Bark Help Centre: Zapier, Bark on the HubSpot marketplace
How does Cotlet connect to Bark?
- Sign in to Bark. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Bark login, and no lead is bought and no buyer hears from you before you approve it.
Connect Bark to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Open Bark in a Cloud Browser. Create a Cotlet account, open Bark in its Cloud Browser, log in to your professional (seller) account yourself and press Enable for agents.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the link. Chat apps show a Cotlet sign-in page. Code editors, n8n and scripts send an API key from the console.
https://cotlet.dev/mcp/v1 serves every app you enable on Cotlet, Bark included. Enable Bark after connecting and the connector needs a refresh before its tools show up.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: bark_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: bark_write
How to use the Bark REST API
Create your Cotlet API key
Create a Cotlet API key with access to Bark and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Bark in Cotlet and enable it for agents. Account access: Your Bark professional (seller) account.
Make your first Bark API request
REST:
curl "https://cotlet.dev/api/v1/bark/leads?limit=5" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read leads and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "bark",
"tool": "list_leads",
"result": {
"leads": [
{
"lead_id": "61842207",
"service": "Wedding Photography",
"location": "Leeds, LS1",
"credits": 12,
"signals": [
"urgent"
],
"submitted": "2026-10-11"
},
{
"lead_id": "61841930",
"service": "Web Design",
"location": "Manchester, M1",
"credits": 9,
"signals": [
"first_to_respond"
],
"submitted": "2026-10-11"
}
]
}
}
Returns the leads Bark matched to your services and locations, newest first by default. Each item has the credit cost and signals such as urgent, so you can decide before you spend anything.
Reading a list spends no credits and notifies no customer.
limit: 1 to 50. Default: 20.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Bark workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Full request: the customer's answers, location, credit cost, responses so far and signals (urgent, verified phone, high hiring intent). Use get_lead in your configured business report. |
| Make | HTTP > Make a request | Leads you contacted (My Responses), with status, contact details and your notes. Use list_responses in your configured business report. |
| Python or Node.js | REST API | Credits available now, from My Credits. Use get_credit_balance in your configured business report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Bark; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Bark API endpoints and MCP tools
Leads before you buy
Reading a lead spends no credits and tells nobody. Contact details stay hidden until contact_lead, which Bark charges the moment it runs.
- Get lead preferences (
get_lead_preferences, read): Your services, locations and coverage areas from Settings > Lead Preferences. - List leads (
list_leads, read): Leads matched to your services and locations, newest first, with credit cost and signals. - Get lead (
get_lead, read): Full request: the customer's answers, location, credit cost, responses so far and signals (urgent, verified phone, high hiring intent). - Contact lead (
contact_lead, write, asks first): Spend credits to contact a lead and get their name, phone and email. Bark notifies the customer. - Skip lead (
skip_lead, write, asks first): Mark a lead Not interested. No credits are charged; Bark tells the customer politely.
My Responses and buyers
Bark notifies the buyer of every estimate, email and text. WhatsApp and calls stay in the Bark app.
- List responses (
list_responses, read): Leads you contacted (My Responses), with status, contact details and your notes. - Get response (
get_response, read): One contacted lead: customer's name, phone and email, request, estimate sent and status. - Send message (
send_message, write, asks first): Email or text a contacted customer from My Responses, as free text or one of your saved templates. - Send estimate (
send_estimate, write, asks first): Send a quote on a contacted lead. Bark notifies the customer. - Add note (
add_note, write): Private note on a contacted lead, to track the job. The customer does not see it. - Update response status (
update_response_status, write, asks first): Move a contacted lead to pending, hired or archived. - Request review (
request_review, write, asks first): Invite a customer who hired you to review you on Bark. The lead must be marked hired.
Credits and invoices
Buying credits and the Elite Pro subscription are not tools; they stay with you in Bark.
- Get credit balance (
get_credit_balance, read): Credits available now, from My Credits. - List invoices (
list_invoices, read): Invoices from Invoices and billing details, with date, amount and a download link.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/bark-api-mcp-server#tools
Who can see my Bark session, and how do I revoke it?
- What we store. Your signed-in Bark profile, encrypted with AES-256-GCM, in Finland. Never your password.
- What your agent gets. 14 Bark tools. No cookie and no login.
- What the session sees. What your Bark seller login sees: leads, My Responses, credits and invoices.
- What no tool touches. Buying credits, Elite Pro, payment cards, your profile, Lead Preferences and credit returns.
- If Bark logs you out. We email you a link. You log in yourself, we never do.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.
Bark buyers' names, phone numbers and emails pass through your agent once you buy a lead. Bark's terms (3.4.4) let you share Contacts with a third party only with Bark's written agreement, so keep them in your own tools and do not resell them. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results); there is no SOC 2 report or third-party pentest yet.
Is it against Bark's terms? Account safety
attempt to copy, modify, duplicate, create derivative works from, frame, mirror, republish, download, display, transmit, or distribute all or any portion of the Website in any form or media or by any means
Bark Terms & Conditions for Professionals, 3.4.1 (updated 1 Nov 2025, read 27 Oct 2026)
The clause is about copying Bark, not about an assistant reading your own leads, and neither the terms nor the Misuse of Bark FAQ mention bots or agents. Clause 3.10 still lets Bark suspend an account that misuses the Website "in any way", and the FAQ says a removal for misuse cannot be appealed. We found no public case of a Bark account closed over automation. Public complaints are about accounts Bark linked to banned ones "through payment and IP insights" (BBB, June 2024) (checked 27 Oct 2026).
How we keep your account looking like you:
- Your own seller login, entered by you
- One Cloud Browser with a steady IP and cookies, like your own office laptop
- Every purchase, message, estimate and review invite waits for your OK
- No tool copies Bark's directory or other professionals' profiles
- If Bark objects, we pause the Bark tools for everyone within 24 h
Bark tells the buyer the moment you contact a lead. Approve a short batch rather than ten leads in one minute, so the account keeps a human pace.
What happens when Bark changes?
- 12 h between tests of the Bark lead, response and credit reads
- 24 h between tests of writes a buyer would hear about
- $0 for a call to a Bark tool paused for a fix
Bark changes its rules as well as its screens: the 1 Nov 2025 terms cut credit validity from 12 months to 3, and the Bark for Professionals app was updated again on 14 Oct 2026. When a page moves, we repair the tool and keep its name and inputs. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Rechecks the lead. Credits and responses so far, read again right before buying.
- Waits for your OK. The purchase waits in your Cotlet console with its credit price and your cap.
- Writes to the buyer. Your template and the estimate, each waiting for its own OK.
- Notes it. Credits spent, template and price in a private note for the follow-up.
| Action | Undo |
|---|---|
| Contact a lead | No; a credit return only for Bark's listed reasons, within 14 days |
| Skip a lead | No tool brings it back; Bark has told the buyer |
| Send an estimate or a message | No; send a corrected one |
| Request a review | No; the invitation is out |
| Change a response status | Set the old status back |
| Add a note | Add a new note; the buyer never saw it |
6 of the 7 write tools ask first. Only add_note runs at once, because a private note reaches nobody. Reads run at once. For a scheduled run you can switch the wait off per tool; for contact_lead, keep it on or set max_credits on every call.
contact_lead with max_credits fails instead of buying when the price has gone up since the shortlist, and a failed call costs nothing on Cotlet and no Bark credits.
MCP call:
{
"name": "contact_lead",
"arguments": {
"lead_id": "61842207",
"max_credits": 15
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/bark/leads/61842207/contact \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"max_credits":15}'
Response:
{
"lead_id": "61842207",
"status": "pending",
"credits_spent": 12,
"credits_left": 88,
"service": "Wedding Photography",
"location": "Leeds, LS1",
"customer": {
"name": "Jordan",
"email": "client@example.com",
"phone": "+44 7700 900123"
}
}
A cron job or a lead dashboard can call the same tools over REST at /api/v1/bark, with one key and one price. Every tool row above lists its REST path.
How much does the Bark MCP server cost?
About $27 a month for one professional who buys about 10 leads, 4,580 credits. Bark credits for the leads are separate and paid to Bark.
| Job | Calls | Credits |
|---|---|---|
| Morning triage of new leads, each workday | 9 × 22 | 1,980 |
| Contact a lead, first message, estimate, note | 5 × 10 | 500 |
| Weekly follow-up of 4 quiet buyers | 13 × 4 | 520 |
| Mark hired and ask for a review | 2 × 3 | 60 |
| Credits and invoices, monthly | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 4,580 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No Elite Pro or Zapier plan needed
The month is our example: a triage run each of 22 workdays, 10 leads bought and quoted, a weekly follow-up and 3 hired jobs. Bark publishes no typical volume. Its own credits run about $2.35 each in the US and £1.80 in the UK, and a lead takes 5 to 20 or more. Dollars at the $29 pack rate.
Bark MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| js9uru/bark-leads-scraper | Python and Playwright: copies leads from your seller dashboard into Google Sheets. 0 stars, last push 21 Jul 2026. | Read only, no MCP, no license; you run and repair it. |
| Apify Bark scrapers | Several actors scrape the public directory of professionals, from about $1.30 per 1,000. | Public profiles only; nothing in your account. |
| bark-mcp servers on GitHub | MCP servers for the Bark iOS push notification app. | Not Bark.com; they send phone notifications. |
If buying and quoting from a fixed rule is enough, Zapier does it with the official Bark app. If you want new leads in a spreadsheet and can host a script, the scraper above does that. If your agent should judge leads, buy under a cap, write to buyers and follow up, Cotlet does that hosted.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Bark tools go to contact@cotlet.dev.
Bark API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Bark under Integrations in the console and log in to your Bark seller account in its Cloud Browser. The trial starts with your Cotlet account and needs no card.
How do I connect Bark to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Bark once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Bark account through Cotlet, in their phone apps too.
What can ChatGPT do in Bark?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Bark: find leads worth buying; contact leads and send quotes; follow up pending responses. You ask in plain words, and anything that reaches other people waits for your OK first.
Does it work with a free Bark account?
It works with the professional (seller) account you sign in with. Bark charges credits for each lead you contact, and contact_lead spends them only after your OK by default.
Does Bark have webhooks?
No. The three Zapier triggers (New Bark, New Purchased Bark, New Review) are the only events Bark sends out, and Zapier polls for them. To react to new leads, run your agent on a schedule and call list_leads.
Can the agent buy leads without asking me?
Only if you switch the approval off for contact_lead. Even then, set max_credits on every call: the purchase fails instead of spending more than your cap.
Is this the Bark push notification app or Bark parental controls?
Neither. This page is about Bark.com, the marketplace where professionals buy leads. The bark-mcp repos on GitHub send iOS push notifications, and Bark at bark.us is a parental control app.
Is the MCP server different from the REST API?
Only in how you call it. Both have the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and dashboards use REST.
Is Cotlet affiliated with Bark?
No. Cotlet is independent and not affiliated with Bark.com Global Limited.
Can I use the Bark API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.