Rolli MCP
Related Servers
Alternatives to Rolli MCP
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceSocialCrawl provides the "best" quality public web data on the internet. Access 65+ real-time social media, e-commerce and public web data from a single API with a single schema.5382 npm23MIT- AlicenseNot gradedqualityDmaintenanceReal-time X/Twitter social intelligence for AI agents and developers, powered by Grok's live search capabilities.69 npm3MIT

Xpoz MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceSearch Twitter/X, Instagram, Reddit, and TikTok from AI agents. 52 tools for keyword and hashtag search, user profiles, posts, comments, follower connections, and tracking. Billions of posts indexed, natural-language queries, CSV export up to 500K rows. Remote server (Streamable HTTP) with OAuth sign-in, no API keys needed.12MIT- AlicenseBqualityCmaintenanceQuery social media data from Instagram, TikTok, Twitter/X, Threads, YouTube, Facebook, and Reddit directly through natural language commands. Retrieves profiles, posts, videos, and engagement metrics using the SociaVault API.1134 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables retrieval and management of social media data from Instagram, TikTok, YouTube, X, and Facebook through MCP tools, supporting extractions, search, discovery, batches, schedules, and saved results.32 npmMIT
- AlicenseNot gradedqualityCmaintenanceX and Twitter MCP by SocialDataX for public post search and details, comments and replies, user profiles, and user post lists with pagination.MIT
TDQS
Scored across 30 tools
The toolset is clearly organized by resource family—keyword searches, user searches, expert searches, agent runs, schedules, and integration settings—and each tool's description identifies its target resource and action. The only mild ambiguity is between get_agent_schedule, which includes recent execution records, and list_agent_schedule_runs, which also exposes execution history.
Most tools follow a predictable list_/get_/update_/delete_ verb_noun pattern, and agent run/schedule tools use clear verbs like start, cancel, rerun, pause, and resume. The main deviation is that the three search creation tools are named bare resources (keyword_search, user_search, expert_search) instead of using a consistent create_ prefix.
At 30 tools, this exceeds the 25+ threshold and makes the surface feel heavy for an agent to navigate, even though the tools are internally organized. The broad scope—three search types, agent runs, schedules, integration, and usage—explains the count, but it is still more than is typically reasonable for a single MCP server.
Core workflows are well covered: each search type has create, get, list, and raw-post retrieval; agent runs have a full lifecycle; schedules support CRUD plus pause/resume; and integration/usage endpoints are present. Minor gaps include no way to delete or cancel searches and no webhook test endpoint, but these are workable limitations rather than blocking dead ends.