hootsuite_approve_ messageApprove a post waiting for approval, which lets it publish publicly.
Schedule next week's post to your LinkedIn and X accounts by name, attach an image from a link, see everything going out this month, or approve what is waiting for you.
PopMCPHootsuite
Every endpoint in Hootsuite's published API is a tool: posts, approvals, media, social accounts, members, teams, user provisioning, analytics, Inbox and Amplify. Four more do the jobs that take several calls: scheduling by account name with files attached, uploading a file and waiting until it is ready, reading a long stretch of the calendar, and approving a post by its id.
77 tools in the full catalog: 51 read and 26 write. 34 load by default, and the rest are found with tool search.
hootsuite_approve_ messageApprove a post waiting for approval, which lets it publish publicly.
hootsuite_delete_ messageDelete a scheduled or pending post so it does not go out.
hootsuite_get_ member_ social_ profile_ permissionsA member's permissions on one social account, such as whether they can publish or need approval.
hootsuite_get_ messageOne post by id (from hootsuite_list_messages): state, text, send time, the social account, media, tags, the public postUrl once sent, and sequenceNumber, which approving or rejecting needs.
hootsuite_get_ message_ review_ historyWho approved, rejected, edited or sent a post, and when.
hootsuite_list_ messagesPosts in a time window, sorted by send time: scheduled, sent, failed, rejected and pending approval.
hootsuite_list_ organization_ membersThe member ids in an organization.
hootsuite_list_ organization_ teamsThe teams in an organization, with id and name.
hootsuite_reject_ messageReject a post waiting for approval, with a reason its creator sees.
hootsuite_schedule_ messageSchedule a post to one or more social accounts, one message per account.
hootsuite_get_ teamOne team by id: name, logo, who made it and when.
hootsuite_list_ team_ membersThe member ids in a team.
hootsuite_list_ team_ social_ profilesThe social accounts a team can use.
hootsuite_get_ meWho this connection signed in as: member id, name, email, company, time zone and language.
hootsuite_get_ paid_ ad_ metricsDaily metrics for campaigns, ad sets or ads, for up to 10 ad accounts.
hootsuite_get_ post_ analyticsPublished posts with lifetime metrics, for up to 10 social accounts on one network.
hootsuite_get_ profile_ analyticsDaily metrics for up to 10 social accounts on one network.
hootsuite_list_ my_ ad_ accountsThe ad accounts this member can use in one organization, with ad_account_id, network, currency and whether the API can use it.
hootsuite_list_ my_ organizationsThe Hootsuite organizations this member belongs to, with id and name.
hootsuite_list_ my_ social_ profilesThe social accounts this member can use, with id, network, name, owner, and whether the account needs reconnecting.
hootsuite_list_ paid_ ad_ entitiesCampaigns, ad sets or ads for up to 10 ad accounts.
hootsuite_list_ postsRead posts over any range up to 24 weeks.
hootsuite_review_ postApprove or reject a post waiting for approval, by its id.
hootsuite_schedule_ postSchedule a post by account name, with images or video from links.
hootsuite_upload_ mediaPut one image or video into Hootsuite and wait until it is ready.
hootsuite_approve_ commentApprove a comment waiting for approval, which lets it publish publicly.
hootsuite_get_ commentOne comment that went through the approval process, by id.
hootsuite_get_ memberOne member by id.
hootsuite_get_ social_ profileOne social account by socialProfileId.
hootsuite_list_ social_ profile_ teamsWhich teams can use a social account: team ids, for hootsuite_get_team.
hootsuite_list_ social_ profilesThe social accounts this token can reach, with id, type, socialNetworkUsername, owner, ownerId and isReauthRequired (1 means it needs reconnecting in Hootsuite).
hootsuite_reject_ commentReject a comment waiting for approval, with a reason its creator sees.
hootsuite_create_ media_ upload_ urlFirst step of a manual upload: gives an id and an uploadUrl to PUT the file to, with the exact size and type given here.
hootsuite_get_ media_ statusWhether an upload has finished processing.
hootsuite_inbox_ get_ agent_ availabilityInbox 2.0: how many agents are available or away.
hootsuite_inbox_ get_ contacts_ waitingInbox 2.0: how many contacts are waiting for a reply now.
hootsuite_inbox_ get_ conversation_ response_ timeInbox 2.0: average seconds to reply, after the first reply.
hootsuite_inbox_ get_ first_ response_ timeInbox 2.0: average seconds to the first reply.
hootsuite_inbox_ get_ handle_ timeInbox 2.0: average seconds an agent handles a conversation.
hootsuite_inbox_ get_ inbound_ message_ volumeInbox 2.0: how many messages came in.
hootsuite_inbox_ get_ longest_ wait_ timeInbox 2.0: the longest time in seconds a contact is waiting for a reply now.
hootsuite_inbox_ get_ outbound_ message_ volumeInbox 2.0: how many messages went out.
hootsuite_inbox_ get_ proactive_ message_ statusInbox 2.0: how many of a proactive message's sends succeeded, failed or are pending.
hootsuite_inbox_ get_ proactive_ message_ status_ detailInbox 2.0: the details of a proactive message's sends in one status, including failure reasons.
hootsuite_inbox_ get_ resolved_ with_ one_ replyInbox 2.0: how many messages were resolved with at least one reply.
hootsuite_inbox_ list_ locked_ conversationsInbox 2.0: conversations and the agent holding each one.
hootsuite_inbox_ list_ online_ agentsInbox 2.0: the agents online right now.
hootsuite_inbox_ send_ proactive_ messageInbox 2.0: send a WhatsApp message to a customer, which reaches them right away.
hootsuite_inbox_ set_ contact_ attributesInbox 2.0: update the attributes shown on a contact, such as a CRM status.
hootsuite_inbox_ update_ bot_ conversationInbox 2.0 virtual agent: reply in a conversation, apply topics, tags or notes, set contact attributes, or hand off or resolve it.
hootsuite_inbox_ upload_ bot_ attachmentInbox 2.0 virtual agent: upload a file to send in a conversation, then name it in hootsuite_inbox_update_bot_conversation.
hootsuite_scim_ create_ groupCreate a team the SCIM 2.0 way.
hootsuite_scim_ create_ userProvision a Hootsuite user the SCIM 2.0 way, for identity systems.
hootsuite_scim_ get_ groupOne team the SCIM 2.0 way.
hootsuite_scim_ get_ userOne user the SCIM 2.0 way.
hootsuite_scim_ list_ groupsList teams the SCIM 2.0 way.
hootsuite_scim_ list_ resource_ typesWhat the SCIM 2.0 service supports.
hootsuite_scim_ list_ usersList users the SCIM 2.0 way.
hootsuite_scim_ replace_ groupReplace a team the SCIM 2.0 way: members left out are removed.
hootsuite_scim_ replace_ userReplace an user the SCIM 2.0 way: fields left out are cleared.
hootsuite_scim_ update_ groupChange some of a team's attributes or members the SCIM 2.0 way.
hootsuite_scim_ update_ userChange some of an user's attributes the SCIM 2.0 way.
hootsuite_get_ organization_ member_ permissionsA member's permissions in an organization.
hootsuite_list_ organization_ member_ social_ profilesThe organization's social accounts a member can use.
hootsuite_list_ organization_ member_ teamsThe teams a member belongs to in an organization.
hootsuite_remove_ organization_ memberRemove a person from an organization, which ends their access to it.
hootsuite_add_ team_ memberAdd a member to a team, which gives them access to the team's social accounts.
hootsuite_amplify_ create_ messageHootsuite Amplify: create a post for employees to share.
hootsuite_amplify_ create_ topicHootsuite Amplify: create a topic in the member's organization.
hootsuite_amplify_ decode_ utm_ member_ idsHootsuite Amplify: turn the obfuscated member ids in tracked links back into member ids.
hootsuite_amplify_ get_ meHootsuite Amplify: the signed-in member.
hootsuite_amplify_ list_ my_ organizationsHootsuite Amplify: the member's organizations.
hootsuite_amplify_ list_ topicsHootsuite Amplify: the topics available to the member.
hootsuite_create_ teamCreate a team in an organization.
hootsuite_get_ team_ member_ permissionsA member's permissions in a team.
hootsuite_create_ memberCreate a member in an organization.
hootsuite_list_ member_ organizationsThe organization ids a member belongs to.
Authorize once, then an endpoint your client signs into. Nothing to deploy, and nothing to install on the Hootsuite side.
Open Hootsuite in PopMCP, click Connect Hootsuite, sign in and approve. There is no developer app, callback URL or secret to set up. Analytics and Inbox ask for more, because Hootsuite only opens them to your own app: its Client ID and secret go under More options.
your-hootsuite-valueyour-hootsuite-value••••••••••••3f7aReading changes nothing, and what the AI can see follows your permissions in Hootsuite. Scheduling, approving, deleting and every other change waits until an owner or admin allows write actions in PopMCP, and new connections start read-only. Scheduled posts publish publicly at their time, so the AI is told to confirm with you first.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Hootsuite credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
Schedule "We are hiring in Berlin" to our LinkedIn company page and X account for Tuesday at 9am Berlin time, with the image at this link
hootsuite_schedule_postok
Then just ask for the work
“Schedule "We are hiring in Berlin" to our LinkedIn company page and X account for Tuesday at 9am Berlin time, with the image at this link”
“What is going out on our social accounts in the next two months, by account?”
“Show me the posts waiting for my approval, then approve the one about the product launch”
“Which of our social accounts need reconnecting, and which teams can use each one?”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting Hootsuite behind an AI client.
Not to connect. Click Connect Hootsuite, sign in and approve. PopMCP is already registered with Hootsuite, so there is no app, secret or callback URL. You only need your own app for Analytics or Inbox.
Hootsuite decides this. Its Analytics API needs the Advanced Analytics add-on and an app with the analytics:read scope, which a normal sign-in cannot ask for. Its Inbox API answers only an Org App that Hootsuite has linked to your organization. Both connect under More options, with your own app's Client ID and secret and your Member ID or Organization ID.
New connections start read-only, so nothing can be scheduled until an owner or admin allows write actions in PopMCP. After that, a scheduled post goes out publicly at its time, so the AI is told to confirm the text, accounts and time with you first. If your account needs approval, the post waits for it, as it does in Hootsuite.
No. Hootsuite's API does not publish to those networks, so the connector says so and sends nothing. Pinterest works, but Hootsuite wants it scheduled on its own rather than bundled with other accounts.
Give the AI a public link. PopMCP fetches the file, up to 50 MB, uploads it to Hootsuite and waits until Hootsuite has processed it. If a video is still processing, nothing is scheduled and the AI gets the file's id to try again with, so you never get a post missing its video.
A sign-in is you, so it reaches what you can reach in Hootsuite, across your organizations and personal accounts. The AI lists your social accounts and organizations and uses the ones you name. An Org App connection is locked to its one organization, and a request naming another is refused.
Hootsuite allows 20 requests a second and 100,000 calls a day for each API client. When a limit is reached, the AI is told to wait and try again.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect Hootsuite in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Hootsuite on the consent screen. The Hootsuite tools are then available in that session, and no Hootsuite credential is stored on your machine.
Loading 77 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 34-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
A tool is something your AI calls, and there are 77 here. A trigger is something PopMCP watches for you: 5 Hootsuite events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Hootsuite.
Launch a hosted MCP endpoint for Hootsuite, keep tool access under control, and start testing real workflow prompts right away.