Shippost MCP vs Xdataapi: X (Twitter) data
A side-by-side look at the Shippost MCP and Xdataapi: X (Twitter) data MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shippost MCP for social media work as a local process; choose Xdataapi: X (Twitter) data for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Shippost MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_my_profile, get_timeline, get_mentions.
Choose Xdataapi: X (Twitter) data when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
XDATAAPI_KEY. - You want tools like
get_user, get_users, get_user_tweets.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 52/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | XDATAAPI_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 17 | 14 |
| Full listing | View Shippost MCP | View Xdataapi: X (Twitter) data |
Tools & capabilities
Shippost MCP tools 17
get_my_profileGet the authenticated Twitter user's profile — name, bio, follower count, tweet count.get_timelineGet recent tweets from my home timeline. Returns tweets with text, author, engagement metrics, and URLs. Use this to see what's happening in the user's feed.get_mentionsGet recent tweets that mention me. Returns tweets where other users have @mentioned the authenticated user.get_user_profileLook up a Twitter user's profile by their username. Returns their name, bio, follower/following counts, and tweet count.get_tweetGet a specific tweet by its ID. Returns the full tweet text, author, engagement metrics, and conversation context.search_tweetsSearch recent tweets by keyword or phrase. Searches the last 7 days of public tweets. Retweets are excluded. Returns tweets with text, author, engagement metrics, and URLs.post_tweetPost a tweet from the authenticated user's account. The tweet will be posted immediately and publicly visible.reply_to_tweetReply to a specific tweet. Posts a public reply to the given tweet from the authenticated user's account.like_tweetLike a tweet.retweetRetweet a tweet.follow_userFollow a Twitter user.find_opportunitiesScan my timeline and find the best tweets to reply to, scored by relevance. Uses AI to analyze each tweet and score it on: - Relevance to your niche/expertise - Engagement potential (will a reply get seen?) - Reply opportunity (can you add genuine value?) Returns scored tweets with suggested reply angles. Requires a ShipPost API key (SHIPPOST_API_KEY). Get one at https://shippost.ai- +5 more on the listing page
Xdataapi: X (Twitter) data tools 14
get_userProfile of one X user by handle. 1 credit.get_usersProfiles of up to 100 X users by handle in one call. 1 credit per profile found.get_user_tweetsLatest tweets of a user, newest first. 1 credit per tweet.get_followersFollowers of a user. 0.1 credit per profile. Not every account tier can read this; a 403 is free.get_follower_idsNumeric ids of the followers of a user, no profiles. 0.02 credit per id. Same page as get_followers, so a page read there is a cache hit here. A 403 is free.get_followingAccounts a user follows. 0.1 credit per profile. Not every account tier can read this; a 403 is free.search_tweetsX advanced search. q takes the x.com operators. 1 credit per tweet or profile. product Latest is always available; Top may answer 403 (free).get_tweetOne tweet by numeric id, with its author. 1 credit.get_tweetsUp to 100 tweets by numeric id in one call. 1 credit per tweet found.get_threadA tweet with its thread and replies; the focal tweet comes first. 1 credit per tweet returned.get_repliesDirect replies to a tweet, one page. 1 credit per reply.get_quotesTweets that quote a tweet, newest first. 1 credit per tweet.- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Shippost MCP
{
"mcpServers": {
"shippost-mcp": {
"command": "uvx",
"args": [
"shippost-mcp"
]
}
}
}
Xdataapi: X (Twitter) data
{
"mcpServers": {
"xdataapi-x-twitter-data-3": {
"url": "https://api.xdataapi.io/mcp"
}
}
}
Frequently asked questions
Shippost MCP is categorized under Social Media and uses a local stdio subprocess. Xdataapi: X (Twitter) data belongs to Social Media and uses a remote HTTP/SSE transport. Pick Shippost MCP for social media work and Xdataapi: X (Twitter) data for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Shippost MCP has no declared pricing — check the project's own site. Xdataapi: X (Twitter) data has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add shippost-mcp and xdataapi-x-twitter-data-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shippost MCP has a quality signal of 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Xdataapi: X (Twitter) data has 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars.
