Before you start
You need a personal access token. Create one under Settings → API tokens — it's shown once, so copy it somewhere safe.
The MCP server endpoint is:
https://zilfu.app/mcp/social-media
Authenticate every connection by sending the token as a Bearer token in the Authorization header. The same token works for both the REST API and the MCP server.
Treat your token like a password. Anyone holding it can act on your account, in every space you belong to. Never commit it to source control or paste it into a shared chat.
Claude Code
From your terminal:
claude mcp add --transport http zilfu \
https://zilfu.app/mcp/social-media \
--header "Authorization: Bearer YOUR_TOKEN"
Start a session with claude and run /mcp — the zilfu server should be listed.
Claude Desktop
Open Settings → Developer → Edit Config and add Zilfu to your mcpServers map. Claude Desktop reaches remote HTTP servers through the mcp-remote proxy:
{
"mcpServers": {
"zilfu": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://zilfu.app/mcp/social-media",
"--header",
"Authorization: Bearer YOUR_TOKEN"
]
}
}
}
Restart Claude Desktop. The Zilfu tools appear in the tools menu of any new conversation.
Cursor
Open Settings → MCP → Add new MCP Server and paste the same JSON shown above for Claude Desktop. Cursor uses the same configuration shape and the same proxy.
Other clients
Any client that speaks MCP can connect. Point it at https://zilfu.app/mcp/social-media over streamable HTTP with an Authorization: Bearer YOUR_TOKEN header. Clients limited to the local stdio transport can reach the server through the mcp-remote proxy, exactly as in the Claude Desktop example.
Check it works
Ask the assistant something concrete:
"List my Zilfu spaces."
It should call list-spaces-tool and come back with the workspaces attached to your account. From there, ask it to draft a post or fill out your weekly schedule.
Troubleshooting
401 Unauthorized — the token is missing, malformed, or revoked. Generate a new one under Settings → API tokens and update the client config.
Tools don't appear — restart the client after editing its config, and check the server name (zilfu) doesn't collide with another entry.
Nothing happens when you ask — confirm the assistant is allowed to call MCP tools. Some clients require enabling tool use per conversation.
"Space not found" or "Account not found" — the ID doesn't exist, or belongs to a space your token can't reach. Ask the assistant to list spaces and accounts first rather than guessing IDs.