PopMCPContent and social MCP stack for your AI
The blog, the marketing site, the social queue, and the two datasets that say whether any of it worked.
- WordPress
- Webflow
- Buffer
- Google Search Console
- Google Analytics 4
app.popmcp.com/mcpThe 5 connections
The blog, the marketing site and the social queue each have their own login and their own editor, and none of them knows what the others published.
- WordPressAPI credentialTaxonomiesCommentsPagesPosts35tools9triggers
- WebflowAPI credentialCMS itemsE-commerceFormsCustom code117tools25triggers
- BufferAPI credentialPostsChannelsIdeasAccount16tools10triggers
- Google Search ConsoleOAuthSitemapsSitesInspectionSearch analytics10tools8triggers
- Google Analytics 4OAuthAdminReporting21tools7triggers
Across the stack102 read and 97 write operations, 36 API modules199tools59triggers
One question, every connection
The tool names below are the real ones your client calls. Check any chain against the catalog on the integration’s own page.
Publish the announcement and queue it everywhere.
- WordPress
wordpress_list_categorieswordpress_create_post - Webflow
webflow_list_collectionswebflow_create_itemwebflow_publish_items - Buffer
buffer_list_channelsbuffer_create_post
One instruction reaches the blog, the site CMS and every social channel, instead of three editors and a scheduling tab.
Which posts are worth updating rather than replacing?
- Google Search Console
gsc_query_search_analytics - Google Analytics 4
ga4_run_report - WordPress
wordpress_list_postswordpress_search_content - Webflow
webflow_list_items
Declining clicks matched to the actual post or CMS item, across both systems, so the refresh list is a list of URLs you can open.
Fix the pages Google shows but nobody clicks.
- Google Search Console
gsc_query_search_analyticsgsc_inspect_url - Webflow
webflow_list_pageswebflow_get_pagewebflow_update_page - WordPress
wordpress_get_postwordpress_update_post
High impressions and a low click rate turns into a title and description edit on the right platform, in the same turn as the diagnosis.
Turning it on
Nothing to deploy, and nothing to install on the provider side.
- Connect the accounts
One connection per store, property or ad account. Two authorise with OAuth, three take an API credential. Credentials are encrypted at rest and never reach your AI client.
- Tick what each client reaches
Your client signs in to PopMCP with OAuth and gets only the connections you approve. Writes run the moment it calls them, so keep reporting teammates on read-only.
- Register one URL
app.popmcp.com/mcp, once per client. Claude, ChatGPT, Codex and the rest reach the same five connections with the same permissions.
Five connections need Starter or above — the free tier holds two. See what each plan includes.
The other stacks
Same endpoint, same controls. Most teams end up running two or three of them side by side.
Questions about the content and social stack
Can it publish something live by itself?
Yes. Creating a WordPress post, updating a Webflow item and publishing it, and scheduling a Buffer post are all write tools, and they take effect when the AI calls them. Asking for drafts is the safe habit; the publish step is the one worth keeping deliberate.
Does it write the content?
Your AI client does that, the same way it does anywhere else. What this stack adds is the context — what the page currently ranks for, what it earns, what the existing posts already say — and the ability to put the result where it belongs without copy-paste.
Can it manage more than one site?
Yes. Each WordPress site, Webflow site, Buffer organization, Search Console property and GA4 property is a separate connection, so an agency can hold every client's publishing stack side by side under its own workspace.
Connect the content and social stack to your AI
Add WordPress, Webflow, Buffer and the rest with credentials you already own, and get one secure MCP URL for all of them.