Built for AI agents

Your AI agent can post too.

Hosted MCP server. Full REST API. Webhooks. Zapier, n8n, Make. Anything that talks HTTP — or thinks for itself — can publish to your social channels.

Get started free → See what agents can do
Plays well with
  • Claude
  • Cursor
  • Zed
  • Zapier
  • n8n
  • Make
  • Custom agents
— What you can build

Four ways to let machines post.

Pick whichever matches the agent or workflow you already use. They're all free, on every plan, with the same flat rate.

Hosted MCP server

Drop one URL into Claude Desktop, Cursor, Zed — or any MCP-compatible client — and your agent gets eight tools immediately. No servers to spin up. No glue code.

Full REST API

The same endpoints we use ourselves. Bearer tokens with Sanctum, JSON in / JSON out, predictable resources for spaces, accounts, slots, and posts. No upgrade required.

Webhooks

Get notified when posts publish, fail, or get a reply. Pipe events into your CRM, your monitoring, your AI agent's memory — anywhere a URL can listen.

No-code automations

Pre-built integrations with Zapier, n8n, and Make. Wire up your CMS, Notion, Sheets, Airtable, or your inbox — without writing a single line of code.

— Just ask

Say it. It does the work.

Skip the dashboard for the small stuff. Here are the kinds of things your agent already knows how to handle.

Plan my next two weeks across every channel.

Drafts and queues fourteen posts, slotted into your recurring weekly times.

Schedule this Reel for Friday at 6pm.

Queued for Instagram and TikTok at the same time, ready to publish.

What's queued for next week?

Reads back every scheduled post with the channel, time, and caption preview.

Set up Mon, Wed, Fri 9am slots.

Creates three recurring weekly slots, ready to be filled by your queue.

Crosspost this to Instagram, TikTok, and LinkedIn.

Publishes to all three accounts as one cluster you can track together.

Turn this into a Threads thread with three replies.

Drafts the lead post and three connected replies, queued together as one thread.

— Setup in seconds

One config. Any agent.

Drop the MCP URL into Claude, Cursor, or Zed — or hit the REST API directly. Bring your own bearer token; we'll handle the rest.

agent-ready 
# Add Zilfu to Claude Desktop, Cursor, Zed, or any MCP client.
{
  "mcpServers": {
    "Zilfu": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://zilfu.app/mcp/social-media",
        "--header",
        "Authorization: Bearer ${SOCIAL_MEDIA_TOKEN}"
      ],
      "env": {
        "SOCIAL_MEDIA_TOKEN": "<paste your api token>"
      }
    }
  }
}
# Or skip the agent — talk to the API directly.
curl -X POST https://zilfu.app/api/posts \
  -H "Authorization: Bearer sk_live_xxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "5 mobile-first design tips ✨",
    "networks": ["instagram", "tiktok"],
    "schedule_at": "2026-04-24T18:00:00Z"
  }'
✓ Response · 200 OK
{
  "id": "post_8aB3xY9k",
  "status": "scheduled",
  "scheduled_at": "2026-04-24T18:00:00Z",
  "networks": [
    { "name": "instagram", "status": "queued" },
    { "name": "tiktok",    "status": "queued" }
  ]
}
Free on every plan

API and MCP server included on Free, Starter, Pro, and Business — same endpoints, no upsells.

No infrastructure

Hosted MCP server. Just drop the URL — we run it, keep it patched, and scale it.

Webhooks included

React to publish, failure, and reply events. Pipe them anywhere a URL can listen.

— Real-world workflows

Set the agent loose. Watch it ship.

A few things our customers already automate. None of these required a single line of integration code on Zilfu's side.

Claude · MCP

"Plan my next two weeks."

Ask Claude to draft fourteen posts based on your last shipped features, then drop them straight into your queue. One conversation, two weeks of content.

CMS · Webhook

Publish post → social.

When a new article hits your CMS, a webhook fires Zilfu to crosspost a teaser to LinkedIn, Threads, and Bluesky — with the canonical link baked in.

n8n · API

Daily digest from Notion.

Each morning, n8n reads your Notion content board, picks today's "ready" item, and schedules it to every connected channel via the REST API.

— FAQ

Agents, asked and answered.

Anything that speaks the Model Context Protocol — Claude Desktop, Cursor, Zed, and a growing list of agent frameworks. If your client supports MCP, it works with Zilfu.

No. Both the REST API and the hosted MCP server are available on every plan, including Free. Same endpoints, same tools — your monthly post limit is the only difference.

Sign in, head to Settings → API tokens, and create one. Tokens are bearer tokens — paste them into your MCP config or pass them as Authorization: Bearer … in API calls.

Tokens are scoped to your account, so an agent can only do what you can. Most clients also confirm tool calls before running them. Posts always show up in your queue, so nothing publishes silently.

The API and MCP server share generous, per-token rate limits — plenty for daily agent workflows. If you're building something bigger, get in touch and we'll work out the right ceiling.

Absolutely. The REST API exposes every primitive — spaces, accounts, slots, posts, media — and webhooks fire on every meaningful event. Wire it into your own framework, runtime, or chat UI.

Hand the keys to your agent.

Free forever, no credit card. Wire up Zilfu and let your AI handle the busywork.

Get started free →