Hosted MCP server
Drop one URL into Claude, Cursor, Zed — or any MCP-compatible client — and your agent gets twelve tools: posts, drafts, slots, media, accounts. No servers to run, no glue code.
Built for AI agents
The social media scheduler your AI agent can drive.
Point Claude, Cursor, or any MCP client at Zilfu and your agent can plan, draft, schedule, and publish across seven networks — while every post lands in a queue you control.
Free plan · No credit card · MCP & API on every plan
Works with
- Claude
- Cursor
- Zed
- Zapier
- n8n
- Make
- Custom agents
— Just ask
Say it. It does the work.
These aren't hypotheticals — each request maps to tools your agent gets the moment you paste the config.
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.
— Four surfaces
Four ways to let machines post.
Pick whichever matches your stack. All four are included on every plan — even Free.
Full REST API
The same endpoints the app runs on. Bearer-token auth, JSON in and out, predictable resources for workspaces, accounts, slots, posts, and media.
Webhooks
Know the moment a post publishes, fails, or gets scheduled — or an account connects or drops. Pipe events into your CRM, your monitoring, or your agent's memory.
No-code automations
Webhooks and a clean REST API slot straight into Zapier, n8n, and Make. Wire your CMS, Notion, Sheets, or inbox to your social queue without writing code.
— You keep final say
Agents draft. You approve.
The obvious fear: your agent posts something embarrassing at 2am. Zilfu is built so it can't. Ask for drafts and nothing goes live until you say so. Want a harder guarantee? Invite the agent as a teammate without publish permission — everything it creates routes into the approval queue automatically, waiting for a human.
Approvals and unlimited teammates are on every plan — the agent gets machine speed, you keep human judgment.
Start free →
Drafted by your agent · Instagram + LinkedIn
Pending
Your best posting slot last month? Saturday, noon. Here's the heatmap — and the three posts that proved it 📊
— Setup
Two minutes, start to first post.
No SDK to install, no server to deploy. If you can paste a config, you're done.
01
Connect accounts
Sign up free and link Instagram to X — as many accounts per network as you run.
02
Create a token
Settings → API tokens. One token covers every workspace you belong to.
03
Paste the config
Drop the MCP URL into Claude, Cursor, or Zed — or skip it and call the REST API.
04
Ask away
"Plan my week." Review what it drafts, approve, and let the queue do the rest.
— The config
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.
# 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/spaces/42/posts \ -H "Authorization: Bearer <your api token>" \ -H "Content-Type: application/json" \ -d '{ "space_id": 42, "at": 1784311200000, "items": [ { "account_id": 7, "social": "instagram", "main": { "content": "5 mobile-first design tips ✨" } } ] }'
✓ Response · 200 OK
[
{
"id": 812,
"status": "Scheduled",
"scheduled_at": "2026-07-17T18:00:00+00:00"
}
]
Free on every plan
API, MCP server, and webhooks included from day one — the free tier gets the same endpoints as the paid ones.
No infrastructure
The MCP server is hosted. Just paste the URL — we run it, patch it, and scale it.
Everything documented
Full API reference, MCP guide, and webhook payloads at docs.zilfu.app.
— Real-world workflows
Set the agent loose. Watch it ship.
Three patterns you can wire up this afternoon — with zero integration code on Zilfu's side.
Claude · MCP
"Plan my next two weeks."
Ask Claude to draft fourteen posts from your last shipped features, then drop them straight into your queue. One conversation, two weeks of content.
CMS · API
Blog post → social, automatically.
When an article ships, your CMS calls the Zilfu API to queue a teaser for LinkedIn, Threads, and X — canonical link included.
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.
— FAQ
Agents, asked and answered.
MCP (Model Context Protocol) is the open standard that lets AI assistants like Claude use outside tools. Zilfu hosts an MCP server, so your assistant can act inside your workspace — drafting, scheduling, and publishing posts — instead of writing captions you paste in by hand.
Anything that speaks MCP: Claude Desktop, Claude Code, Cursor, Zed, and most agent frameworks. If your client supports remote MCP servers with a bearer token, it works. No MCP? Any agent that can make an HTTP request can use the REST API.
No. The REST API, hosted MCP server, and webhooks are on every plan, including Free — no credit card. Plans only change how many social accounts you connect; Free includes 2 accounts and 20 posts a month.
About two minutes. Sign up, connect a social account, create an API token in Settings, and paste the MCP config into your client. Your agent's first post is one prompt away.
You decide how much rope it gets. Tokens are scoped to your account and revocable anytime. Ask the agent for drafts and nothing goes live until you approve — or invite it as a teammate without publish permission, and everything it creates routes into the approval queue automatically. Every action shows up in your calendar, so nothing publishes silently.
All seven Zilfu supports: Instagram, TikTok, Facebook, LinkedIn, Pinterest, Threads, and X — including multi-account posting, media uploads, and multi-part threads on networks that support them.
The API and MCP server share per-token rate limits sized for real agent workflows — the details are documented at docs.zilfu.app. Building something heavier? Get in touch and we'll work out the right ceiling.
Yes. The REST API covers workspaces, accounts, posts, media, slots, and webhooks — the same endpoints the app runs on. Webhooks notify you when posts publish, fail, or get scheduled, so your agent can react in real time.
Hand your agent the keys.
Create a token, paste one config, and let the agent handle the busywork — you keep the approvals. Free plan, no credit card.
Drafted from Friday's changelog. Two more variants queued for review.