The timeline, the mentions and the search come back into the conversation, and the reply goes out from the same place — with the option of having the draft written first, if you add the paid key.
A Twitter/X client for agents, installed from PyPI. The read-and-post calls go straight at the Twitter API with your own OAuth tokens; the drafting and analytics calls route through ShipPost's service and need its key as well.
- Your own profile, your home timeline, and the tweets mentioning you
- Any user's profile, any tweet by id, and recent tweets by search
- Tweets posted, replies sent, tweets liked, users followed
- Your timeline scanned for the posts worth replying to (ShipPost key)
- Replies, single tweets and full threads drafted in your voice (ShipPost key)
- An account analysed, and engagement analytics reported back (ShipPost key)
Pip install shippost-mcp, plus a Twitter OAuth access token in the client config; a refresh token and your app's client id keep it renewing itself. The drafting and analytics calls additionally need a ShipPost API key.
One command plus a key — pip install shippost-mcp, then supply credentials
