Zilfu for X

Post to X.
From anywhere.

Write the take, build the thread, schedule the whole conversation. Zilfu keeps your X presence moving β€” without spending another evening drafting in the app.

L
@lumenstudio
X Β· 3-tweet thread
Scheduled

Hot take: shipping daily beats shipping perfectly. Here's the proof… 🧡

Mon Β· 9:00 AM Smart Slot
POST /v1/posts
{
  "content": "Hot take… 🧡",
  "networks": ["x"],
  "schedule_at": "Mon 9:00"
}
βœ“ scheduled 200 OK Β· 142ms
  • Skip the daily X ritual
  • Multi-tweet threads in one composer
  • Impressions you can actually track
  • Crosspost without copy-paste
β€” What you get

Built for the way you use X.

Schedule tweets weeks ahead, build threads in one composer, and see what actually moved the needle β€” all without opening X.

01 β€” Schedule

Queue today. Forget tomorrow.

Stack two weeks of takes, threads, and replies in one sitting and step out of the daily refresh loop. Zilfu publishes the moment you've planned for, even when you're deep in something else.

Get started free β†’
Up next this week 12 scheduled
Tue Β· 6:15 PM+ photo

Sneak peek of what we shipped this week

Photo
Wed Β· 12:00 PM280 chars

Quick update on the new redesign β€” what we kept, what we tossed

Tweet
Fri Β· 8:00 PM28s clip

Watch what happens when agents ship code on their own

Video
02 β€” Compose

Write once. Post everywhere.

Compose one post, pick your destinations, and Zilfu publishes everywhere at once. X, Threads, Instagram, Facebook, LinkedIn, TikTok, Pinterest, and Bluesky β€” all from a single composer. No copy-paste, no tab-juggling.

Get started free β†’
New post Saved Β· just now

Hot take: shipping daily beats shipping perfectly. Here's the proofβ€¦βœ¨

Publishing to
𝕏 @lumenstudio X
@ @lumenstudio Threads
IG @lumenstudio Instagram
Li Lumen Studio LinkedIn
03 β€” Measure

Track every impression, repost, bookmark.

Impressions, reposts, replies, quotes, bookmarks, and likes β€” broken down per tweet and thread. Refreshed every four hours, ready when you open your laptop. No CSV exports. No spreadsheets.

Get started free β†’
Impressions 38.4K +41%
Reposts 412 +22%
Bookmarks +189 +8%
Tweet impressions Β· last 30 days X
β€” How it works

From zero to scheduled in under a minute.

Three steps. Then the rest of your week takes care of itself.

1

Connect in one click.

Sign in with X, pick the account you want Zilfu to manage, and grant the standard permissions. That's the whole setup β€” OAuth 2.0 with PKCE, no password ever shared.

2

Drop in your tweet.

Compose in the dashboard, build thread replies inline, or trigger from Zapier, n8n, your CMS, your AI agent β€” anything that talks HTTP.

3

We publish. You watch.

Posts go out at the right time. Impressions, reposts, and bookmarks roll in every four hours. Webhooks fire on publish, fail, and reply.

β€” For developers

Automate with APIs.

Your CMS, your AI agent, your automation tool β€” anything that talks HTTP can ship a tweet to Zilfu. Threads, replies, webhooks, and an MCP server included.

142ms
# Schedule a tweet to your X account.
curl -X POST https://zilfu.app/api/posts \
  -H "Authorization: Bearer sk_live_xxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Hot take: shipping daily beats shipping perfectly 🧡",
    "networks": ["x"],
    "schedule_at": "2026-04-23T18:15:00Z"
  }'
# Add Zilfu's MCP server to Claude, Cursor, or any agent.
{
  "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>"
      }
    }
  }
}
βœ“ Response Β· 200 OK
{
  "id": "post_8aB3xY9k",
  "status": "scheduled",
  "scheduled_at": "2026-04-23T18:15:00Z",
  "networks": [
    { "name": "x", "status": "queued" }
  ]
}
No upgrade needed

Full API on the free plan. Same endpoints, no surprises.

No servers to run

Hosted MCP server β€” drop the URL into Claude, Cursor, or any agent.

Real events

Webhooks fire when tweets publish, fail, or get a reply.

β€” FAQ

X, asked and answered.

No β€” any standard X account works. Zilfu connects through X's official OAuth 2.0 flow with PKCE, so your password never leaves X.

Yes β€” by spinning up a workspace for each account. Every workspace stays isolated with its own queue and scheduling slots, and you switch between them in one click. The Free plan includes 2 workspaces; paid plans go up to unlimited.

Yes. Build the whole thread in one composer β€” root tweet plus as many replies as you need β€” and Zilfu publishes them as a single linked conversation. Photos and video can be attached to any tweet in the chain.

Yes. Scheduled tweets sit in your queue until publish time β€” edit the text, swap the media, change the time, or cancel entirely whenever you like.

Impressions, likes, reposts, replies, quotes, and bookmarks β€” pulled from X every four hours and rolled up per tweet, per thread, and per topic. Impressions is the default headline metric. Note: a few of the deeper organic metrics depend on the API access tier on the connected X account; the public counts are always available.

We never see your password β€” Zilfu connects through X's official OAuth 2.0 flow with PKCE and only requests the scopes needed to publish on your behalf and read your posts and engagement. You can revoke access from your X settings β†’ Connected accounts at any time.

Schedule once. Show up daily.

Connect your X account in one click and let your queue do the rest. Free forever β€” no credit card, no commitments.

Connect X free β†’