Your AI.Your systems.One calendar.

Connect Claude, ChatGPT or any MCP app with one sign-in and let it write straight into a brand's calendar. Or post from your own systems with a REST API and signed webhooks. Either way, your approvals stay in charge.

Connect your AI Read the API guide

Write three posts for Harbour Roast's cupping on Saturday, in the voice of our best posts. Drafts for Instagram and Facebook.

writing_guideHarbour Roast: Instagram, Facebook rules; 12 recent posts

create_post× 3, drafts

Done: three drafts are in Harbour Roast's calendar for Thursday, Friday and Saturday morning. The Friday one leads with the R150 price, like your best post last month. Want me to send them to Thandi for approval?

Connect your AI

Indably runs an MCP server. Add it to your AI app, sign in, and choose what the app may do.

https://app.indably.com/mcp

Claude: Settings → Connectors → Add custom connector. Paste the address, then Connect.
ChatGPT: Settings → Apps & Connectors → Create, in developer mode. Paste the address and choose OAuth.
Claude Code, Cursor, VS Code: Add a remote MCP server over HTTP with the same address.
What it can do: List brands and accounts, read each network's rules and the brand's recent posts, upload images, create and schedule posts, send them for approval, and read results. Owners can also allow people and billing.
What it can't: See brands without the add-on, exceed the role you chose or your own, skip approvals, or see your network passwords.
Sign-in: OAuth 2.1 with PKCE and dynamic registration. Hour-long access tokens that renew themselves; a reused renewal token closes the connection.

Connect your AI is an add-on per brand. See pricing.

The REST API and webhooks

For your own systems: create posts, upload media, move them through approval, and read results. Indably tells you when a post goes live.

The API guide

POST https://app.indably.com/api/v1/workspaces/{brand}/posts
Authorization: Bearer ind_…
Idempotency-Key: order-1042-post

{ "caption": "Cupping on Saturday: ten seats.",
  "connections": ["…", "…"],
  "scheduleAt": "2026-10-24T07:00:00Z" }

Never twice: Every write takes an Idempotency-Key: send the same request again after a lost answer and you get the first post back, not a second one.
Webhooks: Published, failed, needs a check, approved, sent back. Signed with HMAC-SHA256, retried for a day, at least once.
Reference: OpenAPI 3 document. Errors are RFC 9457 problem details written for people.

Next week, planned by Friday.

Every feature switched on from the first day. No card until you decide to stay.

Start your free trial Talk to us first