MCP · REST API · CLI · SDK

Social media on autopilot.

AI agents, CI pipelines, and no-code workflows publish to Instagram, X, LinkedIn, TikTok, and six more platforms — through one API with MCP, CLI, and SDK in the box.

Free plan · no credit card · first automated post in 5 minutes

Driven by the tools you already use

ClaudeChatGPTCursorGeminin8nZapierMakeGitHub Actions

// no humans were needed

claude agent · mcp

› ▌

✎ drafting · "Dark mode is here 🌙 Flip it on in Settings → Appearance"

agent → publish_content({ connections, scheduledAt })

instagram-beaconhqscheduled

x-beaconhqscheduled

linkedin-beaconhqscheduled

— set for 9:00 AM — review it on the calendar anytime

10 platforms, one call

// the deck

Everything an agent needs. Nothing it shouldn't have.

Wire it up once — publishing, AI writing, retries, and team control all live behind the same two strings.

01

Connect accounts once

OAuth your socials into a workspace. Tokens encrypted, refreshed automatically.

02

Hand your agent one key

API key + workspace ID — it never sees accounts, tokens, or passwords.

03

Publish everywhere

One call fans out to every connection by slug.

quickstart

On autopilot in 5 minutes

Hand your agent the MCP server, drop the CLI into a pipeline, or call the API directly.

// Claude, Cursor, or any MCP client — .mcp.json
{
  "mcpServers": {
    "socifyr": {
      "command": "npx",
      "args": ["-y", "@socifyr/mcp"],
      "env": {
        "SOCIFYR_API_KEY": "sk_...",
        "SOCIFYR_WORKSPACE_ID": "ws_..."
      }
    }
  }
}
// then just ask: "Post our launch everywhere"
credentials

One key, not ten logins

Connect your socials once with OAuth. From then on, an agent needs exactly two strings — and never sees a token or password. Revoke the key, and it's out.

SOCIFYR_API_KEY=sk_••••••••••••

SOCIFYR_WORKSPACE_ID=ws_abc123

Accounts are addressed by slug, not by credentials:

instagram-mybrandx-myhandlelinkedin-mybrand
human in the loop

AI drafts, your team approves

An agent saves its work as drafts or schedules ahead — a teammate reviews in the dashboard and publishes, edits, or cancels before anything goes live.

reliability

Built for real failure modes

  • Structured errors, idempotent retries
  • HMAC-signed webhooks on completion
  • Timezone-aware scheduling
teams

Humans supervise, roles enforce

Owners manage keys, editors publish, contributors draft. One shared history shows every post — from people and pipelines alike.

// automation

Jobs people stopped doing by hand

Every card below is an hour a week someone got back. Yours is in here somewhere.

Your agent drafts, you approve

Claude writes the week’s posts into drafts overnight. Monday morning, your editor reviews the queue, tweaks two captions, and publishes — AI speed, human judgment.

Ship at 2 a.m., announced by 2:01

A deploy lands overnight. GitHub Actions posts the release to X, Bluesky, and Threads before you wake up.

Write once, post everywhere

A new article hits your RSS feed — it becomes a post on LinkedIn, X, and Facebook without a single copy-paste.

Any trigger becomes a post

Form submission, new product, Stripe sale — one n8n or Make node turns any event into a social post.

A month of content in one sitting

Queue 60 posts with timezone-aware scheduling. Every account posts at its own audience’s 9 a.m.

One platform fails, nine don’t wait

Instagram hiccups while the rest succeed. Retry just the failed channel — no duplicates, ever.

// in production

Trusted by teams worldwide

Digital media outlets, humanitarian networks, and AI labs reach audiences across ten platforms.

also included

A dashboard for the humans

The same API, with a visual interface on top. Compose posts, browse media, track per-channel results, and manage who on your team can do what.

  • Compose and preview across platforms
  • Media library with reuse
  • Publishing history and per-channel results
  • Team workspaces and roles
Dashboard
24Published
8Scheduled
1Failed

// pricing

Free to start

No credit card. Start free, upgrade when your workflow grows.

Free

Get started with basic publishing

Free
  • 10 uploads per month
  • 1 GB media storage
  • 10 platforms
  • 1 API key
  • Scheduling
  • Media library
  • Webhooks
  • Team members
Recommended

Pro

For creators and developers

$9.99/month
  • Unlimited uploads
  • 50 GB media storage
  • 10 platforms
  • 5 API keys
  • Scheduling & timezone
  • Media library
  • Up to 3 team members
  • Webhooks

Business

For teams and agencies

$24.99/month
  • Unlimited uploads
  • 500 GB media storage
  • 10 platforms
  • Unlimited API keys
  • Scheduling & timezone
  • Media library
  • Unlimited team members
  • Webhooks & priority support

// faq

Agent questions, answered

The things people check before pointing an AI at their social accounts.

How does an AI agent post through Socifyr?

Add the Socifyr MCP server to your agent’s config (one npx command). The agent discovers tools like publish_content and list_connections, and from then on "post our launch to Instagram and X" just works — the agent picks the accounts by slug and publishes.

What credentials does my agent need?

Exactly two strings: a Socifyr API key and a workspace ID. Your social accounts are connected once via OAuth in the dashboard — the agent never sees tokens or passwords, and revoking the key cuts off its access instantly.

Which AI tools work with it?

Anything that speaks MCP — Claude (Desktop and Code), Cursor, and other MCP clients. Agents built on custom stacks use the REST API or TypeScript SDK; n8n, Zapier, and Make connect through the API as well.

Can AI write the posts too?

That’s your agent’s job — Socifyr has no built-in AI. Claude, GPT, or your own model writes the content and sends it in through the MCP server or API: as a draft for your team to review, or straight to publish. Socifyr handles validation, scheduling, fan-out, and delivery.

Which platforms can an agent publish to?

Instagram, Facebook, YouTube, X, LinkedIn, TikTok, Threads, Bluesky, Pinterest, and Reddit — all through the same call.

What happens when one platform fails?

Each platform is tracked as its own channel with its own status. If Instagram hiccups while nine others succeed, you retry just the failed channel — idempotency keys guarantee no duplicate posts.

Can my team supervise what agents publish?

Yes — this is the recommended setup. Have your agent save posts as drafts and let an editor review and publish them, or let it schedule ahead and check the calendar before posts go live. Teammates join with role-based permissions, and the history shows every post with per-channel results, whether a person or a pipeline created it.

How is this different from Ayrshare or Buffer?

Buffer and similar schedulers are dashboards built for humans. Ayrshare is an API, but it starts at $299/month. Socifyr gives you the MCP server, CLI, SDK, and a full dashboard on every plan — starting free.

Tonight’s post could publish itself.

Set it up now, wake up to the announcement already live. Every post you publish by hand is a workflow you haven’t automated yet.

10

platforms

1

API call

5 min

to first post

No credit card. 10 posts a month on us, forever.