Go client and MCP for the Hooppy autoposting aggregator
go-hooppy
A Go library, CLI and MCP server for the Russian Hooppy autoposting service: publishing to VK, OK, Telegram and 20+ networks at once
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Publishes posts across several platforms on behalf of the Hooppy token owner
- The token grants access to every page connected in the Hooppy account
Install
Manual install
go install github.com/anatolykoptev/go-hooppy/cmd/hooppy-mcp@latestInstalls the MCP server; the token is set via the HOOPPY_TOKEN variable.
This is third-party code. Review the repository files before installing.
What it does
The package wraps the API of hooppy.ru, a service that itself publishes posts to 20+ networks: VK, Odnoklassniki, Telegram, Instagram, X, TikTok, YouTube, LinkedIn, Dzen, MAX, Threads and others. It ships three ways to use it: a pure Go library with bearer JWT auth and no heavy dependencies, a hooppy CLI command for scripts and manual calls, and hooppy-mcp, an MCP server that gives LLM agents a publishing tool over the protocol directly. The token comes from your Hooppy account and is set via an environment variable or a file at ~/.config/hooppy/token with 600 permissions.
Who it is for. For people already using Hooppy for cross-posting who want to drive publishing from an agent or a Go script.
Good fit when
- You have a Hooppy account with connected pages and need MCP access to it from an agent
- You need a Go library for scripted publishing without heavy dependencies
- You want one API instead of a separate integration for each of the 20+ networks
Not a fit when
- You have no Hooppy account and do not want a third-party posting middleman
- You need to work directly with a specific network's API without an aggregator layer
Example request
Publish the text "New blog post" to all VK and Telegram pages connected in HooppyLimitations
The tool requires an active account and token for the third-party Hooppy service, so it depends on Hooppy's availability and pricing, which the README does not describe. Publishing targets page IDs already connected in Hooppy; connecting the social accounts themselves happens in the Hooppy account, not in this package.
How to disable. Remove the hooppy-mcp binary and the ~/.config/hooppy/token file or the HOOPPY_TOKEN variable.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| HOOPPY_TOKEN required, secret | A bearer JWT token from the Hooppy account, Settings → API token section. |
Security check
- Publishes posts across several platforms on behalf of the Hooppy token owner
- The token grants access to every page connected in the Hooppy account
README in short
The README describes three package parts: a pure Go client library, the hooppy CLI command and the hooppy-mcp server, all sharing bearer JWT auth via the HOOPPY_TOKEN variable or a token file. It shows a Go code example listing connected accounts and publishing a post to several page IDs at once. It states an Apache-2.0 license and installation via go get and go install.
FAQ
Do I need to connect each social network separately in this package?
No, pages are connected once in the Hooppy account, and the package publishes to them by ID through one API.
Is there a ready MCP server or just a library?
Both: a library for Go code and a separate hooppy-mcp binary built specifically for LLM agents.
Related
A skill that strips AI writing tells from text using Wikipedia's list, without adding invented facts
Marketing Skills for AI agents
Marketing Skills for AI Agents
About fifty skills for CRO, copywriting, SEO, analytics, ads and launches, built for coding agents
SendPulse MCP server
SendPulse MCP
SendPulse's official remote MCP server: statistics, campaigns and user data through an agent chat
Yandex Direct MCP generated from a machine-readable schema
yandex-direct-mcp
An MCP server and CLI covering all 113 Yandex Direct API v5 methods generated from WSDL, exposing 9 read tools by default and writes only on demand