fanfou-mcp
Related Servers
Alternatives to fanfou-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to read feeds, search, browse full comment trees, and look up users, while performing guarded write actions like posting, replying, editing, voting, saving, and joining or leaving subreddits. Runs over stdio or HTTP with confirmation required for every write, dry-run previews, rate spacing, and hourly caps.Apache 2.0
- AlicenseAqualityCmaintenanceAn MCP server that gives read-only access to the open database of uploaded Twitter/X archives, enabling tweet lookup, full-text and per-account search, timeline windows, follower/following overlap, thread reconstruction, and dated proof "receipts" for posts. It can run as a hosted OAuth connector with per-user API keys or as a local stdio server.15MIT
- AlicenseAqualityBmaintenanceEnables agents and scripts to drive a social publishing account through remote or local MCP tools: drafting, scheduling, approving and publishing posts, running durable background jobs with file attachments, and reading or editing Brand Memory, assets, and standing agents. Hosts can connect over OAuth with no API key, or run the stdio variant with a key for local disk tools.651MIT
- AlicenseBqualityDmaintenanceMCP server for interacting with the X platform (Twitter) via MCP clients like Claude, Cursor AI, and Windsurf AI.2018 npm6MIT
- -licenseNot gradedqualityNot gradedmaintenanceA local read-only MCP server that lets MCP clients such as the Claude app fetch X/Twitter posts and search, Reddit posts, threads and search, and YouTube transcripts and search. It reads through your own saved logins using a fixed set of read-only commands, and cannot post, vote, follow or message.-
- AlicenseNot gradedqualityCmaintenanceTwitter/X MCP server for the API v2, enabling users to manage profiles, posts, likes, retweets, and follows through natural language using a stateless Streamable HTTP transport with OAuth user access token authentication.14 npmISC
TDQS
Scored across 15 tools
Most tools have clearly distinct resource+scope (home_timeline vs user_timeline vs public_timeline vs mentions are separated by audience, not confused). The one real overlap is verify_credentials versus get_user with an empty id, which both return the authenticated user, and the two search_* variants could be momentarily confused. Otherwise boundaries are clean.
The set mixes verb_noun (get_user, get_status, post_status, delete_status) with bare-noun reads (home_timeline, user_timeline, mentions, favorites) and bare-noun writes (favorite, friendship). The convention is readable and mostly predictable, but the inconsistent use of get_/search_ prefixes across reads keeps it from being fully uniform.
15 tools is at the upper edge of the well-scoped band but each one maps to a distinct Fanfou operation (timelines, search, status lifecycle, favorites, follow, context). Nothing feels redundant enough to cut. Slightly heavy but justified by the surface.
Core lifecycle is covered: read/search timelines, get status and reply context, post/delete, favorite/unfavorite, follow/unfollow. Gaps exist (no follower/following lists, no direct messages, no user search), but these are minor for the primary microblogging workflows an agent would run.