OPENQUOK Social media CLI and MCP for AI agents
Install openquok-core on OpenClaw, Hermes, Grok Bot, ThinkRail, or another skill host. Or connect OpenQuok in Cursor, Claude Code, Codex, and other MCP clients. Schedule posts from chat. You approve what goes live.
Install the CLI:
npm install -g @openquok/auto-cliInstall our core skill:
npx skills add https://github.com/Ratimon/openquok-monorepo/tree/main/agent --skill openquok-coreAutonomous Agent
Autonomous agent hosts
Message your assistant from Telegram, Discord, Slack, Grok Bot, or ThinkRail. Install openquok-core. Schedule posts from chat. Pick a host below for setup and skill install commands.
- View integration →
OpenClaw
OpenClaw is a personal AI assistant you run on your own devices. It answers on the channels you already use. You get voice on macOS, iOS, and Android, and a live Canvas you control.
- View integration →
Hermes Agent
Hermes Agent autonomously runs on a laptop, a VPS, or serverless infrastructure. Talk to it from Telegram while it works on a host you never SSH into. Skills load on demand.
- View integration →
Grok Bot
Grok Bot teammates run on a persistent cloud computer with browser, filesystem, and terminal. Message them from macOS, Windows, or iOS. Install openquok-core as a skill. Schedule posts. You approve on OpenQuok.
- View integration →
ThinkRail
ThinkRail is a worktree IDE. Each workspace is its own git branch and cwd. Install openquok-core as a pi skill. Run the CLI in the worktree terminal. Schedule posts. You approve on OpenQuok.
MCP
Native MCP clients
Add OpenQuok where you already chat with an AI agent. Use Cursor or Claude Code in the IDE. Use Warp in the terminal. Pick a client below for setup and a copy-paste MCP config.
- View integration →
Antigravity CLI
Add OpenQuok in ~/.gemini/config/mcp_config.json for agy.
- View integration →
ChatGPT
Add OpenQuok as a custom connector. Paste the MCP URL with your token.
- View integration →
Codex
Add OpenQuok MCP servers in Codex config.toml.
- View integration →
Cursor
Add OpenQuok in .cursor/mcp.json. Use Agent and Composer.
- View integration →
Claude Code
Add OpenQuok with claude mcp add over HTTP.
- View integration →
Claude Cowork
Add OpenQuok with custom connectors or managedMcpServers.
- View integration →
VS Code / Copilot
Add OpenQuok in .vscode/mcp.json for GitHub Copilot.
- View integration →
Devin Desktop
Add OpenQuok in ~/.codeium/mcp_config.json for Devin Local.
- View integration →
Amp
Add OpenQuok with amp mcp add or Amp settings.json.
- View integration →
Warp
Warp is an AI-native terminal with built-in MCP. Ship code, debug deploys, and schedule social from one window.
- View integration →
Muse Code
Add OpenQuok in ~/.config/muse/settings.json with streamable HTTP MCP.
What you unlock
- groupList — list channel groups when channels are organized by customer
- integrationList — list connected channels from chat
- integrationSchema — platform limits and compose rules
- triggerTool — Dev.to tags and organizations, LinkedIn company URLs, and other provider helpers
- schedulePostTool — draft and schedule posts in natural language
Try: List my connected social media accounts
Hosted Agent vs MCP client
agent hosts vs MCP clients match the tool to how you work
Both paths connect to OpenQuok. Use an agent host such as OpenClaw, Hermes, Grok Bot, or ThinkRail for messaging, memory, and parallel sessions. Use an MCP client such as Codex or Claude Code for focused work in your editor or terminal.
Agent hosts (OpenClaw, Hermes, Grok Bot, ThinkRail)
- Schedule from Telegram, Discord, Slack, or WhatsApp
- Persistent memory across sessions
- Parallel sessions across channels
- Messaging, memory, and workflows in one assistant
- Model-agnostic — swap providers freely
MCP clients (Codex, Claude Code, Cursor)
- Work in Cursor, Claude Code, or Codex
- Focused, per-session coding sprints
- Async tasks with clear specs
- Native OpenQuok MCP tool calls
- Ticket- and PR-friendly review flows
Frequently asked questions
Agent hosts vs MCP clients,answered
How OpenClaw, Hermes, Grok Bot, and ThinkRail differ from Cursor, Codex, and Claude Code. When to pick each path. How they connect to OpenQuok. What each costs to run. Why many teams use both.
OpenQuok bills workspaces, channels, and scheduling. Your LLM and agent app bill separately. OpenClaw, Hermes, and ThinkRail are open source. Grok Bot needs SuperGrok or Cursor. Cursor, Claude Code, and Codex use their own plans. OpenQuok MCP needs only your programmatic token.
The MCP host is the app you use, such as Cursor or Claude Desktop. It opens one MCP client session per connected server, including OpenQuok. We call Cursor, Codex, and Claude Code MCP clients because that matches how developers name their tools.
Yes, regardless of path. Agent hosts and MCP clients create drafts or scheduled items in your OpenQuok workspace. Nothing goes live on autopilot — review on the calendar or kanban and approve what should publish.
Browse agent setup guides
Platform-specific guides for OpenClaw, Hermes, Grok Bot, ThinkRail, Cursor, Claude Code, and other agent hosts and MCP clients.
Start free. Publish with confidence.
Connect your agent, review every draft, and schedule posts across channels before anything goes live.