OpenClaw Integration
The open-source AI agent framework meets social media automation. Text your OpenClaw agent over Signal, Telegram, WhatsApp, or Discord — it schedules posts, generates content, and pulls analytics.
In your OpenClaw character file (characters/my-agent.json), add the MCP block:
{
"name": "my-agent",
"modelProvider": "anthropic",
"plugins": [],
"mcpServers": {
"postquickai": {
"command": "npx",
"args": ["-y", "@postquickai/mcp"],
"env": {
"POSTQUICKAI_API_KEY": "pq_live_your_key_here"
}
}
}
}If you already have other MCP servers configured, add postquickai alongside them.
pnpm start --character=./characters/my-agent.jsonWatch the logs — you'll see [MCP] Connected to postquickai (40 tools) when it's ready.
Whatever messaging adapter you have configured (Telegram, Discord, WhatsApp, Signal):
Run your agent on cron for autonomous workflows — nightly analytics digests, morning content-batch planning, weekly retrospectives. Each task exits cleanly; pair with your system's scheduler (cron, systemd timer, Railway cron).
MCP server, Skills, and REST API are all included with the API add-on on any paid plan.
OpenClaw (formerly Clawdbot) is a free open-source AI agent framework with 150k+ GitHub stars. Agents run locally, connect to messaging platforms (Signal, Telegram, Discord, WhatsApp, X DMs) as their interface, and work with Claude, GPT, Gemini, Grok, or any model you bring.
OpenClaw supports MCP servers natively. Add the PostQuickAI config to your character file's `mcpServers` block, restart the agent, and all 40 social media tools appear automatically alongside your other plugins.
Yes. OpenClaw routes incoming messages to the agent loop, the agent picks tools to call (including PostQuickAI), and responses flow back through the same messaging adapter. Text your agent "schedule a post for tomorrow 9am" from WhatsApp — it works.
Absolutely. OpenClaw agents are designed for multi-plugin workflows. Chain PostQuickAI with the Twitter reader plugin, the news plugin, the image-gen plugin, etc. — one agent, many capabilities.
Only when you want real-time messaging. For purely scheduled work (nightly analytics digests, daily content batches), run the agent as a cron job with `pnpm start --character=./config.json --task=digest` and let it exit after the task completes.
Almost always a config format issue. Make sure command is just npx and args is an array — never put the whole command in one string. Also fully quit and restart your agent after editing config.
MCP and REST API access both require the API add-on on your plan. Enable it at postquick.ai/pricing.
Generate a key at postquick.ai/dashboard/api. Keys start with pq_live_. Put it in the env block of your MCP config.
Basic plan: 30 req/min, 5k/day. Pro plan: 120 req/min, 50k/day. See rate limits in the API docs.
Still stuck? See the developer docs or email support@postquick.ai.
PostQuickAI is agent-native — same API, same MCP server, same skills bundle across every major AI coding agent.
Plug PostQuickAI into OpenClaw and your autonomous agent can post to 8 platforms, analyze performance, and iterate on its own content strategy.
Start free trial