Hootsuite's new how-to walks through using its MCP connectors to run publishing, inbox, and listening from Claude — with one important limit: Claude won't do any of it on its own.
2026-10-02 · by Moe Ameen
Hootsuite published an official guide on October 2, 2026 for creating and publishing social content from inside Claude. The bridge is its Model Context Protocol (MCP) connectors — remote servers you add to Claude as a custom connector, which have been live since Hootsuite's June 24, 2026 "Social OS" relaunch. You set it up in Claude's Settings under Connectors, choose "Add custom connector," paste the remote MCP URL (for example the Perch publishing server at mcp.hootsuite.com/perch), and sign in to your Hootsuite workspace with OAuth. Hootsuite's Social OS lineup has four connectors — Perch for publishing, Nest for the social inbox, Lumen for listening and intelligence, and Parliament for employee advocacy — and the new guide walks through Perch, Nest, and Lumen for creating and publishing content.
Once connected, you can work with your social accounts in plain language. Through Perch, Claude can check your content calendar for gaps, draft posts, and schedule or publish them. Through Nest, it can read inbound messages and draft replies. Through Lumen, it can pull brand mentions, sentiment, and performance numbers into the conversation so you can ask questions about how content is landing. Hootsuite is explicit that Claude follows the same permissions and approval workflows your team already uses in the dashboard, so the connector does not route around your sign-off process.
The limits are the important part. The connectors run only inside a conversation you start — nothing continues after you close the chat. There is no "when a mention comes in, draft a reply" and no "post this thread every Tuesday at 9am"; Claude will not run your queue or respond to mentions on its own. Hootsuite's own guidance is that someone on your team should still review every post before it goes live. The connectors ride on your paid Hootsuite products, and while Claude's free plan allows a single custom connector, running more than one of Hootsuite's connectors at once needs a paid Claude plan — so the workflow typically assumes two active subscriptions. And one thing the connector does not change: Claude drafts captions and schedules assets, but it does not produce the video, carousel, or graphics a post is built from.
The connector is good at telling you the Tuesday slot is empty and drafting the caption that would fill it. What it cannot do is make the thing that goes in the slot — and that gap is usually a missing short, a carousel, or a blog, not a missing sentence. That is the exact seam [Kompozy](/) is built for. Point Kompozy at one source — a long video, a newsletter, a transcript — and it generates the finished assets the connector assumes you already have: persona and avatar [shorts](/glossary/persona-shorts), clipped verticals, brand-exact carousels, quote cards, [blog articles and newsletters](/glossary/output-buckets), and platform-native text, all in one brand voice.
So the practical play today is to let Claude and Hootsuite do the surfacing and the scheduling, and let Kompozy do the producing. Better still, Kompozy does not need you sitting in a chat to ship: its [autopilot](/glossary/autopilot) runs a per-post review pipeline and publishes on a schedule across the eight social platforms plus blog and email on its own, which is the autonomous half the connector explicitly will not do. If your real bottleneck is making enough content rather than clicking schedule, that is where the hours actually go. The step-by-step for the connector itself is in our guide on [posting to social media from Claude with Hootsuite](/how-to/post-to-social-media-from-claude-with-hootsuite).
It is a set of Model Context Protocol (MCP) connectors from Hootsuite's Social OS lineup — Perch for publishing, Nest for the inbox, Lumen for listening, and Parliament for employee advocacy — that you add to Claude as a custom connector and authorize with your Hootsuite workspace. Hootsuite's new guide focuses on Perch, Nest, and Lumen for content creation and publishing. Once connected, you can draft, schedule, and publish posts, triage messages, and pull analytics from inside a Claude conversation.
Not on its own. The connectors run only inside a conversation you start, so Claude will publish or schedule when you ask it to during a chat, but it will not run your content queue or reply to mentions autonomously, and nothing continues after you close the window. Hootsuite also recommends a human review every post before it goes live.
You need paid Hootsuite products (Perch, Nest, Lumen). On the Claude side, a free plan allows one custom connector, but running more than one of Hootsuite's connectors at the same time requires a paid Claude plan. Setup is done in Claude's Settings under Connectors by pasting the remote MCP URL and signing in to Hootsuite with OAuth.
No. Claude can draft text and captions and schedule assets through the connector, but it does not generate the video, carousels, infographics, or branded graphics a post is built from. Producing those assets is a separate step, which is the gap a generation engine like Kompozy fills.