
Hootsuite
io.github.asklokeshPublished by GitHub account asklokeshv0.1.0Updated Oct 24, 2026
MCP server for Hootsuite API integration
Overview
A local MCP server that connects an assistant to the Hootsuite social media management API for social media tasks.
- What you can do
- Connect an assistant to the Hootsuite social media management platform through its API, described as comprehensive API coverage with async support, rate limiting, retry logic and error handling. The manifest lists no individual tools, so the exact operations available are not documented here.
- When to use it
- Consider it when you want an assistant to work with Hootsuite social media management data and you already have Hootsuite API access.
- Requirements
- Runs locally as a stdio process, installed from PyPI with uvx or pip. Requires a Hootsuite API key in the HOOTSUITE_API_KEY environment variable and, optionally, an API URL in HOOTSUITE_API_URL. Network access to the Hootsuite API is needed.
Installation
In SourceWeft
- Open Hootsuite in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Hootsuite MCP Server
Hootsuite Mcp Server
[GitHub stars] [GitHub forks] [GitHub watchers]
A Model Context Protocol (MCP) server for integrating Hootsuite with GenAI applications.
Overview
Social media management platform
Features
- Comprehensive Hootsuite API coverage
- Multiple authentication methods
- Enterprise-ready with rate limiting
- Full error handling and retry logic
- Async support for better performance
Installation
Or install from source:
Configuration
Create a .env file or set environment variables according to Hootsuite API requirements.
Quick Start
License
MIT License - see LICENSE file for details
Source: README.md at commit 37c7a82
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.