Marketing Assistant MCP
Related Servers
Alternatives to Marketing Assistant MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA local-first MCP server for social publishing on X (Twitter), enabling draft management, scheduling, and posting via CLI or AI agents.41 npm5MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows AI agents to post tweets and threads to X (Twitter) via two tools: post_tweet and post_thread.MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server for managing social media posts, currently supporting X (formerly Twitter).37MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models and applications to interact directly with Twitter/X, providing capabilities to create posts, reply to tweets, retrieve user data, and manage account actions.13 npm11MIT
- FlicenseAqualityDmaintenanceModel Context Protocol server that enables LLMs to interact with X.com (formerly Twitter) through OAuth 2.0 authentication, supporting major Post-related operations including reading, writing, searching, and managing posts, likes, retweets, and bookmarks.2133 npm8-
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI agents to interact with Twitter without direct API access, supporting tweet operations, user interactions, and Grok AI integration.142,017 npm32MIT
TDQS
Scored across 33 tools
Each major resource (posts, retweets, DMs) has its own draft lifecycle tools, and the descriptions clearly indicate which resource they apply to. However, the three DM list tools and the two account analytics tools could confuse an agent selecting among them.
The set follows a consistent verb_noun snake_case pattern (create_, list_, get_, update_, approve_, reject_, publish_, etc.). Minor exceptions like be_trendy and analyze_x_posting_times deviate from the pattern but are still readable.
At 33 tools, this server has far more than typical MCP servers. While the tools cover multiple subdomains (posts, retweets, DMs, analytics), the repeated approve/reject/list/get patterns for each draft type inflate the count. Many tools could be consolidated without losing functionality.
The posting, retweet, and DM workflows are well covered, including approval, publishing, and rate-limit management. Minor gaps include the lack of an update_retweet_draft tool and the inability to delete a draft that was never published (only reject). Analytics are comprehensive.