OpenQuok ships as a Grok Bot skill. You message the Bot from the desktop or iOS app. The Bot runs openquok-core on its cloud computer. It drafts and queues posts in your workspace. You approve every publish on the calendar or kanban. That gate matches Dev.to, LinkedIn, and every other connected channel.
Start on the OpenQuok for Grok Bot landing page. For editor MCP and Grok 4.7 in Cursor, use How to Post to Social Media with Grok 4.7. This article stays on chat, skills, and the CLI on the Bot computer.
Why Grok Bot fits social scheduling
Grok Bot is a teammate with a browser, filesystem, and terminal on shared cloud infrastructure. You do not keep an MCP connector open all day. You invoke a skill when you need OpenQuok. That keeps context small and fits repeatable jobs: weekly batches, analytics pulls, and per-channel rewrites.
OpenQuok is CLI-first: JSON on stdout, uploads in the workspace, drafts you can reject. The Bot handles volume. You handle copy and timing before anything goes live.
xAI also ships Grok Build, a terminal coding agent with MCP. Grok 4.7 runs in Cursor and on Grok Bot. Grok Build is a third path over HTTP MCP. See Grok Bot vs Grok Build: Pick Your OpenQuok xAI Surface before you pick a surface.
What you need
The Grok Bot app on macOS, Windows, or iOS, with at least one Bot created.
An eligible plan that includes Grok Bot (for example SuperGrok Heavy or an eligible Cursor plan when you sign in with Cursor).
An OpenQuok workspace with at least one social channel connected. On OpenQuok Cloud, connect accounts in the app. You do not register Meta or TikTok developer apps yourself. See Connect channels after sign up.
Permission to run terminal commands on the Bot cloud computer—not on your laptop.
Not sure Grok Bot is the right host? Read Grok Bot vs OpenClaw: Pick Your OpenQuok Social Scheduler Agent before you install.
Create a workspace token (optional)
Grok Bot can sign in with device login in the browser on its cloud computer. That path is the default in the Grok Bot agent setup guide.
Some teams prefer a programmatic token on the Bot shell only:
In OpenQuok, open Account → Settings → Developers → Access.
Create an OAuth app if the UI asks you to.
Generate an
opo_…token. One token maps to one workspace.On the Bot computer, set
export OPENQUOK_API_KEY="opo_…"in the shell profile the Bot uses—not in public chat.Run
openquok auth:statusto confirm the CLI sees the workspace.
Never paste tokens into group chats or screenshots. Rotate the token if it leaks. Device login and API keys both land in the same workspace; only the auth surface changes.
If you schedule from Cursor with MCP instead of Grok Bot, you use the same token in .cursor/mcp.json. Full steps live in How to Post to Social Media with Grok 4.7 and the Cursor MCP setup guide.
CLI and skill, not an always-on MCP socket
OpenQuok exposes MCP for editors such as Cursor. Grok Bot uses the openquok-core skill and the global openquok CLI. You load the skill with / in chat or under Settings → Plugins. You do not leave an MCP server connected all day.
Many teams use both: Grok Bot for always-on chat on a shared machine, and MCP when OpenQuok should live inside a repo session. The approval flow in OpenQuok does not change.
Connect the Bot once, then compose like any channel
Ask the Bot to install the CLI and copy the skill onto durable workspace storage, not your laptop:
npm install -g @openquok/auto-cli@latest
openquok --version
mkdir -p /workspace/openquok-core
curl -fsSL "https://raw.githubusercontent.com/Ratimon/openquok-monorepo/main/agent/skills/openquok-core/SKILL.md" \
-o /workspace/openquok-core/SKILL.mdSave that flow as a skill named openquok-core, or enable it under Settings → Plugins → Yours. Authenticate once with device login when the Bot opens the browser, or with OPENQUOK_API_KEY as above.
Start a new chat after install so the Bot reloads skill instructions. Installing a skill does not upgrade the CLI by itself. Ask the Bot to run npm install -g @openquok/auto-cli@latest when you need a newer openquok --version.
Before you customize per-channel recipes, assemble blocks in the Skill Builder. Export SKILL.md and place it on the Bot computer the same way. More command patterns sit in CLI getting started.
Verify in a new chat
With openquok-core enabled, ask:
List my connected social media accounts.
The Bot should run openquok integrations:list or follow the skill and return channel names and UUIDs. If the list is empty, connect a channel in OpenQuok first, then ask again.
If auth fails, rerun device login or check openquok auth:status on the Bot shell. See the troubleshooting section in the Grok Bot agent setup guide.
Pick a slot, then draft — do not publish yet
Give the Bot a time window and a channel UUID from openquok integrations:list. For a first slot, try the Best Time to Post calculator or a channel page such as TikTok or LinkedIn. Then say draft only in plain language.
Example prompt:
List my connected accounts. Draft a LinkedIn post for tomorrow 9am workspace time about our launch. Save as draft. Do not schedule until I approve.
The CLI and skill can draft, schedule, or publish now. Draft is the safe default until you read the copy in OpenQuok.
Human approval stays the gate
Posts from the CLI land as drafts or scheduled rows in your workspace. Nothing goes live on autopilot. Open the calendar or kanban. Edit tags, media, or timing if you need to. Approve what should publish.
Grok Bot handles repetition. You keep final say—the same gate as Dev.to series, Instagram carousels, and every other network.
If the draft sounds too machine-written, run it through the Humanizer before you approve.
Prompts that work on Grok Bot
Keep prompts short. State the action, the channel, and the time.
Rewrite this note for X and Threads. Stay under each limit. Save drafts for Friday 2pm workspace time. Do not publish.
What performed best on my channels over the last 7 days? Then draft a follow-up for my top channel next Tuesday 9am. Save as draft only.
For multi-step tool recipes in Cursor, see MCP examples. On Grok Bot, the skill maps the same jobs to CLI commands.
When you work in Cursor instead
Cursor Agent calls OpenQuok over MCP. You can pick Grok 4.7 or another model in the same session. That path fits in-repo work, image attachments, and native tool calls.
Grok Bot fits desktop or iOS chat and parallel Bots on one cloud computer. Both use one workspace when you auth the same account. Read How to Post to Social Media with Grok 4.7 for MCP token setup and verify prompts in the editor.
Next steps
Follow the Grok Bot agent setup guide end to end.
Compare hosts in Grok Bot vs OpenClaw if privacy or chat app choice matters.
Review pricing for workspace limits after your first approved draft.
