mcpField
S
Sorsa Api Mcp

Sorsa Api Mcp

Local
github.com/Sorsa-ioDeveloper Tools4Updated 18w ago

About Sorsa Api Mcp

Sorsa Api Mcp connects MCP clients to the Sorsa.io API v3 for X/Twitter profiles, posts, search, metrics, lists and communities. It registers 40 tools, with each tool corresponding to an API endpoint.

Key features

  1. 01Access X/Twitter profiles and posts
  2. 02Search tweets, users and mentions
  3. 03Check follow, retweet and quote relationships
  4. 04Retrieve Sorsa scores and follower statistics
  5. 05Query lists and communities

Use cases

  1. 01Look up X/Twitter profiles and tweets
  2. 02Search for posts, users or mentions
  3. 03Check whether accounts follow or retweet
  4. 04Review Sorsa scores and follower statistics

MCP support

The MCP server exposes 40 Sorsa API v3 endpoints as tools to MCP clients. Requests use the Sorsa API key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"sorsa-io-sorsa": {
"command": "npx",
"args": [
"-y",
"sorsa-mcp"
],
"env": {
"SORSA_API_KEY": "<SORSA_API_KEY>"
}
}
}
}
Run commandnpx -y sorsa-mcp
Environment variables to set
SORSA_API_KEYSecretSorsa.io API key, sent in the ApiKey header with every request.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmsorsa-mcp1.0.4

Tools

40

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
user_idstringNoNumeric X/Twitter user ID.
usernamestringNoX/Twitter handle without the @ (provide one of username / user_id / user_link).
user_linkstringNoFull URL of the X/Twitter profile.

Details

From the project 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

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

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

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.