Asking a chatbot for a social post gets you text. You still have to design it, and it still comes out in whatever colours the tool feels like. MCP closes that gap: it is a standard way for an assistant to use an outside tool, and PostPop now speaks it.
Connect it once and PostPop appears inside Claude as four tools. Ask for a post in the middle of a conversation and you get the finished thing back — copy, slides and caption, in your brand’s colours, fonts and language. Same account, same brand kits, same monthly allowance as the Studio.
Settings → API keys → name it Claude and create. It is shown once and never again: only a hash is stored, so we genuinely cannot show it to you later. Copy it now.
The same screen hands you the config block with your key already in it, ready to paste. One button, nothing to assemble by hand.
Claude Desktop → Settings → Developer → Edit config. Paste, save, restart Claude. PostPop shows up in the tools list as four things it can do.
“Make me a PostPop carousel about five signs a roof needs checking before winter.” Claude finds your brand, generates it, and hands back the slides and the caption in about twenty seconds.
Four tools. Claude picks the right one from what you ask — you never call them by name.
Writes and renders a finished post in your brand’s colours, fonts and language. This is the one that spends a post from your monthly allowance, and the tool tells Claude so.
Every post needs a brand kit, so Claude calls this first. Free, and it never creates anything.
Posts used, posts left, and when the month resets — so a batch does not stop halfway through with no warning.
Same idea, same two minutes. One ends as text in a chat window. One ends as a post you can publish.
Now design it yourself · wrong fonts · wrong colours
Rendered · your brand · ready to post
Connect PostPop to Claude in about five minutes.
Get your API key →