The Model Context Protocol (MCP) is an open standard that lets AI assistants talk directly to your tools. Instead of clicking through a dashboard, you describe what you want in plain language and the assistant carries it out.
Zilfu ships an MCP server, so any MCP-compatible client can read your data, create content, and schedule posts on your behalf — using the same personal access token that powers the REST API.
What you can do
Through an ordinary conversation with your assistant:
- Find your workspaces and accounts — list every space you can publish to, and the social accounts connected to each.
- Create posts across one or many accounts in a single request, as drafts, scheduled for a time, or published immediately.
- Manage your weekly schedule — list, create, and delete recurring posting slots.
- Upload media through a hosted page — request a one-time URL, drop your files in the browser, then carry on the conversation.
- Read your analytics, one account at a time — list every connected account with its collection health, pull a full report for the one you care about, then page through the posts it published, ranked by whatever metric that platform reports.
- Inspect your session — confirm who you're authenticated as before taking action.
Permissions
Every MCP action runs with your workspace permissions. The token acts as you.
In a space where you can create but not publish, creating a post sends it to that workspace's approval queue for a reviewer to sign off, exactly as the app does. If you can publish, posts schedule or go live directly.
Tokens are not scoped. A personal access token carries every permission its owner has, in every space they belong to — there's no read-only or single-space variant. Issue one per client, and revoke it rather than sharing it.
What isn't supported yet
- Editing or deleting posts. The MCP server can create posts but not change them afterwards. The REST API covers both — see the API reference.
- Queueing into the next free slot. Slots can be listed, created, and deleted over MCP, but a post created over MCP takes an explicit time or publishes immediately; it can't be dropped into the next open slot. Use the dashboard for that.
- Connecting accounts. OAuth runs in the browser. Connect accounts in the app first, then MCP can publish to them.