Sorsa MCP
OfficialSummary: This server lets an MCP client query X/Twitter data (profiles, tweets, search, communities, lists, relationship checks) through the Sorsa API v3, with optional Sorsa Score metrics.
Profiles — fetch a user's public profile (single or batch), followers, following, verified followers, and "About" metadata.
Tweets — get tweet details (single or up to 100 bulk), a user's tweet feed, replies, quotes, retweeters, long-form Articles, and trending topics by WOEID.
Search — search tweets using Advanced Search operators, search users, search mentions with engagement/date filters, and get Space info.
Communities — list community members, fetch community tweets, and search tweets within a community.
Checks — verify whether an account follows another, replied to a tweet, quoted/retweeted it, retweeted it, or is a community member.
Lists — get list members, list tweets, and list followers.
Utilities — convert username ↔ numeric ID, extract ID from a profile URL, and check API key usage/remaining balance/expiry.
Sorsa Score (opt-in) — get an account's score, 7/30-day score changes, follower category breakdown, top followers/following by score, and new followers/following from the last 7 days.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Sorsa MCP get the latest tweets from @elonmusk"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sorsa MCP
An MCP server for the Sorsa.io API v3 — access to X/Twitter data: profiles, tweets, search, follow/retweet checks, lists and communities, plus optional Sorsa Score metrics.
The server exposes 33 tools by default, one per API endpoint. Seven additional Sorsa Score tools are opt-in and bring the total to 40 when enabled (see Sorsa Score tools).
Installation
npm install
npm run buildOr, once published, run it with no install via npx (see below).
Related MCP server: TwitterAPI MCP Server
Configuration
You need a Sorsa API key. It is read from the SORSA_API_KEY environment variable
and sent with every request in the ApiKey header.
Variable | Required | Default |
| yes | — |
| no |
|
| no | off |
Sorsa Score tools (opt-in)
The seven Sorsa Score tools are off by default. This is the behavior promised on the Sorsa website: Sorsa Score is off unless you turn it on.
To enable them, set SORSA_ENABLE_SCORE to 1 or true (case-insensitive) in the
MCP client config:
{
"mcpServers": {
"sorsa": {
"command": "npx",
"args": ["-y", "sorsa-mcp"],
"env": {
"SORSA_API_KEY": "YOUR_KEY",
"SORSA_ENABLE_SCORE": "1"
}
}
}
}Without the flag the client sees 33 tools; with it, 40. Any other value (or an unset variable) keeps Score tools hidden.
Connecting a client
Cursor
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).
Using the published npm package (nothing to install, npx fetches it):
{
"mcpServers": {
"sorsa": {
"command": "npx",
"args": ["-y", "sorsa-mcp"],
"env": {
"SORSA_API_KEY": "YOUR_KEY"
}
}
}
}Or running from a locally built checkout:
{
"mcpServers": {
"sorsa": {
"command": "node",
"args": ["D:\\Code\\Cursor Projects\\Sorsa_MCP\\dist\\index.js"],
"env": {
"SORSA_API_KEY": "YOUR_KEY"
}
}
}
}Claude Desktop
Edit %APPDATA%\Claude\claude_desktop_config.json and add the same mcpServers
block as above, then restart the app.
Local check
# build
npm run build
# run (communicates over stdio — easiest to test through a client)
SORSA_API_KEY=YOUR_KEY npm start
# verify the tool counts (requires a build; the key value is irrelevant)
SORSA_API_KEY=x node scripts/count-tools.mjs
# → default=33 score=40The quickest way to confirm your key works is the get_key_usage_info tool —
it returns your remaining request balance and the key's expiration date.
Available tools
Profiles: get_user_info, get_user_info_batch, get_followers, get_following,
get_verified_followers, get_account_about
Tweets: get_tweet_info, get_tweet_info_bulk, get_user_tweets, get_tweet_comments,
get_tweet_quotes, get_retweeters, get_article, get_trends
Search: search_tweets, search_users, search_mentions, get_space_info
Communities: get_community_members, get_community_tweets, search_community_tweets
Checks: check_follow, check_comment, check_quoted, check_retweet,
check_community_member
Sorsa metrics (opt-in, see above): get_sorsa_score, get_sorsa_score_changes, get_followers_stats,
get_top_followers, get_top_following, get_new_followers_7d, get_new_following_7d
Lists: get_list_members, get_list_tweets, get_list_followers
Utilities: username_to_id, id_to_username, link_to_id, get_key_usage_info
Project layout
src/endpoints.ts— a declarative table of every endpoint (method, path, parameters, opt-in group). To add or change a tool, edit this file only.src/index.ts— the HTTP client plus tool registration driven by that table.scripts/count-tools.mjs— asserts the 33/40 tool-count invariant on the built output.
How it works
Each endpoint is one entry in ENDPOINTS. Based on each field's in
(path / query / body), the handler routes arguments into the URL path, the
query string, or the JSON body, then sends the request to Sorsa with the ApiKey
header. The response is returned to the client as JSON text.
Entries marked optIn: "score" are filtered out unless SORSA_ENABLE_SCORE
is enabled, so MCP clients only see the tools the user opted into.
License
MIT
Available Tools
40 toolscheck_commentA
Check whether a user has replied under a given tweet. Returns commented: true plus the reply if found.
Inputs: tweet_link (required), username, user_link, user_id.
check_community_memberA
Check whether a user is a member of a given X/Twitter Community. Returns is_member: true/false.
Inputs: community_id (required), username, user_id, user_link.
check_followA
Check whether account 2 follows account 1. Identify each account by id, link, or username (one per side).
Inputs: user_id_1, user_link_1, username_1, user_id_2, +2 more.
check_quotedA
Check whether a user has quoted or retweeted a tweet. Returns a status of quoted / retweeted / none.
Inputs: tweet_link, username, user_id, user_link.
check_retweetA
Check whether a user has retweeted a tweet. Scans up to 100 retweets per request; paginate with next_cursor for popular tweets.
Inputs: tweet_link, username, user_id, user_link, +1 more.
get_account_aboutB
Get metadata from an account's "About" section: country, total number of username changes, account creation info.
Inputs: username, user_id, user_link.
get_articleA
Get full data for an X/Twitter Article (long-form post): complete text, title, author and metadata.
Inputs: tweet_link.
get_community_membersB
Get a paginated list of member profiles of an X/Twitter Community.
Inputs: community_link (required), next_cursor.
get_community_tweetsB
Get a paginated feed of tweets published inside an X/Twitter Community.
Inputs: community_id (required), order, next_cursor.
get_followersA
List accounts that follow the given user (up to 200 profiles per page). Use next_cursor to paginate.
Inputs: username, user_id, user_link, next_cursor.
get_followers_statsB
Get a breakdown of an account's followers by Sorsa category: influencers, projects, and VC employees.
Inputs: username, user_id, user_link.
get_followingB
List accounts that the given user follows (up to 200 profiles per page). Use next_cursor to paginate.
Inputs: username, user_id, user_link, next_cursor.
get_key_usage_infoA
Get usage stats for the current API key: total allocated requests, remaining balance, and expiration date.
Inputs: no named parameters.
get_list_followersB
Get accounts that follow (are subscribed to) an X/Twitter List.
Inputs: list_link (required), next_cursor.
get_list_membersB
Get profiles of all accounts in an X/Twitter List.
Inputs: list_id (required), next_cursor.
get_list_tweetsB
Get a paginated feed of tweets from members of an X/Twitter List (up to 20 per page).
Inputs: list_id (required), next_cursor.
get_new_followers_7dA
Get accounts that started following the user in the last 7 days (crypto ecosystem).
Inputs: username, user_id, user_link.
get_new_following_7dC
Get accounts the user started following in the last 7 days (crypto ecosystem).
Inputs: username, user_id, user_link.
get_retweetersA
Get a paginated list of users who retweeted the given tweet (newest first).
Inputs: tweet_link, next_cursor.
get_sorsa_scoreB
Get the Sorsa Score for an account — a numeric estimate of its recognition and influence.
Inputs: username, user_id, user_link.
get_sorsa_score_changesA
Get the change in Sorsa Score over the last 7 and 30 days.
Inputs: username, user_id, user_link.
get_space_infoA
Get information about an X/Twitter Space: title, state, schedule, host and participants.
Inputs: id, link.
get_top_followersB
Get the 20 followers of an account with the highest Sorsa Score.
Inputs: username, user_id, user_link.
get_top_followingA
Get the 20 accounts a user follows with the highest Sorsa Score.
Inputs: username, user_id, user_link.
get_trendsB
Get trending topics for a location identified by its WOEID.
Inputs: woeid (required).
get_tweet_commentsB
Get a paginated list of replies (comments) under a tweet (up to 20 per page).
Inputs: tweet_link, order_by, next_cursor.
get_tweet_infoA
Get full data for a single tweet: text, date, language, engagement metrics, author and media.
Inputs: tweet_link (required).
get_tweet_info_bulkB
Get full data for up to 100 tweets in a single request.
Inputs: tweet_links (required).
get_tweet_quotesA
Get a paginated list of tweets that quoted the given tweet (up to 20 per page).
Inputs: tweet_link, next_cursor.
get_user_infoB
Get the public profile of an X/Twitter account: display name, bio, follower/following counts, tweet count, verification, etc.
Inputs: username, user_id, user_link.
get_user_info_batchB
Get public profiles for multiple X/Twitter accounts in one request. Provide a list of usernames and/or user_ids.
Inputs: usernames, user_ids.
get_user_tweetsB
Get a paginated feed of tweets posted by a user (up to 20 per page).
Inputs: username, user_id, user_link, next_cursor.
get_verified_followersB
List verified accounts that follow the given user. Use next_cursor to paginate.
Inputs: username, user_id, user_link, next_cursor.
id_to_usernameA
Convert a numeric X/Twitter user ID into the account's current username.
Inputs: user_id (required).
link_to_idB
Extract the stable numeric user ID from a profile URL.
Inputs: link (required).
search_community_tweetsB
Search tweets by keyword within a specific X/Twitter Community.
Inputs: community_link (required), query, order, next_cursor.
search_mentionsA
Get tweets that mention a user handle (newest first), with optional engagement and date filters.
Inputs: query, min_likes, min_replies, min_retweets, +4 more.
search_tweetsB
Search tweets using X/Twitter Advanced Search syntax (operators like from:, since:, min_faves:, etc.).
Inputs: query, order, next_cursor.
search_usersB
Search X/Twitter accounts by keyword or phrase.
Inputs: query, next_cursor.
username_to_idB
Convert an X/Twitter username into its stable numeric user ID.
Inputs: user_handle (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 40 tools
Most tools have clearly distinct purposes, but the large number of similar-sounding tools (e.g., get_followers, get_new_followers_7d, get_top_followers) may cause slight ambiguity. However, descriptions are specific enough to differentiate.
All tool names follow a consistent verb_noun snake_case pattern (e.g., check_comment, get_user_info, search_tweets). No mixing of conventions.
40 tools is on the high side, but the server covers a broad analytics-focused domain (Twitter data, Sorsa Score). The number is borderline but mostly justified by the granularity of operations.
The server excels at read operations, covering user profiles, tweets, followers, communities, trends, and spaces. Missing write operations (e.g., post, follow) are absent, but the stated purpose appears analytics-oriented, so minor gap.
Maintenance
Related MCP Connectors
Official twitterapi.io hosted MCP: Twitter/X tweets, users, followers, trends. OAuth or API key.
Official MCP server for twitterapis.com. Twitter/X search, users, DMs, Grok, monitoring and writes.
Hosted X (Twitter) MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Hosted MCP server from TwitterAPI.io that gives AI agents read-only access to Twitter/X data. 12 tools: tweet search with X operators, user profiles, a user's latest tweets, followers and followings, replies, quotes, retweeters, mentions and trends. Connect at https://mcp.twitterapi.io/mcp with a TwitterAPI.io API key or account sign-in; usage is paid per result returned. Separately, TwitterAPI.io also offers x402 pay-per-call HTTP endpoints (tweet search, user info, a user's latest tweets) paid in USDC on Base or Solana with no account or API key; see https://docs.twitterapi.io/x402-pay-per-call. The MCP server itself uses an API key or sign-in.
Related MCP Servers
- AlicenseCqualityDmaintenanceAn MCP server for accessing the Twitter/X Api45 API, allowing users to retrieve user profiles, timelines, followers, and media. It supports searching communities, jobs, and trends, while also providing tools to monitor live broadcasts and Twitter Spaces.28MIT
- AlicenseBqualityDmaintenanceAn MCP server that provides access to Twitter data and write actions through TwitterAPI.io, bypassing the need for a standard Twitter developer account. It enables users to search tweets, retrieve profiles, and post content with support for pagination and enterprise proxy configurations.16 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for interacting with the Twitter/X API v2, enabling AI assistants to retrieve tweets, post content, reply, quote, and more programmatically.13MIT
- FlicenseAqualityDmaintenanceAn MCP server for interacting with X/Twitter, enabling posting tweets, searching, user info, timeline, liking, retweeting, and deleting tweets.71-