Sorsa Mcp

io.github.Sorsa-ioPublished by GitHub account Sorsa-iov1.0.4Updated Oct 24, 2026

MCP server for the Sorsa.io X/Twitter data API

The publisher's own server: Sorsa

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Local MCP server that connects an assistant to the Sorsa.io X/Twitter data API for profiles, tweets, search, lists, communities and Sorsa metrics.

What you can do
Look up profiles, followers, following, verified followers and account details, including batch lookups and username/ID/link conversion. Retrieve tweets, comments, quotes, retweeters, articles and trends. Search tweets, users, mentions and spaces. Inspect communities and lists, including members and tweets. Run follow, comment, quote, retweet and community-membership checks. Read Sorsa scores, score changes, follower statistics and top or new followers, and check API key usage.
When to use it
Useful when you want an assistant to research X/Twitter accounts, posts and communities, verify engagement or follow relationships, or pull Sorsa-specific scores and follower analytics without leaving the chat client.
Requirements
Runs locally over stdio, typically via npx or a built checkout, so Node.js is needed. Requires a Sorsa.io API key supplied in the SORSA_API_KEY environment variable; an optional SORSA_BASE_URL overrides the default API endpoint. Network access to the Sorsa API is required.
Before you install
The SORSA_API_KEY is sent with every request, so keep it out of shared configuration files. Requests consume the key's request balance, which the usage tool reports. Queries and account identifiers are sent to the third-party Sorsa.io service. The tools read data; the README lists no tools that post or modify content.

Installation

In SourceWeft

  1. Open Sorsa Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Sorsa MCP

An MCP server for the Sorsa.io API v3 — access to X/Twitter data: profiles, tweets, search, follow/retweet checks, Sorsa scores, lists and communities.

The server exposes 40 tools, one per API endpoint.

Installation

bash
npm installnpm run build

Or, once published, run it with no install via npx (see below).

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.

VariableRequiredDefault
SORSA_API_KEYyes—
SORSA_BASE_URLnohttps://api.sorsa.io/v3

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):

json
{  "mcpServers": {    "sorsa": {      "command": "npx",      "args": ["-y", "sorsa-mcp"],      "env": {        "SORSA_API_KEY": "YOUR_KEY"      }    }  }}

Or running from a locally built checkout:

json
{  "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

bash
# buildnpm run build
# run (communicates over stdio — easiest to test through a client)SORSA_API_KEY=YOUR_KEY npm start

The 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: 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). To add or change a tool, edit this file only.
  • src/index.ts — the HTTP client plus tool registration driven by that table.

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.

License

MIT

Source: README.md at commit 01b3f52

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Sorsa integrations