Sendible MCP Server
Posts, inbox replies, approvals and reports for your Sendible workspaces.
होस्ट किया गया MCP सर्वर
npx add-mcp 'https://cotlet.dev/mcp/v1/sendible'Claude Code, Codex, Cursor और अन्य में इंस्टॉल होता है
दस्तावेज़
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Sendible API and MCP server: Let your AI agent clear the Sendible inbox for every client.
Sendible has no MCP server and no public API docs: developers.sendible.com and sendible.com/api both redirect to the home page (checked 27 Oct 2026). Cotlet runs 14 Sendible tools hosted, over MCP for agents and REST for scripts, in your own Sendible login.
Posts, inbox replies, approvals and reports for your Sendible workspaces. 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 Sendible
- Page: https://cotlet.dev/integrations/sendible-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Sendible. Sendible is a trademark of its owner. If Sendible's own integrations cover what you need, use them first.
What can you automate in Sendible?
- Triage the Priority Inbox each morning
- Chase posts waiting for client approval
- Write a weekly report per client
- Schedule a month from a content plan
- Fill an evergreen queue
- Find posts that failed to publish
Does Sendible have an MCP server or an API?
- Sendible's Zapier app, launched in January 2026, has no triggers and 4 actions: Create Scheduled Post, Create Queued Post, Delete Post and Approve Draft Post. Zapier MCP offers the same 4, at 2 Zapier tasks per call.
- Nothing official reads the calendar, the Priority Inbox, approval tasks or reports, replies to a comment or rejects a post.
- Sendible's terms mention access "via our API". Its software integrators page sells API, white label and SSO to SaaS platforms after a demo, with no public docs.
| What you need | Zapier and Zapier MCP | Partner API | Cotlet |
|---|---|---|---|
| Schedule or queue a post | Yes | Not documented | Yes, after your OK |
| Read posts, tasks, inbox and reports | No | Not documented | Yes |
| Reply to a comment or message | No | Not documented | Yes, after your OK |
| Send for approval, approve, reject | Approve only | Not documented | All three |
| What you need first | A Zapier account | A demo and a contract | Any Sendible plan |
| Price on top of Sendible | Zapier tasks | Not published | Pay per call |
Checked 27 Oct 2026. Sources: Sendible Help: Automate tasks using Zapier and Sendible, Zapier: Sendible triggers and actions, Zapier MCP for Sendible, Sendible: software integrators, Sendible changelog
How does Cotlet connect to Sendible?
- Sign in to Sendible. 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 Sendible password, and no post, reply or approval goes out until you approve it.
Connect Sendible 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.
- Enable Sendible for agents. Create a Cotlet account, log in to Sendible with your own admin or team login in its Cloud Browser, then press Enable for agents.
- Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
- Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Sendible shares the address https://cotlet.dev/mcp/v1 with every other app you enable. If you enabled Sendible after connecting, refresh the connector and the 14 tools appear.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-sendible \
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-sendible": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-sendible]
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: sendible_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: sendible_write
How to use the Sendible REST API
Create your Cotlet API key
Create a Cotlet API key with access to Sendible and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Sendible in Cotlet and enable it for agents. Account access: Your own Sendible account (admin or team member; approvals and the report builder need a plan that includes them).
Make your first Sendible API request
REST:
curl https://cotlet.dev/api/v1/sendible/workspaces \
-H "Authorization: Bearer $COTLET_API_KEY"
Read workspaces 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": "sendible",
"tool": "list_workspaces",
"result": {
"workspaces": [
{
"workspace_id": "ws_4821",
"name": "Harbor Dental",
"time_zone": "Europe/London",
"profiles": 3,
"publishing_paused": false
},
{
"workspace_id": "ws_4822",
"name": "Northside Bakery",
"time_zone": "Europe/London",
"profiles": 2,
"publishing_paused": false
}
]
}
}
Returns every workspace you can open, with its time zone, the number of profiles and whether publishing is paused. Sendible keeps one workspace per client, brand or location, and the other tools need a workspace_id from this list.
A paused workspace shows its posts as sent although nothing was published.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Sendible workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Posts of a workspace calendar, filtered by status, network, profile, queue or dates. Use list_posts in your configured marketing report. |
| Make | HTTP > Make a request | Comments and messages from Activity > Priority Inbox, with sentiment. Use list_inbox_messages in your configured marketing report. |
| Python or Node.js | REST API | A Quick Report from Reports > All Reports for a date range: engagement or one network. Use get_report in your configured marketing report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Sendible; 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.
Sendible API endpoints and MCP tools
Workspaces, profiles and users
Every other tool takes a workspace_id from here. Connecting a social profile or adding a user stays in Sendible, because both need the network's own login or an invite.
- List workspaces (
list_workspaces, read): Workspaces of your Sendible account: one per client, brand or location. - List social profiles (
list_profiles, read): Connected social profiles of a workspace, with network and inbox alerts. - List users (
list_users, read): Users of a workspace with their type, so you know who can approve a post.
Posts and queues
The calendar goes back 12 months. A post takes text, one link and one image URL. Published posts still count toward your plan's daily limit per workspace, from 100 on Core to 500 on Elite.
- List posts (
list_posts, read): Posts of a workspace calendar, filtered by status, network, profile, queue or dates. - Get a post (
get_post, read): Full text, media, profiles, status and approval state of one post. - List queues (
list_queues, read): Queues of a workspace with their weekly time slots and how many posts wait in each. - Create a post (
create_post, write, asks first): Schedule a post, add it to a queue or save it as a draft, for one or more profiles.
Approval tasks
Approval workflows start on the Plus plan. "Marked as done" is not approval, so only approve and reject are offered.
- List approval tasks (
list_tasks, read): Tasks from Publish > Tasks: posts waiting for approval and assigned messages. - Send a post for approval (
send_for_approval, write, asks first): Send a post to a user for approval, with a comment. - Approve or reject a task (
decide_task, write, asks first): Approve and send a post, or reject it with a comment.
Priority Inbox
Only profiles with inbox alerts on show up, 1 to 2 hours late. Replies go out on Facebook, Instagram and LinkedIn; archive is undone with restore.
- List Priority Inbox messages (
list_inbox_messages, read): Comments and messages from Activity > Priority Inbox, with sentiment. - Reply to a message (
reply_to_message, write, asks first): Reply to a comment or message in the Priority Inbox. - Archive inbox messages (
archive_inbox_messages, write): Move messages out of the Priority Inbox into Archived Only, or restore them.
Reports
Quick Reports only, for a range that ends before today and starts within the last 90 days.
- Get a Quick Report (
get_report, read): A Quick Report from Reports > All Reports for a date range: engagement or one network.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/sendible-api-mcp-server#tools
Who can see my Sendible session, and how do I revoke it?
- What we store. Your logged-in Sendible profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 14 Sendible tools, never the session cookie.
- What the session sees. Every workspace your login opens: posts, inbox, clients, reports.
- What no tool touches. Billing, users, white label, profile connections, deletes.
- If Sendible logs you out. You log in again yourself, in the same Cloud Browser.
- How to cut access. Disable for agents, reset the browser, or change your Sendible password.
The tokens for each client's Facebook, Instagram and LinkedIn stay with Sendible, which connected them; Cotlet never sees them, and the agent reaches those profiles only through Sendible. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads the open tasks. Every request you sent, with its approver and label.
- Sorts by the clock. "Received on" first: approving those posts sends them at once.
- Finds unsent drafts. Drafts with a publish time that nobody sent for approval.
- Waits, then sends. Each approval request shows up in your Cotlet console first.
| Action | Undo |
|---|---|
| Archive inbox messages | Yes, restore with the same tool |
| Create a draft | Yes, delete it in Sendible; nobody saw it |
| Schedule or queue a post | Delete it in Sendible before its slot; after that it is public |
| Send for approval | Reject or edit it; the approver already got the email |
| Approve, reject | A reject can be sent again; an approved post goes out |
| Reply to a message | No |
4 of 14 tools ask first: create_post, send_for_approval, decide_task and reply_to_message. Archiving reaches no one and restores in one call, so it runs at once, like every read. You can turn the wait off per tool, for example for drafts you check later in Sendible.
No tool deletes a published post. Sendible itself deletes them only for Facebook, from the Social Feeds view.
MCP call:
{
"name": "create_post",
"arguments": {
"workspace_id": "ws_4821",
"profile_ids": [
"pr_301",
"pr_302"
],
"message": "Open this Saturday, 9 to 1. Book at harbordental.example/book",
"url": "https://harbordental.example/book",
"mode": "schedule",
"send_at": "2026-10-23T09:00:00"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/sendible/workspaces/ws_4821/posts \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"profile_ids":["pr_301","pr_302"],"message":"Open this Saturday, 9 to 1. Book at harbordental.example/book","url":"https://harbordental.example/book","mode":"schedule","send_at":"2026-10-23T09:00:00"}'
Response:
{
"post_id": "post_77a1",
"status": "scheduled",
"send_at": "2026-10-23T09:00:00+01:00",
"time_zone": "Europe/London",
"profiles": [
"Harbor Dental (Facebook Page)",
"Harbor Dental (Instagram)"
]
}
A cron job or n8n flow can call the same tools over REST at /api/v1/sendible with the same key and price, for example the open approvals of every workspace mailed to you at 4 pm. A post for a profile ID that is not in the workspace fails, and failed calls are free. Each tool row above shows its REST path.
How much does the Sendible MCP server cost?
About $42 a month for an agency with 5 client workspaces, 7,250 credits. Your Sendible plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Priority Inbox triage, 5 clients, each workday | 11 × 22 | 2,420 |
| Open approvals check, each workday | 6 × 22 | 1,320 |
| Weekly report, 5 clients | 16 × 4 | 640 |
| Failed-post check, weekly | 8 × 4 | 320 |
| A month of posts, 20 per client | 21 × 5 | 1,050 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 7,250 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser, one for all workspaces
- Works on Core to Enterprise; approvals need Plus
Sendible publishes no post or message counts per account, so the month is our example. For scale, Sendible Premium, the plan it marks most popular, is $199 a month for 7 workspaces of 6 profiles each, and Core is $35 for one. Dollars at the $29 pack rate.
Sendible MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Zapier MCP for Sendible | Create Scheduled Post, Create Queued Post, Delete Post and Approve Draft Post as MCP tools. | No reads at all; cannot reply, reject or send for approval. 2 Zapier tasks per call. |
| Sendible for software integrators | White label, SSO, embedding and API access for SaaS platforms. | Sold after a demo, with no public docs or price. |
| viaSocket Sendible MCP | A generic MCP page for Sendible. | Lists no Sendible actions yet. |
| api-evangelist/sendible | A third-party profile of a Sendible API, 0 stars. | No code; its docs link redirects to the Sendible home page. |
We found no Sendible MCP server or CLI on GitHub, and n8n and Composio have no Sendible node or toolkit. If a planning tool such as Airtable or Notion should push finished posts into Sendible, Sendible's own Zapier app does that. For the inbox, approvals and client reports, Cotlet works in the Sendible account you already run.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Sendible tools go to contact@cotlet.dev.
Sendible API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Sendible under Integrations in the console and log in to Sendible in its Cloud Browser. The trial starts when you sign up and asks for no card.
How do I connect Sendible to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Sendible 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 Sendible account through Cotlet, in their phone apps too.
What can ChatGPT do in Sendible?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Sendible: triage the Priority Inbox; weekly client social report; chase posts waiting for client approval. You ask in plain words, and anything that reaches other people waits for your OK first.
Which Sendible plan do I need?
Cotlet works inside your own Sendible account, so it needs no API plan. The features of your plan still apply: Sendible says approval workflows and editing a saved report are not on all plans. The daily posting limit also stays: 20 posts per workspace on a trial, then 100 on Core, 200 on Plus, 300 on Premium and 500 on Elite and Enterprise (Sendible Help: Account sending limits).
Which inbox messages can my agent read and answer?
Those in Sendible's Priority Inbox: Facebook Page comments, replies and direct messages, Facebook Ads comments, Instagram Professional comments, LinkedIn Company Page replies and YouTube comments. X, TikTok, Google Business, personal LinkedIn profiles and Instagram direct messages are not in it. Replies work for Facebook, Instagram and LinkedIn (Sendible Help: Overview of the Priority Inbox, Reply to a message).
What can it not do?
create_post takes text, one link and one image URL; it does not upload files or video. Nothing deletes a published post: Sendible itself allows that only for Facebook posts in the Social feeds view (Sendible Help: Can I delete posts on my social accounts). Billing, users, permissions and connecting social accounts stay in Sendible.
Does one Cloud Browser cover all my client workspaces?
Yes. Workspaces live inside one Sendible login, and every tool takes a workspace_id, so one browser and one daily fee cover all the clients your login can open.
Can it react when a comment comes in?
Cotlet has no Sendible trigger, and neither does Sendible's Zapier app. Run your agent on a schedule, such as every morning for the Priority Inbox.
Is the MCP server different from the REST API?
Only in how it is called. Both carry the same 14 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with Sendible?
No. Cotlet is independent and not affiliated with Sendible Limited.
Can I use the Sendible 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.