Public reads need nothing; search, followers and DMs need your auth_token cookie, and every posting or automation tool then acts as your account. That makes the read and analysis half — unfollower detection, competitor comparison, best time to post — the low-risk place to start, and the auto-follow and auto-comment tools the ones to reach for deliberately.
An X/Twitter toolkit whose MCP server exposes the scraping, analysis and posting surface to any MCP client.
- Scraping — x_get_profile, x_get_tweets, x_search_tweets, x_get_followers, x_get_following, x_get_thread, x_get_replies, x_get_mentions, x_get_likers, x_get_retweeters, x_get_media and x_download_video
- Analysis — x_detect_unfollowers, x_analyze_sentiment, x_best_time_to_post, x_competitor_analysis, x_brand_monitor, x_audience_insights and x_engagement_report
- Actions — x_post_tweet, x_post_thread, x_reply, x_retweet, x_quote_tweet, x_like, x_bookmark, x_follow, x_unfollow, x_send_dm, x_create_poll and x_delete_tweet
- Automation — x_auto_follow, x_follow_engagers, x_smart_unfollow, x_unfollow_non_followers, x_auto_comment, x_auto_retweet and x_auto_like
- AI-assisted — x_analyze_voice, x_generate_tweet, x_summarize_thread, x_rewrite_tweet, x_detect_bots and x_find_influencers
- Monitoring, workflows, personas, Spaces and a follower graph — x_monitor_keyword, x_workflow_create, x_persona_run, x_scrape_space, x_graph_build and more
- A CLI for the same jobs: npx xactions profile, tweets, search, with CSV output
Node and npx. Public reads — a profile, a timeline — work with no account at all. Anything past that needs your own session: put your x.com auth_token cookie in XACTIONS_SESSION_COOKIE. npx xactions mcp-config writes the client config for Claude, Cursor or Windsurf. Since it drives your own session rather than an API, the automation tools act as you.
One command plus a key — npx -y xactions-mcp, then supply credentials