ChatGPT Integration
Two integration paths — MCP in ChatGPT Desktop for the full toolkit, or a Custom GPT Action for the web and mobile. Either way, your social media scheduler lives inside the conversation you're already having.
In ChatGPT Desktop: Settings → Experimental → Model Context Protocol. Paste:
{
"mcpServers": {
"postquickai": {
"command": "npx",
"args": ["-y", "@postquickai/mcp"],
"env": {
"POSTQUICKAI_API_KEY": "pq_live_your_key_here"
}
}
}
}Fully restart ChatGPT Desktop. Verify by asking "list my PostQuickAI content groups" — if the tool fires, you're done.
chatgpt.com/gpts/editor and create a new GPThttps://www.postquick.ai/openapi.jsonSet authentication:
pq_live_your_key_hereSave + publish. Now the GPT can call any of the 40 PostQuickAI endpoints. Share it with your team (each user supplies their own API key for production use).
MCP server, Skills, and REST API are all included with the API add-on on any paid plan.
ChatGPT Desktop supports MCP on macOS and Windows via the same claude_desktop_config-style mcpServers block. The web app and mobile apps don't run MCP locally — for those, use a Custom GPT with an Action.
Open ChatGPT Desktop → Settings → Experimental → Model Context Protocol. Paste the PostQuickAI server block, save, and fully restart ChatGPT Desktop.
Go to chatgpt.com/gpts/editor → Configure → Actions → "Import from URL" and paste https://www.postquick.ai/openapi.json. Set Auth to API Key, Header name `Authorization`, value `Bearer pq_live_your_key`.
MCP runs locally via stdio — works in ChatGPT Desktop, zero server cost. Custom GPT Actions call our REST API directly — works in ChatGPT web/mobile, visible to anyone you share the GPT with. Both use the same API key.
Yes, but each user needs their own PostQuickAI API key. Set auth to "API Key (per-user)" so each conversation prompts for the user's own key. Never hard-code your key into a public GPT.
No. Both paths hit the same PostQuickAI v1 API with the same limits. Basic: 30 req/min, 5k/day. Pro: 120 req/min, 50k/day.
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.
One API key. Two integration paths. Every PostQuickAI tool available from plain English.
Start free trial