Hootsuite is included for three hosted MCP services: Perch for content and publishing, Nest for social inbox and customer care, and Lumen for listening, sentiment, trends, competitors, and influencer research.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Perch posts, drafts, schedules, media, content-library items, plans, and analytics; Nest inbox conversations, assignments, saved replies, and issue state; Lumen mentions, sentiment, trends, competitors, influencers, and listening insights.
Review cross-network performance and content plans, monitor mentions and sentiment, identify trends or influencers, and summarize or prioritize social inbox conversations within the connected product.
Perch can draft, upload media, prepare, schedule, and publish content; Nest can triage, assign, reply to, and resolve supported inbox conversations. Lumen is presented as an insight and listening surface.
Each remote server uses OAuth 2.0 Hootsuite sign-in to a selected workspace. The user needs an active account and access to the relevant Perch, Nest, or Lumen product; resulting access remains tied to Hootsuite account permissions.
Keep server identity and workspace visible, and preserve human review for public posts and replies. Confirm channel, account, media, schedule, conversation, assignee, saved response, and resolution effect before Perch or Nest writes.
There is no universal Hootsuite MCP endpoint: Perch, Nest, and Lumen have separate URLs and require the corresponding product entitlement. ChatGPT and Claude use connectors; Gemini and Copilot setup may require an IT administrator.
Agent access
Support: Official MCP server
Read scope: Perch reads content plans and performance, Nest reads and summarizes inbox conversations, and Lumen reads listening, sentiment, trend, competitor, influencer, and industry context.
Write scope: Perch drafts, uploads, schedules, and publishes supported social content; Nest assigns, replies to, and resolves supported social-care conversations. No Lumen mutation is claimed by the reviewed source.
Authentication: OAuth 2.0 sign-in to a Hootsuite workspace for the selected remote Perch, Nest, or Lumen server.
Approval boundary: Require human review of public content and replies, and confirm the target social account, channel, media, schedule, conversation, assignee, and resolution state before execution.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Hootsuite ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Hootsuite documents MCP servers for products such as Perch and Lumen, enabling publishing, analytics, listening, and customer-interaction workflows.
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
