Using MakeJust to Post Tweets?

OpenTweet is the posting layer for X (Twitter), built for AI agents, developers, and creators. AI agents post through the MCP server and REST API with no X developer account. Automated accounts run on smart connectors (RSS, GitHub, Stripe). And creators get a full Twitter scheduler: visual calendar, AI content generation, thread scheduling, and an evergreen queue. One tool, whether the one posting is you or your agent.

Yes. OpenTweet has an MCP server (Model Context Protocol) and REST API that lets AI agents post to X. Point Claude Desktop, Claude Code, Cursor, Windsurf, or any MCP-compatible client at the hosted server at https://mcp.opentweet.io/mcp, or install the npm package locally. Your agent gets 36 tools including create_tweet, schedule_tweet, create_thread, batch_schedule, create_article, get_analytics and add_to_evergreen. No X developer account needed.

MCP (Model Context Protocol) is an open standard by Anthropic that lets AI assistants connect to external tools. The OpenTweet MCP server gives your AI agent direct access to post, schedule, and manage your X account through natural conversation. Run it two ways: point your client at the hosted endpoint at https://mcp.opentweet.io/mcp with nothing to install, or install the npm package so it runs locally and your API key never leaves your machine.

OpenTweet has an MCP server (Model Context Protocol) that connects to Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, and any MCP-compatible AI client. Add three lines to your MCP config file with your OpenTweet API key, and your AI assistant gets 36 tools to post tweets, schedule threads, check analytics, and manage your evergreen queue, all through natural conversation.

No. You connect your X account through OpenTweet's dashboard with one click. OpenTweet handles the Twitter API for you: no developer applications, no API key management from X, and setup takes under 2 minutes.

The official X API and XMCP both require an X developer account and pay-per-use API pricing since February 2026: about $0.015 a post, $0.200 when the post contains a link, and $0.005 a read. The $200 Basic and $5,000 Pro tiers were retired to new signups in May 2026. OpenTweet sits on top of all that: you connect your X account with one click, and your agent gets an MCP server, REST API, and CLI with scheduling, threads, analytics, and an evergreen queue already built in, for a flat $11.99 to $49 a month with no meter. No developer application, no OAuth token management, no usage-based bill.

No, and no other tool on a self-serve tier can either. On 23 February 2026 X restricted programmatic replies through POST /2/tweets: an app can only reply when the original author @mentions it or quote-posts it. That applies to the pay-per-use tier too, and only Enterprise access is exempt. OpenTweet posts through the official X API, so the restriction applies to us as well. Threads still work, because a thread is a reply to your own post, which is unaffected.

No. Scheduled and automated posting is allowed under X’s automation rules as long as it goes through the official API on an account you authorized. OpenTweet publishes through the official X API. It does not scrape, it does not drive a logged-in browser session, and it never signs in with your password, which are the behaviours that get accounts suspended.