Summary
One list, one call — nothing to configure and nothing else to learn.
The whole server is get_list_tweets(list_id, max_results), which suits a workflow that already knows which curated list matters and wants its recent items in context. There is no search, no posting and no home timeline, so anything outside that one list is out of reach.
What it is
A single-tool server for X lists. get_list_tweets takes a list_id and a max_results cap and returns that list's tweets; there is nothing else in the surface.
What you get
- The tweets from a named X list, addressed by its list_id
- A cap on how many come back in one call, through max_results
Requirements
Node on your PATH, and the numeric ID of the X list you want to read.
Setup effort
One command plus a key — npx -y x-mcp-server, then supply credentials