OpenQuok now ships as a Grok Bot skill: message the Bot from the desktop or iOS app, let openquok-core draft and queue posts on its cloud computer, and keep every publish behind OpenQuok approval. Same human-in-the-loop as scheduling Dev.to or any other connected channel.
Landing: Grok Bot + OpenQuok. Editor MCP path: OpenQuok for Cursor. Install and auth: Grok Bot agent setup.
CLI + skill, not an always-on MCP socket
OpenQuok is CLI-first: JSON on stdout, workspace uploads, drafts you can reject. A saved skill keeps Grok Bot’s context small — invoke it with / in chat or enable it under Settings → Plugins. You do not leave an MCP connector loaded all day. Editor MCP still fits Cursor or Claude Code; Grok Bot fits always-on chat on a shared machine. Many teams use both.
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 as a skill named openquok-core, or enable it under Settings → Plugins → Yours. Auth with device login on the Bot’s browser, or OPENQUOK_API_KEY. Full walkthrough: Grok Bot agent setup. Assemble recipes first in Skill Builder if you customize per channel.
Pick a slot, then draft — do not publish yet
Give the Bot a window and a channel UUID from openquok integrations:list. Benchmark slots with the Best Time to Post calculator (or a channel page such as TikTok) if you want a starting point — then tell the Bot “draft only.”
Example prompt: list connected accounts, draft a LinkedIn post for tomorrow 9am about a launch, save as draft, do not schedule until you approve.
Human approval stays the gate
CLI creates land as drafts or scheduled items in your workspace. Nothing goes live on autopilot. Review on the calendar or kanban, then approve. Grok Bot handles volume; you handle the copy — same gate as Dev.to tags and series and every other connected channel.
Prefer MCP inside your editor instead? Wire OpenQuok in Cursor with .cursor/mcp.json — see the Cursor MCP setup guide — and keep Grok Bot for parallel desktop teammates on the same workspace.
