X Marketplace Seller MCP
Related Servers
Alternatives to X Marketplace Seller MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to fully automate X/Twitter interactions including searching, posting, engaging, and managing multiple accounts without paid API keys.MIT
- 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 gradedqualityDmaintenanceEnables interaction with X (formerly Twitter), allowing for posting tweets, searching content, managing accounts, and organizing lists.10 npm3MIT
- AlicenseAqualityDmaintenanceEnables AI agents to read, post, search, and engage with Twitter/X content, including AI-powered reply drafting and analytics.17MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to post richly formatted tweets to X (Twitter) with optional images, monetized via Bitcoin Lightning micropayments and secured with OAuth2 PKCE, Nostr identity, and encrypted credential vaulting.3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with X (Twitter) to post tweets, threads, and replies while retrieving tweet metrics and account information. It supports core management tasks like deleting tweets and verifying authentication through the Twitter API.MIT
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes: listing management, negotiation, deal approval, posting, and messaging are separated. The main overlap is draft_buyer_reply vs negotiate_offer, since both run the negotiation engine, but one records a thread and drafts a reply while the other is explicitly a non-recording what-if. Draft vs send boundaries (draft_handoff, send_dm, post_listing) are also clear from descriptions.
The set mostly follows a predictable snake_case verb_noun pattern: create_listing, update_listing, list_listings, draft_buyer_reply, negotiate_offer, propose_deal, approve_deal, post_listing, send_dm. The main deviation is deal_ledger, which is a noun-only read tool rather than verb_noun. The convention is still readable and largely consistent.
Eleven tools are well-scoped for an X marketplace seller workflow, covering listings, negotiation, deal approval, posting, DMs, and ledger review. Each tool appears to earn its place by handling a distinct step, with no obvious filler or redundant surface.
The surface covers the core seller lifecycle: create/update/list listings, draft buyer replies, negotiate offers, propose/approve/complete/cancel deals, post listings, send DMs, draft handoffs, and view the deal ledger. Minor gaps remain, such as no get_listing for a single listing, no permanent delete_listing (only withdrawal), no photo upload (explicitly manual), and no dedicated view of negotiation thread history.