TwittrAPI vs Uluesky
A side-by-side look at the TwittrAPI and Uluesky MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TwittrAPISocial Media · Local subprocess (stdio)Read public Twitter/X data: tweets, profiles, followers, search. No X developer account.56GoodAuth: api key requiredVerdict: choose TwittrAPI for social media work as a local process; choose Uluesky for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
TChoose TwittrAPI when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TWITTRAPI_API_KEY, RAPIDAPI_KEY, RAPIDAPI_HOST, TWITTRAPI_BASE_URL, TWITTRAPI_RESPONSE_FORMAT, TWITTRAPI_X_COOKIE, TWITTRAPI_X_PROXY, TWITTRAPI_X_CHAT_PASSCODE. - You want tools like
get_user_by_username, get_user_by_id, username_to_id.
Choose Uluesky when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_profile, get_posts, search_posts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T TwittrAPI | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 56/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | TWITTRAPI_API_KEYRAPIDAPI_KEYRAPIDAPI_HOSTTWITTRAPI_BASE_URLTWITTRAPI_RESPONSE_FORMATTWITTRAPI_X_COOKIETWITTRAPI_X_PROXYTWITTRAPI_X_CHAT_PASSCODE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 28 | 8 |
| Full listing | View TwittrAPI | View Uluesky |
Tools & capabilities
TwittrAPI tools 28
get_user_by_usernameProfile by handle, including the numeric user IDget_user_by_idProfile by numeric user IDusername_to_idResolve a handle to its user IDusers_by_idsProfiles for up to 500 user IDs at onceget_user_tweetsA user's tweetsget_user_tweets_and_repliesA user's tweets and repliesget_user_mediaA user's tweets with photos or videosget_followersA user's followersget_followingAccounts a user followsget_verified_followersA user's verified followerssearch_tweetsSearch with X operators; Top, Latest, People, Photos or Videosget_tweetA tweet and its reply thread- +16 more on the listing page
Uluesky tools 8
get_profileLook up a Bluesky user's profile by handle (e.g., "alice.bsky.social"). Returns display name, bio, follower/following counts, avatar, and verification status.get_postsFetch recent posts from a Bluesky user's timeline. Returns post text, timestamps, likes, reposts, reply counts, and threaded replies.search_postsSearch Bluesky posts by keyword or phrase. Returns matching posts with author handles, timestamps, engagement metrics, and content.Requires bsky_handle and bsky_app_password in the gateway URL query params.get_feedGet posts from a Bluesky feed (e.g., "discover", "what's-hot"). Returns recent posts with authors, timestamps, and engagement counts.get_followersGet a user's followers on Bluesky by handle. Returns follower profiles including handles, display names, bios, and follower counts.get_followsGet accounts a Bluesky user follows by handle. Returns followed profiles with handles, display names, bios, and descriptions.get_threadFetch a post thread by URI. Returns the parent post and all replies in conversation order with timestamps, authors, and engagement data.resolve_handleConvert a Bluesky handle to its DID (decentralized identifier). Returns the DID for programmatic account lookups.
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.
TwittrAPI
{
"mcpServers": {
"twittrapi": {
"command": "npx",
"args": [
"-y",
"twittrapi-mcp"
],
"env": {
"TWITTRAPI_API_KEY": "YOUR_TWITTRAPI_API_KEY_HERE",
"RAPIDAPI_KEY": "YOUR_RAPIDAPI_KEY_HERE",
"RAPIDAPI_HOST": "YOUR_RAPIDAPI_HOST_HERE",
"TWITTRAPI_BASE_URL": "YOUR_TWITTRAPI_BASE_URL_HERE",
"TWITTRAPI_RESPONSE_FORMAT": "YOUR_TWITTRAPI_RESPONSE_FORMAT_HERE",
"TWITTRAPI_X_COOKIE": "YOUR_TWITTRAPI_X_COOKIE_HERE",
"TWITTRAPI_X_PROXY": "YOUR_TWITTRAPI_X_PROXY_HERE",
"TWITTRAPI_X_CHAT_PASSCODE": "YOUR_TWITTRAPI_X_CHAT_PASSCODE_HERE"
}
}
}
}
Uluesky
{
"mcpServers": {
"uluesky": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-bluesky"
]
}
}
}
Frequently asked questions
TwittrAPI is categorized under Social Media and uses a local stdio subprocess. Uluesky belongs to Social Media and uses a local stdio subprocess. Pick TwittrAPI for social media work and Uluesky 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.
TwittrAPI is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Uluesky 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 twittrapi and uluesky as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TwittrAPI has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Uluesky has 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars.