bookmark_tweet
Adds the tweet to bookmarks
LABSCO SUMMARY
Four tools say in their own descriptions that they are simulated or mocked, which is unusually honest and is the first thing to read here.
It would have been easy to leave those unlabelled and let a caller assume the data was real — a simulated 'followers you know' returns something plausible either way. Marking them means an agent has a chance of not building on fiction, and it tells you something good about the rest of the surface. The other labelling worth having is delete_all_bookmarks announcing itself as destructive and irreversible before saying what it does. Set expectations correctly: this is a mixed surface where most tools hit the real API, several do not, and the API tier decides which of the real ones work at all.
What it is
A broad X client covering user lookup and social graph, tweet reading and posting, engagement, bookmarks, timelines, search and trends.
What you get
- Users by screen name, by id, or as a full profile, with followers and following lists.
- Tweets posted with optional media, reply and tags; deleted; read in detail; and created as polls.
- Engagement covered both directions — favourite and unfavourite, bookmark and remove.
- Two timelines kept distinct: the algorithmic For You and the chronological Following.
- search_twitter for queries, get_trends for trending topics, and get_user_mentions for tweets mentioning a user.
- delete_all_bookmarks opens its own description with DESTRUCTIVE AND IRREVERSIBLE and states it deletes them one by one.
- Four tools mark themselves as not real: get_user_followers_you_know and get_highlights_tweets are labelled simulated, vote_on_poll is labelled mocked, and get_user_subscriptions notes it uses a substitute.
- get_bookmarks and delete_all_bookmarks need TWITTER_OAUTH2_USER_ACCESS_TOKEN, a user-scoped OAuth 2.0 token; get_bookmarks also asks for the Basic API tier or higher in its own description.
Requirements
Python 3.10 or higher and X API credentials — TWITTER_API_KEY, TWITTER_API_SECRET, TWITTER_ACCESS_TOKEN, TWITTER_ACCESS_TOKEN_SECRET and TWITTER_BEARER_TOKEN, plus TWITTER_OAUTH2_USER_ACCESS_TOKEN for the bookmark tools. Some tools require a specific API access tier, which they name in their own descriptions.
Setup effort
One command plus a key — pip install x-twitter-mcp, then supply credentials
USE CASES
01
Looking someone up properly
Resolve by screen name or id, read the full profile, and walk the followers and following lists.
02
Posting something and managing it after
Post with media or as a reply, read it back in detail, and delete it if it needs to go.
03
Reading the timeline you actually meant
Choose between the algorithmic For You feed and the chronological Following one — they are separate tools because they are different feeds.
04
Finding out what is being said
Search with a query, read trending topics, and check who has mentioned a user.
05
Keeping track of things to come back to
Bookmark and unbookmark individual tweets and read the list — noting that clearing all of them is marked destructive and irreversible.
06
Engaging without posting
Favourite and unfavourite tweets, which is the lightweight interaction that does not put anything on your own timeline.
24 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_poll_tweet
Create a tweet with a poll
delete_all_bookmarks
DESTRUCTIVE AND IRREVERSIBLE: Permanently deletes ALL bookmarks one by one. This cannot be undone. Always confirm explicitly with the user before calling this tool.
delete_bookmark
Removes the tweet from bookmarks
delete_tweet
Delete a tweet by its ID
favorite_tweet
Favorites a tweet
get_bookmarks
Retrieves the authenticated user's bookmarked tweets. Requires Basic access tier or higher.
get_highlights_tweets
Retrieves highlighted tweets from a user's timeline (simulated)
get_latest_timeline
Get tweets from your home timeline (Following)
get_timeline
Get tweets from your home timeline (For You)
get_trends
Retrieves trending topics on Twitter
get_tweet_details
Get detailed information about a specific tweet
get_user_by_id
Fetches a user by ID
get_user_by_screen_name
Fetches a user by screen name
get_user_followers
Retrieves a list of followers for a given user
get_user_followers_you_know
Retrieves a list of common followers (simulated)
get_user_following
Retrieves users the given user is following
get_user_mentions
Get tweets mentioning a specific user
get_user_profile
Get detailed profile information for a user
get_user_subscriptions
Retrieves a list of users to which the specified user is subscribed (uses following as proxy)
post_tweet
Post a tweet with optional media, reply, and tags
search_twitter
Search Twitter with a query
unfavorite_tweet
Unfavorites a tweet
vote_on_poll
Vote on a poll (mocked)
BEFORE YOU INSTALL
What to know first
Tools you get
24 tools when we connected. get_bookmarks and delete_all_bookmarks need TWITTER_OAUTH2_USER_ACCESS_TOKEN. vote_on_poll returns a mock response, and get_user_followers_you_know, get_user_subscriptions and get_highlights_tweets are approximations.
Requires
- Python 3.10 or later
- TWITTER_API_KEY in your environment
- TWITTER_API_SECRET in your environment
- TWITTER_ACCESS_TOKEN in your environment
- TWITTER_ACCESS_TOKEN_SECRET in your environment
- TWITTER_BEARER_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 24 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install x-twitter-mcpMCP Clients
Claude Desktop — Smithery
CLAUDE DESKTOP — SMITHERY · TERMINAL
npx -y @smithery/cli install @rafaljanicki/x-twitter-mcp-server --client claudeClaude Desktop — pip
CLAUDE DESKTOP — PIP · JSON
{
"mcpServers": {
"x-twitter-mcp": {
"command": "x-twitter-mcp-server",
"args": [],
"env": {
"PYTHONUNBUFFERED": "1",
"TWITTER_API_KEY": "<YOUR_TWITTER_API_KEY>",
"TWITTER_API_SECRET": "<YOUR_TWITTER_API_SECRET>",
"TWITTER_ACCESS_TOKEN": "<YOUR_TWITTER_ACCESS_TOKEN>",
"TWITTER_ACCESS_TOKEN_SECRET": "<YOUR_TWITTER_ACCESS_TOKEN_SECRET>",
"TWITTER_BEARER_TOKEN": "<YOUR_TWITTER_BEARER_TOKEN>",
"TWITTER_OAUTH2_USER_ACCESS_TOKEN": "<YOUR_TWITTER_OAUTH2_USER_ACCESS_TOKEN>"
}
}
}
}
