@helloaigent-dev/publisher
Related Servers
Alternatives to @helloaigent-dev/publisher
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server for managing and querying RSS/news feeds, enabling real-time fetching, searching, and retrieval of feed items.58 npm1MIT
- FlicenseAqualityBmaintenanceAn MCP server for aggregating multi-domain intelligence feeds, performing 80:20 crossover analysis, and publishing structured insights to multiple channels.5-
- AlicenseNot gradedqualityDmaintenanceMCP server for the FreeFeed social network API. Enables reading timelines, posts, comments, and attachments, as well as writing posts, comments, and managing subscriptions.MIT
- AlicenseAqualityBmaintenanceLocal-first MCP server for per-agent key management, generating and using signing keys without external KMS.816 npm1MIT

Paragraph MCPofficial
AlicenseNot gradedqualityAmaintenanceMCP server that connects AI agents to your Paragraph publication, enabling post management, subscriber analytics, and search across posts and publications.48 npm1MIT- AlicenseNot gradedqualityAmaintenanceMCP server for permissioned, structured agent-to-agent communications, enabling agents to coordinate and negotiate through scoped, typed messages with authentication and audit logging.1,004 PyPIMIT
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: feed creation, listing, publishing, event reporting, subscriber data, event log, analytics overview, funnel, and discovery file. There is no overlap or ambiguity between them.
All tools share the hello_aigent_ prefix, which provides strong consistency. However, the second part mixes noun-only names (event_log, subscribers, overview, funnel, discovery_file) with verb_verb_noun patterns (create_feed, list_feeds, report_event), making the convention slightly inconsistent.
Nine tools is well within the ideal 3-15 range and each tool serves a clear, non-redundant purpose for a feed management and analytics domain. The count feels appropriate and not bloated.
The tool set covers the core lifecycle of a feed: creation, publishing, event reporting, and analytics (overview, funnel, subscribers, event log). Minor gaps exist such as feed deletion or metadata update, but these are not critical to the primary publisher workflow.