
Rolli
ai.rolliPublished by rolli.aiv1.2.1Updated Oct 24, 2026
Social media search, expert discovery, and analytics across X, Reddit, YouTube, and more
Overview
Lets an assistant run social media keyword, user, and expert searches across X, Reddit, YouTube and more, and manage Rolli Agent reports.
- What you can do
- Rolli IQ provides social media search and analytics across X, Reddit, YouTube, Facebook, Instagram, Threads, Bluesky and other platforms. Tools create and retrieve keyword/hashtag searches, user profile searches, and expert searches, returning status, analytics, posts, and conversation topic trees. It also manages Rolli Agent investigations and scheduled reports, including starting, cancelling, rerunning, pinning, renaming, and deleting runs and schedules, plus webhook setup and API usage reporting.
- When to use it
- Use it when an assistant needs cross-platform social listening, topic breakdowns, profile analysis, expert discovery, or recurring social intelligence reports. It fits research, marketing, and monitoring workflows that already use a Rolli account.
- Requirements
- Runs locally over stdio via the npm package @rolli/mcp, so Node.js and npx are needed. A Rolli account with API access is required, and the API token is supplied through the ROLLI_API_TOKEN environment variable. Optional variables include ROLLI_USER_ID, ROLLI_POLL_INTERVAL_MS, and ROLLI_MAX_POLL_MS. Network access to the Rolli API is required.
Installation
In SourceWeft
- Open Rolli in the dashboard and add it to a workspace.
- 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
rolli-mcp
MCP server for Rolli IQ — social media search and analytics across X, Reddit, YouTube, Facebook, Instagram, Threads, Bluesky, and more.
[Rolli MCP server]Tools
Setup
You need a Rolli account with API access. Get your API token from rolli.ai.
Claude Desktop / Claude Code / VS Code / Cursor / Windsurf
Add to your MCP config (claude_desktop_config.json, .vscode/mcp.json, or equivalent):
ROLLI_USER_ID is optional and defaults to "rolli-mcp". Set it to override with your own user ID.
Optional Environment Variables
Smithery
This server includes a smithery.yaml for deployment via Smithery. It will prompt for your API token during setup.
Usage Examples
Search for a keyword across social media:
"Search for posts about 'artificial intelligence' on Twitter and Reddit from the last week"
Analyze a user profile:
"Look up @elonmusk on Twitter and analyze their recent posts"
Get topic breakdown:
"Show me the topic tree for my keyword search #123"
Check API usage:
"How many searches have I used this month?"
Set up a webhook:
"Set my webhook URL to https://myapp.com/rolli-callback"
Optional X/Twitter Source Context
Rolli is useful for cross-platform social search, topic trees, user analysis, and scheduled social intelligence reports. If an agent also needs reviewed account-scoped X/Twitter source evidence before a Rolli investigation, collect that evidence in an approved OpenClaw workflow such as TweetClaw, then pass only the reviewed handles, post URLs, post IDs, excerpts, or summary notes into Rolli prompts.
Keep Rolli and TweetClaw credentials separate. Do not transfer API tokens, cookies, sessions, or account credentials between tools. Treat TweetClaw output as source context for Rolli searches and reports, not as publishing approval.
Development
CI runs on every push and PR to master. Releases published on GitHub automatically publish to npm (requires NPM_TOKEN repo secret).
License
MIT
Source: README.md at commit f0ded75
Tools
0Version history
1- v1.2.1LatestSep 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