Influship vs Uluesky
A side-by-side look at the Influship and Uluesky MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Influship 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?
Choose Influship when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
INFLUSHIP_API_KEY, INFLUSHIP_MCP_URL. - You want tools like
search_creators, autocomplete_creators, find_lookalike_creators.
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 | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 52/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | INFLUSHIP_API_KEYINFLUSHIP_MCP_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 8 | 8 |
| Full listing | View Influship | View Uluesky |
Tools & capabilities
Influship tools 8
search_creatorsautocomplete_creatorsfind_lookalike_creatorsmatch_creatorsget_creatorget_profilelookup_profilesget_posts
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.
Influship
{
"mcpServers": {
"influship": {
"command": "npx",
"args": [
"-y",
"@influship/mcp"
],
"env": {
"INFLUSHIP_API_KEY": "YOUR_INFLUSHIP_API_KEY_HERE",
"INFLUSHIP_MCP_URL": "YOUR_INFLUSHIP_MCP_URL_HERE"
}
}
}
}
Uluesky
{
"mcpServers": {
"uluesky": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-bluesky"
]
}
}
}
Frequently asked questions
Influship is categorized under Social Media and uses a local stdio subprocess. Uluesky belongs to Social Media and uses a local stdio subprocess. Pick Influship 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.
Influship has no declared pricing — check the project's own site. 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 influship and uluesky as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Influship has a quality signal of 52/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Uluesky has 60/100 (Good) with 1 views, 0 installs and 0 GitHub stars.
