Integration

Postifys integration

Publish to the social accounts you connected in Postifys: Facebook Page posts (images, Reels, feed posts, Stories), Instagram professional posts, YouTube video uploads, Pinterest image Pins, LinkedIn member posts and TikTok videos (Direct Post or Draft Upload). The publish tools post publicly, except YouTube uploads (private unless privacyStatus says otherwise) and TikTok (the privacy level you choose). You can also list connected accounts, Pinterest boards and TikTok creator options, prepare remote media, check post and media status, and read recent publish history. Postifys publishes through each network's official API (Meta Graph API, YouTube Data API, Pinterest API v5, LinkedIn member sharing, TikTok Content Posting API) with the access you granted when connecting each account in the Postifys dashboard. Left out: the Content Queue scheduler (an optional server feature whose request and response fields Postifys does not document), retrying a failed post (documented for browser sessions only; publish again instead), account connection, OAuth and sign-in routes, Meta callbacks and the TikTok token refresh. Authentication is a Postifys API key created in Postifys Settings (Postifys suggests the connections, media, publish and status scopes), sent as a Bearer token; publishing needs a paid seat after the 7-day trial.

Connect Postifys How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Postifys.Built from the 15 Postifys tools below, on the connection you add once.

What you can do with Postifys

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Post, 6 operations

create_pinterest_pinCreate pinterest pinPOSTAgents: ask firstCreates an image Pin on a board of a connected Pinterest account; it is visible to everyone who can see that board. Returns the history id and Pinterest's pin id.
publish_facebook_postPublish facebook postPOSTAgents: ask firstPublishes PUBLICLY on a connected Facebook Page: a photo, a Reel, a text or link feed post, or a Story (expires after about 24 hours). Returns the history id and Facebook's post id.
publish_instagram_postPublish instagram postPOSTAgents: ask firstPublishes PUBLICLY on a connected Instagram professional account: an image, a video or Reel, or a Story (expires after about 24 hours). Returns the history id and Instagram's media id.
publish_linkedin_postPublish linkedin postPOSTAgents: ask firstPublishes a post at once on a connected LinkedIn member profile, seen by the member's LinkedIn audience (no draft, no visibility choice): text, image, video or link preview. No Company Pages. Returns the history id and LinkedIn's share id.
publish_tiktok_videoPublish tiktok videoPOSTAgents: ask firstPublishes a video to a connected TikTok account: postMode direct posts it to the creator's profile at the chosen privacy level, inbox sends a draft the creator finishes in TikTok. Read get_tiktok_creator_info first.
upload_youtube_videoUpload youtube videoPOSTAgents: ask firstUploads a video from a downloadable URL to a connected YouTube channel, private unless privacyStatus says otherwise (public makes it visible to everyone). Returns the YouTube video id and URL.

Status, 2 operations

get_media_jobGet media jobGETAgents: ask firstReads a media download job started by queue_media_download; each call reads it fresh. completed carries the serve URL to publish; failed carries a failure reason.
get_post_statusGet post statusGETAgents: ask firstReads the current state of a post submitted with async or still processing on the network, by postId; each call reads it fresh. Final states include published and failed (with a failure reason).

Board, 1 operation

list_pinterest_boardsList pinterest boardsGETAgents: ask firstLists the boards of a connected Pinterest account (id and name); create_pinterest_pin needs one of these board ids.

Connection, 1 operation

list_connectionsList connectionsGETAgents: ask firstLists the social accounts connected in Postifys (Facebook Pages, Instagram, YouTube, Pinterest, LinkedIn, TikTok) with their ids, names, usernames and avatars; pass an id as the target of a publish tool.

Creator info, 1 operation

get_tiktok_creator_infoGet tiktok creator infoGETAgents: ask firstReturns a connected TikTok creator's current publishing options (allowed privacy levels, whether comments, duets and stitches can be enabled); read it before publish_tiktok_video with postMode direct.

Post history, 1 operation

list_post_historyList post historyGETAgents: ask firstLists recent Postifys publish attempts, newest first, with platform, status, target account, text, media URLs, failure reason and creation time. Use it to find failed posts or a post whose id was lost.

Queue, 1 operation

queue_media_downloadQueue media downloadPOSTAgents: ask firstQueues a remote media file (a Google Drive or Dropbox share link, or any URL) for Postifys to download in the background; poll get_media_job with the returned media job id until it is completed, then publish its serve URL.

Test, 1 operation

test_api_keyTest api keyGETAgents: ask firstChecks that the connected Postifys API key is accepted; any successful answer means it is. Use it to diagnose a connection before publishing.

Upload, 1 operation

upload_mediaUpload mediaPOSTAgents: ask firstUploads a stored file to Postifys as temporary media and returns a short-lived serve URL to pass to a publish tool.

Use Postifys from Claude Code, Cursor or Codex

Connect Postifys in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Postifys operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Postifys

Create your workspace
Sign up free. Nothing to install.
Connect Postifys once
Add your Postifys connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.