mcpField
P
publish-to-social

publish-to-social

github.com/gitroomhqMarketing & growth83123 installsUpdated 3d ago
Repository

About publish-to-social

publish-to-social is a skill for publishing finished agent-media videos to connected TikTok, Instagram, or X channels. It offers REST, CLI, and MCP interfaces, with human authorization required to connect channels.

Key features

  1. 01Connect supported social channels
  2. 02List and disconnect connected channels
  3. 03Publish videos immediately
  4. 04Schedule video posts

Use cases

  1. 01Publish a finished agent-media video
  2. 02Schedule a video for a selected channel
  3. 03Review connected channels before publishing

MCP support

Exposes MCP tools for connecting channels, listing them, and publishing videos. Channel connection returns an OAuth URL that a human must authorize.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gitroomhq/agent-media --skill publish-to-social

After installing, type/publish-to-socialin Claude Code to confirm it loaded.

Details

From the project README

Publish to Social

Post a finished agent-media video (an R2 video_url from any of the video skills) to the user's connected social channels: TikTok, Instagram, or X. Works from three surfaces: REST, the CLI (agent-media social ...), and MCP tools (social_channels / social_connect / social_publish). All calls use the user's Authorization: Bearer ma_... token against https://api.agent-media.ai.

1. Connect a channel (one-time, requires the human)

GET    /v1/social/providers             -> connectable networks: tiktok, instagram, instagram-standalone, x
POST   /v1/social/connect { provider }  -> { url }   # the user opens this OAuth url and authorizes
GET    /v1/social/channels              -> { channels: [{ id, name, provider, profile, picture }] }
DELETE /v1/social/channels/:channelId   -> disconnect

The connect step returns an OAuth URL the human must open and authorize; an agent cannot complete OAuth itself. Once authorized, the channel appears in /v1/social/channels with an id you pass to publish.

CLI: agent-media social providers · agent-media social connect x · agent-media social channels. MCP: social_connect { provider } (returns the URL for the user) · social_channels.

2. Publish a video

curl -X POST https://api.agent-media.ai/v1/social/publish \
  -H "Authorization: Bearer ma_..." -H "Content-Type: application/json" \
  -d '{ "video_url": "https://pub-...r2.dev/generation-outputs/<user>/<job>/...mp4",
        "channel_ids": ["<channel-id-from-/channels>"],
        "caption": "made with agent-media",
        "type": "now" }'    # or "type":"schedule" + "date":"2026-06-01T10:00:00.000Z"

CLI: agent-media social publish --video <url> --channels <id,id> --caption "..." (add --at <iso> to schedule). MCP: social_publish { video_url, channel_ids, caption, type }.

video_url must be an agent-media R2 URL (the output of a video skill); agent-media re-hosts it on the publishing provider for you. channel_ids come from /v1/social/channels. Per-network requirements (e.g. X reply settings) are filled in server-side; you don't send them.

Returns { success: true, media_id, post_ids: ["..."] }. A real post was created only when post_ids is non-empty; treat an empty post_ids as a failure, not a success.

Typical flow

  1. Produce a video with generate_video and take final_output.video_url.
  2. If the user has no connected channel, send them to connect (step 1); you can't OAuth for them.
  3. Publish that video_url to the chosen channel_ids; confirm post_ids came back.

Note: social operations run on a shared rate budget: don't poll; connect once and publish on demand.

Comments

Markdown supported