OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
Connect Amp to OpenQuok over MCP with a programmatic token. Draft and schedule X posts in natural language while you review and approve on the calendar or kanban.
Use native MCP tools or install the openquok-core skill — Amp discovers commands through MCP or SKILL.md.
On it — scheduling across your workspace.
Queued for tomorrow:
Prompt from your terminal and IDE
Describe what to publish on X in Amp. The 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
Stay visible on X without living in the app. Ask your agent to schedule tweets and threads while you ship product. Ask Amp to draft X posts in chat.
Batch a week of X posts. Control reply settings per tweet. Track engagement with your other channels. Batch X drafts through Amp and review before publish.
Pipe X drafts from your backend via the public API, CLI, or MCP. Configure thread replies and reply settings per post. Let Amp queue X content.
Minimal setup
Amp is built for focused sessions where you already ship work. Paste one MCP config. OpenQuok tools live inside that flow. List channels, draft posts, and queue schedules. You do not open another dashboard or chat app.
First prompt to try
List my connected social media accountsUse this token to call the Public API from CI pipelines and other automated scripts. Tokens start with opo_….
Example token placeholder: opo_your_programmatic_token
integrationList
Connected channels in your workspace:
Sample channels
These chips set format and character limits. They are not your accounts.
Workspace tools. Sign in or sign up to use your library, Photo Editor, and signatures.
75 / 280
Ship the company launch post — a personal profile can repost after publish.
Thread reply publishes after your chosen delay
Post editor
A strong tweet deserves a conversation. You do not need another tab open on X. Add follow-up replies in the composer with delays. Preview text and media before you schedule. Chain the full thread from one draft.
Example prompts
Schedule a X post for tomorrow at 9am — move to review with a note to check the CTA before it goes liveInsights
Track likes, replies, reposts, quotes, and impressions from connected X profiles inside OpenQuok analytics. Then 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>On it — scheduling across your workspace.
Queued for tomorrow:
Pulled platform analytics (7d)
Scale what works
Spot a winner in analytics. Clone more dedicated workspaces for the next client or brand. 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
Mix X-focused playbooks, skills, and MCP servers—then tailor them to your Amp workflow.
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
Browse every X building block.
comparisons
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for X from Amp in your editor and terminal.
Start with X, then schedule every other network from Amp.
Frequently asked questions
What Amp MCP is, how to connect OpenQuok, scheduling X posts, human approval, and example prompts.
Step-by-step self-host setup for connecting OpenQuok to Amp — install commands, auth patterns, and configuration snippets.
Connect your agent, review every draft, and schedule posts across channels before anything goes live.