Build automation on top of your social.

The 28 MCP tools

The complete set. Grouped here for reading, but the server exposes one flat list.

The 29 REST endpoints

Every path is relative to the base URL above, and the pill on each row is the permission that route checks on your key.

• GET/workspacesaccounts:read

  The brands on the account. Everything else is scoped to one.

• GET/platformsaccounts:read

  Which platforms a workspace can publish to.

• GET/accountsaccounts:read

  The social accounts connected to a workspace.

• GET/brand-contextaccounts:read

  Brand voice, audience and DNA. Read it before writing copy.

• GET/contentcontent:read

  List content by state, platform or scheduled window.

• POST/contentcontent:write

  Create a draft. Prefer POST /posts, which also schedules.

• POST/postscontent:write

  Create and schedule across platforms in one call.

• POST/content/validatecontent:read

  Check a post against each platform's rules. Writes nothing.

• POST/content/approvepublish

  Approve items waiting in the review queue.

• GET/content/:contentIdcontent:read

  One item in full, including per-platform variants.

• PATCH/content/:contentIdcontent:write

  Edit text, media, tags or the scheduled time.

• DELETE/content/:contentIdcontent:write

  Delete a post and every publication attached to it.

• POST/content/:contentId/unschedulepublish

  Take a scheduled post off the calendar, back to draft.

• POST/content/:contentId/schedulepublish

  Set a future date and time. Must be in the future.

• POST/content/:contentId/publishpublish

  Publish immediately instead of queueing.

• GET/content/:contentId/publicationscontent:read

  Per platform status, including why one failed.

• GET/publicationscontent:read

  Sweep every publication. The way to find what failed.

• POST/generate-textcontent:write

  Write on-brand captions, one per platform.

• POST/mediamedia:write

  Import media straight from a public URL.

• POST/media/uploadsmedia:write

  Start a local-file upload. Returns a presigned PUT URL.

• POST/media/uploads/:uploadId/finalizemedia:write

  Close the upload and get the media id back.

• GET/mediamedia:write

  The media library, so you can reuse instead of re-upload.

• DELETE/media/:mediaIdmedia:write

  Delete one media item and detach it from any draft.

• POST/webhookswebhooks:manage

  Subscribe an endpoint to publish events.

• GET/webhookswebhooks:manage

  List your subscriptions.

• DELETE/webhooks/:webhookIdwebhooks:manage

  Remove a subscription.

• GET/webhooks/:webhookId/deliverieswebhooks:manage

  Every delivery attempt, with its response.

• POST/webhooks/:webhookId/pingwebhooks:manage

  Send a test event to check the endpoint.

• POST/webhooks/:webhookId/deliveries/:deliveryId/redeliverwebhooks:manage

  Replay one delivery that failed.

Scopes

The same six on both surfaces. An app or a key acts only inside the scopes you grant, and you can revoke either at any time.

• accounts:read

  See your workspaces, brand profile, and connected social accounts

• content:read

  Read your content and its publishing status

• content:write

  Create and update content drafts on your behalf

• publish

  Schedule and publish posts to your connected accounts

• media:write

  Upload, list and delete media in your library

• webhooks:manage

  Create, list, and delete webhook subscriptions on your behalf

Webhooks

Publishing is asynchronous, so you should not have to poll for the outcome. Register an endpoint and EzSocial posts to it when a queued post resolves.

• content.published

  A queued post went out. Carries the platform, the post id and the live URL.

• content.publish_failed

  A platform rejected it. Carries the reason the platform gave.

Getting started

1. 1

   Connect an account in the dashboard

   OAuth to Instagram, TikTok or LinkedIn happens in the app, once. Neither surface can add a connection for you, which is deliberate: a token grant is a decision, not an API call.

2. 2

   Pick your surface

   For your own code, generate an API key and send it as a bearer token. For an AI client, point it at the MCP URL and approve the scopes on the consent screen. There is no key to paste for MCP.

3. 3

   Create, schedule, publish

   Attach media by id, create the post, then either schedule it for a future time or publish it now. Subscribe a webhook if you want to be told when it lands.