Schedule and publish social posts to 12 platforms with first comments, analytics, and listening.
Schedulala teaches any AI agent to run your social media end to end: schedule and publish to 12 platforms — Twitter/X, Instagram, TikTok, LinkedIn, YouTube, Facebook, Threads, Bluesky, Pinterest, Mastodon, Telegram, and Google Business Profile — with first comments on 8 of them through one API field, every post validated against each platform's character limits and media rules before anything publishes, plus analytics, comment triage, and keyword listening from the same conversation. The skill was tested against genuinely cold agents until one installed, connected, and posted with zero human help.
Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, claude.ai, ChatGPT, and anything with a shell. Per-runtime guides: schedulala.com/agents.
CLI · MCP (remote or stdio) · sandbox keys that never publish
Get your API key from schedulala.com, then send this message to your agent:
Read https://schedulala.com/SKILL.md and follow it to set up Schedulala. My API key is sk_live_·········
That's the whole install. The hosted skill walks your agent through the CLI
(npm i -g schedulala, zero tool-schema tokens), or MCP if you prefer typed
tools — and teaches the safe workflow: draft → validate/preview → confirm →
publish → verify, plus the per-platform rules that reject posts (TikTok
privacy + postMode, Instagram media, YouTube titles, character limits, …).
No key yet? A free one takes two minutes (npx schedulala init --email you@example.com) and includes 2 connected accounts and 4 posts to try the
loop. sk_test_ keys simulate everything without publishing.
No install at all — interactive widgets included (post previews, in-chat media upload, analytics cards, calendar, inbox). In Claude: Settings → Connectors → Add custom connector and paste:
https://schedulala.com/api/mcp
OAuth sign-in, no API key handling. Requires a paid Claude plan for custom connectors; the same URL works in ChatGPT. Setup guide: https://schedulala.com/developers/docs/claude-connector
The one-liner above needs no install. If your runtime prefers a local skill:
# skills CLI
npx skills add schedulala/schedulala-agent
# Claude Code plugin marketplace
/plugin marketplace add schedulala/schedulala-agent
# OpenClaw (ClawHub)
openclaw skills install schedulala
# plain git
git clone https://github.com/schedulala/schedulala-agent ~/.claude/skills/schedulala-agent
Pair it with either:
npx -y @schedulala/mcp-server with
SCHEDULALA_API_KEY (Claude Desktop / Claude Code / Cursor config in the
package README), ornpx schedulala init --email you@example.com, then
npx schedulala post "Hello" --platforms twitter --now. Every command
supports --json; exit codes 0–7.skills/schedulala/SKILL.md the skill: install, workflow, rules, decision trees
skills/schedulala/references/ per-platform schemas, media protocol, CLI, widgets
examples/ ready-to-adapt JSON payloads (tiktok, threads, bulk, …)
.claude-plugin/ Claude Code plugin + marketplace manifest
schedulala ·
MCP server on npm: @schedulala/mcp-serverMIT — see LICENSE. The skill documents the Schedulala service, which is a separate commercial product.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @schedulala/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-schedulala-schedulala": {
"command": "npx",
"args": [
"-y",
"@schedulala/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@schedulala/mcp-servernpmcom.schedulala/schedulala works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.