Claude Code Integration
One CLI command unlocks 40+ social media tools + 6 opinionated skills inside Claude Code. Schedule posts, generate content, pull analytics — all without leaving your terminal.
Requires Claude Code and the PostQuickAI API add-on. Free trial available.
Recommended — one CLI command:
claude mcp add postquickai \
-e POSTQUICKAI_API_KEY=pq_live_your_key_here \
-- npx -y @postquickai/mcpThe -- separator matters — everything after it is the command + args. Without it, Claude Code treats the whole string as the binary name and fails to connect.
Verify:
claude mcp listYou should see postquickai: ... ✓ Connected. If it says "Failed to connect", see Troubleshooting below.
Claude Code stores MCP configs in ~/.claude.json under a per-project mcpServers key. Add:
{
"mcpServers": {
"postquickai": {
"command": "npx",
"args": ["-y", "@postquickai/mcp"],
"env": { "POSTQUICKAI_API_KEY": "pq_live_..." }
}
}
}Inside Claude Code:
/plugin marketplace add kodenark/postquickai-agent-skills
/plugin install weekly-content-batchAll 6 skills are available — see /agent-skills for the catalog.
Fully quit Claude Code and reopen it. Window reload isn't enough — MCP servers only load on full restart.
Try these in a fresh conversation:
MCP server, Skills, and REST API are all included with the API add-on on any paid plan.
Run: claude mcp add postquickai -e POSTQUICKAI_API_KEY=pq_live_your_key -- npx -y @postquickai/mcp. The `--` separator is required — everything after it is the command + args. Then restart Claude Code and verify with `claude mcp list`.
Claude Code persists MCP configs in ~/.claude.json under the per-project `mcpServers` key. You can edit it directly as JSON, or use the `claude mcp add` CLI (recommended).
Inside Claude Code, run /plugin marketplace add kodenark/postquickai-agent-skills, then /plugin install <skill-name>. Skills available: schedule-post, weekly-content-batch, analyze-post-performance, onboard-brand, reply-thread, daily-digest.
Yes. Fully exit Claude Code (not just close the window) and reopen it. MCP servers only load at startup.
Run `claude mcp list` — postquickai should show as Connected. Or run /mcp inside Claude Code. If it shows "Failed to connect", check that `command` is `npx` (not the whole string) and your API key is set.
Yes. Each developer installs their own MCP config with their own PostQuickAI API key. The Skills marketplace is a shared GitHub repo so everyone on the team uses the same workflows.
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.
5 minutes of setup. Unlimited creativity from Claude Code.
Start free trial