# Hootsuite (Social OS) ID: 15-hootsuite Page: https://gtmmcps.com/tools/15-hootsuite JSON: https://gtmmcps.com/data/tools/15-hootsuite.json Documentation references: https://gtmmcps.com/docs/15-hootsuite/ Category: Community & Dark Social MCP support: official Testing: RESEARCHED API access: paid Last checked: 2026-09-07 Endpoint check: not-probed; date: Not recorded A social-media management suite split into four named products, each with its own MCP server: Perch for content creation, planning and publishing, Nest for social inbox and customer care, Lumen for listening and insights, and Parliament for employee advocacy. ## MCP links - https://mcp.hootsuite.com/perch - https://mcp.hootsuite.com/nest - https://mcp.hootsuite.com/lumen - https://mcp.hootsuite.com/parliament - https://www.hootsuite.com/integrations/mcp ## Sources - https://www.hootsuite.com/integrations/mcp - https://www.hootsuite.com/plans - https://mcp.hootsuite.com/perch ## Research notes Verified 2026-09-07: POST of an MCP initialize to https://mcp.hootsuite.com/perch returned HTTP 401 with {"error":"no_suitable_provider","error_description":"No OAuth provider is configured to handle this request"}, confirming a live OAuth-gated server; the other three addresses are printed on the same vendor page and follow the same pattern. FOUR SCOPED SERVERS, NOT ONE, which is the same governance pattern Zoho CRM uses in 06-revops-infra.md and is worth naming as an emerging design: an operator connects only the surface a task needs, so a listening agent never holds publishing rights. CROSS-FILE CORRECTION FLAGGED, NOT MADE: the Lumen server is the Talkwalker listening product, and this file already carries a separate "Talkwalker (Lumen by Talkwalker)" entry. Those two entries now describe overlapping products under two vendor names and should be reconciled by the directory maintainer, either as a declared cross-listing in INDEX.md or as a merge; that decision is editorial and is not made here. The vendor states setup is "no technical setup required" for ChatGPT and Claude via pre-built connectors, with a manual server-URL path for Gemini and Copilot. Publishing and inbox write access are both in scope, so an agent connected to Perch or Nest can post publicly and reply to customers. 2026-09-07: All four documented Social OS servers answered 401 to an MCP initialize POST: https://mcp.hootsuite.com/perch, /nest, /lumen and /parliament (https://mcp.hootsuite.com/perch). ## Named capabilities Tool names below are reported by sources. Their presence is not a successful call. ## CLI evidence Status: none-found Read current vendor documentation before configuring or running commands.