Install openquok-core on OpenClaw, Hermes, Grok Bot, Dots, Meta Muse, ThinkRail, Manus, or another skill host. Or connect OpenQuok in Cursor, Claude Code, Codex, Grok Build, and other MCP clients. Schedule posts from chat. You approve what goes live.
Message your assistant from Telegram, Discord, Slack, Grok Bot, Dots, Meta Muse, ThinkRail, or Manus. Install openquok-core or wire a custom connector. Schedule posts from chat. Pick a host below for setup commands.
Add OpenQuok where you already chat with an AI agent. Use Cursor or Claude Code in the IDE. Use Warp or Grok Build in the terminal. Pick a client below for setup and a copy-paste MCP config.
>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 hostsvsMCP clients match the tool to how you work
Both paths connect to OpenQuok. Use an agent host such as OpenClaw, Hermes, Grok Bot, Dots, Meta Muse, ThinkRail, or Manus for messaging, memory, and parallel sessions. Use an MCP client such as Codex, Claude Code, or Grok Build for focused work in your editor or terminal.
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, Grok Build)
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 hostsvsMCP clients,answered
How OpenClaw, Hermes, Grok Bot, Dots, Meta Muse, ThinkRail, and Manus differ from Cursor, Codex, Claude Code, and Grok Build. When to pick each path. How they connect to OpenQuok. What each costs to run. Why many teams use both.
Choose an agent host to schedule from chat apps, keep memory, and run parallel sessions. Install openquok-core as a SKILL.md you can customize. OpenClaw, Hermes, Grok Bot, Dots, Meta Muse, ThinkRail, Manus, and Gemini Task stay reachable while you are away.
Choose an MCP client when OpenQuok lives in your editor or terminal. You get native tool calls. You do not install a skill. Cursor, Claude Code, and Codex fit focused repo work. Warp and Grok Build fit terminal-first workflows.
OpenQuok bills workspaces, channels, and scheduling. Your LLM and agent app bill separately. OpenClaw, Hermes, and ThinkRail are open source. Grok Bot is included with paid Cursor plans or linked SuperGrok. Dots need eligible ChatGPT Pro or Business Premium. 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. One workspace can serve an OpenClaw skill and a Cursor MCP config at the same time. You keep the same channels and the same approval flow. Message Grok Bot from your phone. Chat in ThinkRail. Or call OpenQuok tools from your IDE.
Agent hosts like OpenClaw, Hermes, Grok Bot, Dots, Meta Muse, ThinkRail, Manus, and Gemini Task are built for long-lived sessions — they remember preferences, past decisions, and project context across conversations. MCP clients like Cursor and Grok Build typically run per-session: productive for focused coding sprints, but you start fresh when you open a new session unless the client stores its own project notes.
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.
Hosts like Grok Bot, Dots, and Manus can use a cloud browser, but that is not a scheduler. Pasting social passwords into chat exposes secrets, while scripted logins risk restrictions or bans. OpenQuok uses official APIs, keeps tokens off the agent VM, and lets you approve every post before publish. See the connect channels guide.
MCP (Model Context Protocol) lets AI assistants connect to the tools you use. Connect OpenQuok in your MCP client and your agent can list channels, read platform rules, and schedule posts without opening the dashboard. Start with MCP getting started or a MCP setup guide.
Yes. OpenQuok offers one 7-day free trial per payment customer so you can run social media accounts on auto-pilot before you subscribe the plan. Create an account and start today — no credit card required. Canceling and resubscribing, or creating another workspace, does not grant a second trial. Plan limits are on Pricing and in the billing limits guide; trial rules are in the Cloud trial guide.