get_v2_Followers — twitter MCP Tool Read-only
get_v2_Followers
(get v2 followers) is one of 32 tools on the
twitter
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_v2_Followers from your client
- Claude Code twitter get_v2_Followers run in your project directory
- Claude Desktop twitter get_v2_Followers ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor twitter get_v2_Followers ~/.cursor/mcp.json
- VS Code twitter get_v2_Followers .vscode/mcp.json
- Zed twitter get_v2_Followers ~/.config/zed/settings.json
- Windsurf twitter get_v2_Followers ~/.codeium/windsurf/mcp_config.json
- Cline twitter get_v2_Followers ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI twitter get_v2_Followers ~/.gemini/settings.json
- Grok twitter get_v2_Followers .mcp.json (in your project root)
- ChatGPT twitter get_v2_Followers Settings → Connectors → Advanced → Developer mode
- Claude.ai twitter get_v2_Followers Settings → Connectors → Add custom connector
- LangChain twitter get_v2_Followers pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http twitter https://mcp.jojapi.com/twitter
Other tools on this server
- get_AutoComplete
- get_Search
- get_v1_1_Trends
- get_v1_1_Locations
- get_v2_TweetDetail
- get_v2_Tweet
- get_v2_Favoriters
- get_v2_Retweeters
- get_v1_1_TranslateTweet
- get_email_search_by_username
- get_v1_1_Users
- get_v2_UserByScreenName
- get_v2_UserByRestId
- get_v2_UsersByRestIds
- get_v2_UserTweets
- get_v2_UserTweetsAndReplies
- get_v2_UserMedia
- get_v2_Likes
- get_v1_1_Followers
- get_v1_1_FollowersIds
- get_v2_VerifiedFollowers
- get_v2_Following
- get_v1_1_Following
- get_v1_1_FollowingIds
- get_v2_Subscriptions
- get_v2_UserAffiliates
- get_v2_UserHighlights
- get_v1_1_TranslateProfile
- get_ShortUrl
- get_v1_1_Hashflags
- get_v2_ListTimeline
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.