# Rumoro Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Rumoro

Monitor what people say about your brand on Reddit, X, Hacker News and GitHub with sentiment and intent analysis

- Record: https://musedirectory.ai/connector/rumoro
- Category: Marketing & Ads
- Developer: Rumoro (https://rumoro.dev)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1130ms, checked 2026-10-29T10:16:07Z
- Endpoint: https://mcp.rumoro.dev/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T00:06:11Z)
- Source: Found in the official MCP Registry (dev.rumoro/mcp) https://registry.modelcontextprotocol.io/v0/servers?search=dev.rumoro%2Fmcp

Tracks mentions of your brand and competitors across social platforms and review sites. Filters by sentiment, buying intent, keywords and audience segments. Provides analytics, alerts and share-of-voice reports. Requires API key and paid subscription.

Example request: "Show me negative mentions of our product on Twitter from the last week and assign them to my team"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Rumoro to help me. It is a free service with an MCP server at https://mcp.rumoro.dev/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- list_segments: Lists your saved audience segments, which are named people filters such as "Large accounts" or "Open to switching", with the current number of people in each. Also returns presets you can save with create_segment. To see who is in a segment, pass its id to list_people.
- create_segment: Saves an audience segment with a name and a filter. The filter can use platforms, tags, follower range, minimum mentions or negative mentions, intents, keyword kinds the person did or did not mention, first seen within N days, and linkHosts they linked to. Members are worked out 
- update_segment: Changes a saved segment's name, description or filter. `filter` sets the full new filter.
- delete_segment: Deletes a saved segment. The people in it are not changed.
- list_views: Lists your saved views, which are named mention filters such as "Bug reports" or "Waiting on us". Pass a view's id as viewId to search_mentions to get exactly what it shows.
- create_view: Saves a view with a name and a filter. The filter uses the fields of search_mentions, such as keywords or keyword kinds, platforms, status, relevant, sentiments, intents, languages, author tags, follower range, replies, link hosts, automated and free text. A list matches any valu
- update_view: Changes a saved view's name, description or filter. `filter` sets the full new filter.
- delete_view: Deletes a saved view and leaves its mentions untouched.
- list_groups: Lists the workspace's keyword groups, the default first. Groups organize keywords, for example by client, campaign or product. Every keyword is in one group, a group can hold a term once, and get_usage_breakdown with by=group shows each group's cost. externalId finds the group wi
- get_group: Returns a keyword group by id, with its number of keywords.
- create_group: Creates a keyword group with a name that is unique in the workspace. You can add externalId, your own unique id such as a client id. You can also add context, a company description saying who the business is, what it sells and to whom. The classifier reads it instead of the whole
- update_group: Changes a keyword group's name, its externalId or its company description in context. Null clears externalId. Null clears context too, so the workspace profile applies again, and new mentions use the change right away. The default group can be renamed but takes no description, be
- delete_group: Deletes a keyword group and all of its keywords, each as delete_keyword would, mentions included. The default group cannot be deleted. The answer says how many keywords were deleted.
- search_mentions: Searches the workspace's mentions. You can filter by keyword, platform, status (open, ignored, done), relevant, minimum relevance, minimum confidence (0 to 1), sentiment, intent, text (q, in the post or the author's name) and time range (ISO 8601). You can also filter by one pers
- get_mention: Fetches one mention, classification included (relevance, sentiment, intents, confidence, uncertain, note).
- list_mention_comments: The comments under a mention's post, newest first, whether or not each names your keyword, with a light sentiment and intent read and mentionId when a comment is itself one of your mentions. Filled for new relevant mentions of keywords with comments on, from 30 minutes after the 
- update_mention: The only way to change a mention. Set status to "ignored" when it is not interesting, "done" when handled, or "open" to reopen it. Assign it with assigneeId, or null to remove the assignment. Hide it from the feed until an ISO 8601 time with snoozedUntil, or null to bring it back
- add_keyword: Creates a keyword to track. kind is "brand" (default), "competitor" or "topic". platforms limits where it runs, all by default. New posts with the term are matched, classified and delivered. To narrow a common word, set `matching` (requiredTerms with requiredMode any or all, excl
- update_keyword: Changes a keyword. You can rename it with term: the new term is tracked from now on, with no look-back, and the keyword keeps its id, settings and what the old term found. You can set its platforms (a list, or null for all), mute or unmute it, change its kind, or set its classifi
- duplicate_keyword: Creates a new keyword with an existing keyword's settings. Give the new term, or the same term with another groupId, since a group tracks a term once. It copies the kind, platforms, context, every matching rule, the monthly mention cap and the comments setting. Review pages and f
- get_analytics_summary: Returns summary counts for a period. Covers matched and relevant mentions, unique posts and people, sentiment, buying intent, questions, reach and triage. Reach sums followers where known. Triage gives open, ignored and done counts, mentions waiting over 24h, handled rate and med
- get_analytics_series: Counts matched, relevant and sentiment mentions per day or week (bucket, days by default up to 90 days). Returns one "total" series, or splits by="platform" or by="keyword" (top 20, rest as "other"). Period options match get_analytics_summary. compare=true adds `previous`, the pr
- get_analytics_breakdown: Returns a table grouped by `by`. That is platform, keyword, sentiment, intent, status (open, ignored, done), hour (weekday and hour in timezone, to see when people post) or person (the most active authors, with followers). Each row has matched, relevant, its percentage of the per
- get_share_of_voice: Compares your brand with competitors. Returns each keyword with matches in the period, with matched, relevant, negative and buy-intent counts and its percentage of all brand and competitor matches. Topics are counted but not part of the split. The period works as in get_analytics
- get_reviews_report: Reports on the reviews your keywords collect from the App Store, Google Play, Trustpilot and Google over a period. Includes totals (reviews, average stars, star distribution, replies, open 1 and 2 star reviews), tags from unhappy reviews, and each review page's average stars per 
- list_alerts: Returns every alert with its filter, mode, schedule and channels. The mode is instant, or hourly, daily or weekly for a digest.
- get_alert: Fetches an alert by id. Includes delivery stats as well as its filter, mode, schedule and channels.
- delete_alert: Deletes an alert. Its channels remain and other alerts can use them. This cannot be undone. To keep the alert, disable it with update_alert enabled=false instead.
- list_channels: Lists alert destinations (Slack channels, Telegram chats, email lists, webhooks). Connect Telegram chats in the dashboard under Settings, Integrations. The API can't.
- list_attention: Lists items that need a person, latest first. Kinds are mention.spike (mentions jumped in the last hour), sentiment.negative_spike (24-hour negative share jumped), keyword.noisy (turned noisy) and channel.failing (recent sends all failed). Checks run hourly, and items resolve whe
- dismiss_attention: Moves an attention item (att_... from list_attention) out of the open list for as long as its condition lasts.
- create_alert: Creates an alert. mode "instant" sends each matching mention as it arrives. "hourly" sends a digest of the previous UTC hour at five past, skips hours with no mention above the minimum, and takes no schedule and no email channel (only Slack, Telegram and webhooks). "daily" sends 
- update_alert: Changes an alert's name, enabled, mode, schedule, filter or channelIds. filter and channelIds are replaced in full.
- mute_authors: Adds authors to an alert's muted list and keeps the rest of the filter. Entries can be profile or post links, @handles, u/names, Bluesky DIDs or display names. Links are stored as the author's profile. Authors already on the list are skipped, and entries that don't name a person 
- unmute_authors: Takes authors off an alert's muted list and keeps the rest of the filter. Each entry can be the stored value or a link to the person's profile or posts. Authors not on the list are skipped.
- list_keywords: Lists the workspace's keywords with stats, polling status, matching rules and context, plus `total`. With no arguments you get all keywords, latest first. q searches the term and context. You can filter by kind, status (active, muted by someone, paused for balance, noisy when the
- get_keyword: Fetches a keyword by id. Returns its setup (term, kind, platforms, matching rules, context, monthly cap, pausedForCap), its stats and how polling goes on each platform.
- get_keyword_health: Checks whether a keyword earns its cost, over range 7d, 30d or 90d (default 30d). Returns a status with plain-word reasons. noisy is 20+ scored matches with under 30% relevant, quiet is 7+ days old with nothing relevant, new is under 7 days old, and the rest are healthy, capped o
- delete_keyword: Stops monitoring a keyword and deletes its mentions, but keeps a post that another keyword also matched. Alerts that named it drop it, and an alert that named only this keyword is disabled instead of widening to all keywords. This cannot be undone. Muting with update_keyword mute
- whoami: Returns the workspace this credential works in, the kind of credential (an API key or an OAuth sign-in), whether it can write, and the signed-in user if there is one. Call it once when a session starts, to name the workspace and learn whether write tools will work.

Screening checks:
- MCP handshake: pass (Answered in 1721ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.rumoro.dev, rumoro.dev not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (55 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 10 days ago)
- AI review of purpose and tool behavior: pass (No concerns)