The search tool is the part worth knowing about: instead of guessing at operator syntax, you pass engagement thresholds, required words, a date floor and a flag for originals only. That makes it usable for finding what a topic actually looked like on a given week, rather than for one-off lookups. Getting started is the friction — the key is issued by hand.
An MCP server over Apex's social-media infrastructure, covering X. Tweets can be read, searched, posted and replied to; lists and follows can be managed; and reply drafts can be generated from text or an image.
- Detailed information about a specific tweet, and structured search across tweets
- Search by criteria rather than a query string: minimum likes, words to include, a start date, originals only, replies included or not
- Posting new tweets with optional images, and posting replies to existing ones
- Generated reply suggestions for a piece of text or an image
- Full profile details for a user by handle or numeric id, including follower counts and verification
- Follow and unfollow, plus paginated follower and following lists
- Lists created, read, updated and deleted, with members added and read back page by page
An Apex account and an API key, which is requested from the maintainer rather than self-served. The key and the API host are passed as arguments in the client config. There is a one-click install through Smithery, and a bundle you can build and install into Claude Desktop directly.
One command plus a key — npx -y apex-mcp-server, then supply credentials
