Majika Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
MCP
Amp
Schedule X from Amp then you approve
Connect Amp to Majika over MCP with a programmatic token. Draft and schedule X posts in natural language while you review and approve on the calendar or kanban.
Connect Majika
Use native MCP tools or install the openquok-core skill — Amp discovers commands through MCP or SKILL.md.
Chat
Queue my launch announcement on Facebook, Instagram, and Threads — attach the hero image and set it for tomorrow at 9am.
On it — scheduling across your workspace.
- 1. Reading openquok-core skills or openquok MCP tool definitions
- 2. integrationList → 3 channels matched
- 3. Uploading hero-image.png
- 4. Creating scheduled drafts
Queued for tomorrow:
- • Facebook — My Brand Page · 9:00 AM
- • Instagram — @mybrand · 9:00 AM
- • Threads — @mybrand · 9:00 AM
Prompt from your terminal and IDE
One prompt,X on your calendar
Describe what to publish on X in Amp. Agent lists your connected channels, attaches media, and queues drafts for the time you pick — you approve on the calendar before anything goes live.
Built for X with Amp
Who schedules X with Amp?
Creators & founders
Stay visible on X without living in the app. Queue tweets, images, and thread chains on the calendar while you ship product. Ask Amp to draft X posts in chat.
Social managers
Batch a week of posts in one sitting, control reply settings per tweet, and track engagement alongside your other channels. Batch X drafts through Amp and review before publish.
Developers & agents
Pipe X drafts from your backend via the public API or CLI — including thread replies under providerSettings — while you keep approval control in the dashboard. Let Amp queue X content.
How it works
Five steps,to Amp + Majika
Minimal setup
stay in your editor or terminalconnect onceschedule without switching apps
Amp is built for focused sessions where you already ship work — paste one MCP config, and Majika tools live inside that flow. List channels, draft posts, and queue schedules, without opening another dashboard or chat app.
First prompt to try
List my connected social media accountsProgrammatic access token
Use this token to call the Public API from CI pipelines and other automated scripts. Tokens start with opo_….
No token on screen — generate one below. Existing tokens stay hidden for security.
Example token placeholder: opo_your_programmatic_token
Chat
List my connected social media accounts
integrationList
Connected channels in your workspace:
- • Facebook — My Brand Page
- • Instagram — @mybrand (Business)
- • Threads — @mybrand
Create Post
Connected channels
Editing a Specific Network
67 / 280
Follow-up comments
Reply
46/280
Delay
09:00 + 300s ≈ 09:05:00
Majika Settings
Post into an X community when the URL is valid.
Add a thread finisher
14/280
Post Preview
Majika @Majika
Jun 12, 9:00 AM
Ship the launch tweet, then queue one follow-up reply with a delay.
Scheduled thread replies
- MajikaAfter 5 min
Thread reply publishes after your chosen delay
- MajikaThread finisher
That's a wrap — thanks for reading.
Thread momentum
Set who can replyqueue thread replieswiden reach with plugs
A strong tweet deserves a conversation — not another tab open on X. Set reply rules and disclosure labels when you schedule, queue timed thread replies before the post goes live, and use internal plugs so your other connected X accounts repost automatically and more followers see the thread.
Example prompts
Schedule a X post for tomorrow at 9am — move to review with a note to check the CTA before it goes liveInsights
See what resonates on X track impressions and engagementand iterate
Track likes, replies, reposts, quotes, and impressions from connected X profiles inside Majika analytics — so you can schedule more of what already works.
Example prompts
What performed best on my X account over the last 30 days?
Break down likes, comments, and shares for post <id>Targeted channels
Overview
Impressions
10.4%
9,432
Likes
8.6%
681
Replies
5.8%
218
Reposts
4.2%
153
Quotes
3.0%
75
Chat
Queue my launch announcement on Facebook, Instagram, and Threads — attach the hero image and set it for tomorrow at 9am.
On it — scheduling across your workspace.
- 1. Reading openquok-core skills or openquok MCP tool definitions
- 2. integrationList → 3 channels matched
- 3. Uploading hero-image.png
- 4. Creating scheduled drafts
Queued for tomorrow:
- • Facebook — My Brand Page · 9:00 AM
- • Instagram — @mybrand · 9:00 AM
- • Threads — @mybrand · 9:00 AM
What performed best on my channels over the last 7 days? Break down impressions and engagement.
Pulled platform analytics (7d)
- Top post: 12.4k impressions, 842 reactions — carousel on product tips.
- Facebook Page leads with +24% impressions vs last week.
Compare that post on TikTok vs Instagram Reels.
TikTok: 48k views, 2.1k likes. IG Reel: 31k plays, 312 saves. TikTok wins reach; IG leads on saves.
Scale what works
when a format hits, scale by adding workspaces and parallel sessions
Spot a winner in analytics, then clone more dedicated workspaces for the next client or brand while parallel Amp sessions queue posts and pull metrics — multi-workspace isolation keeps credentials and channels from mixing as you scale.
Parallel sessions
# Workspace A — launch (client brand)
Queue my launch thread for Tue 9am across Facebook and Instagram
# Workspace B — another client (switch workspace + token)
List draft posts waiting for review in this workspace
# Same workspace — metrics in parallel
What performed best on my channels over the last 7 days?Playbooks & Building Blocks Directories
X viral formats
Mix X-focused playbooks, skills, and MCP servers—then tailor them to your Amp workflow.
comparisons
MCP-native scheduling, not another dashboard
Most social scheduler SaaS keeps you in a browser tab. Majika is built for X from Amp in your editor and terminal
Typical social scheduler SaaS
- Copy posts between your AI session and a separate scheduling tool
- Siloed API keys and workflows that do not compose with your agent stack
- Custom integrations you maintain for every tool and channel
- Locked to one vendor's models or automation layer
- Autopilot publishing with no human checkpoint
Majika + Amp
- Stay in your terminal and IDE — Schedule from Amp in one session
- Connect over MCP — credentials stay in your workspace
- Built-in MCP tools that upload media, and schedule with structured responses
- Works with any model Amp supports — Claude, GPT, Gemini, and more
- Every post lands as draft or scheduled — you approve before anything goes live
By channel
More channels for Amp
Choose a channel for platform-specific workflows, examples, and FAQs.
Page feed posts, MP4 Reels, and link-preview cards — built for Facebook Pages, not personal profiles.
Threads
Soon500-character posts with media and scheduled follow-up reply chains — conversation-first text on Meta Threads.
Feed posts, Reels, carousels, and Stories — with trial Reels, collaborator tags, and follow-up comments.
YouTube
Long-form MP4 uploads and vertical Shorts — title, privacy, tags, and custom thumbnail per video.
TikTok
Vertical video and photo carousels — direct publish or queue to your TikTok inbox to add trending audio.
B2B thought leadership on profile and company Page — scheduled, reviewed, and ready when buyers research you.
Frequently asked questions
Amp + X,answered
What Amp MCP is, how to connect Majika, scheduling X posts, human approval, and example prompts.
Majika exposes X scheduling tools over MCP so Amp can list your connected account, read platform limits, and draft or schedule X posts in natural language — you approve what publishes in your Majika workspace.
No — Amp connects over MCP with an opo_ token and built-in tools, which is the fastest path for editor and terminal workflows. The openquok-core skill on agent hosts like OpenClaw and Hermes is worth it when you want deeper customization: compose Majika with other skills, run parallel sessions, automate from shell scripts, and scale into workflows MCP alone does not cover yet.
OpenClaw and Hermes fit always-on scheduling from Telegram, Discord, or Slack — persistent memory and parallel sessions across channels. Amp fits when Majika should live inside your editor or terminal: native MCP tool calls, focused sessions, and async tasks with clear specs. Choose Amp when you already work there; choose an agent host when messaging-first scale matters. Many teams use both.
Create an OAuth app in Developers → Apps, generate an opo_ token under Developers → Access, then paste the MCP config with either an Authorization header or the API key in the URL path.
Start a fresh session in your client and ask: List my connected social media accounts. The agent should call integrationList and return your workspace channels.
Connect your X account in the Majika web app, add Majika MCP to Amp with an opo_ token, and ask in natural language to draft and schedule. Every post lands as a draft or scheduled item until you approve on the calendar or kanban.
Read the Amp setup guide
Step-by-step instructions for connecting Majika to Amp — install commands, auth patterns, and configuration snippets.
Start free. Publish with confidence.
Connect your agent, review every draft, and schedule posts across channels before anything goes live.