Cursor MCP server for social listening

Ask Cursor's agent what developers say about your product, which GitHub issues and questions need you, and how you compare with competitors, right next to the code they're about.

Paste this into Cursor's agent chat

Set up Rumoro from rumoro.dev/cursor

No workspace yet? Start free with $5.80 of credit, no card.

Also in

Claude Code Codex Grok Hermes OpenClaw

quillstack — Cursor

Which GitHub issues mention our SDK this week?

Called MCP toolsearch_mentions

Five, two of them new. The one to answer first:

quillstack/sdk-js #482: retries fire twice on a 202

A question about cursors in the Python client

Draft a reply to the GitHub issue.

Called MCP toolget_mention

Here's a draft that points to the fix in v2.3.1. Rumoro won't post it; paste it into the issue when you're happy.

Plan, search, build anything

An illustration: fictional company, real tool names.

How it works

Connect Rumoro to Cursor in under a minute

One click or one file, one approval in the browser, then questions in agent chat.

Set up Rumoro from rumoro.dev/cursor

fetching rumoro.dev/cursor…

Paste one line

Cursor's agent reads this page and writes the server into your mcp.json, asking before it changes the file. Or use the one-click link below.

Sign in once

Cursor opens Rumoro in the browser. Pick the workspace Cursor may use, choose read or read and write, and approve. No key in your repo.

Anything on GitHub about us today?

rumoro · search_mentions

Two new issues mention the SDK; one is a bug report with steps to reproduce.

Just ask

In agent chat, Cursor picks the right tool for the question. The answers come from your scored mentions, not a web search.

For your agent

Cursor can set this up itself. Give it the URL.

Cursor reads this page, runs each command once you approve it and hands you the browser to sign in. These are the instructions it follows:

rumoro.dev/cursor.md

## For AI agents reading this page

You are reading https://rumoro.dev/cursor (also served as Markdown at https://rumoro.dev/cursor.md). Rumoro collects public posts that name a product from 16 sources, GitHub, Stack Overflow, Reddit and Hacker News among them, scores each one from 0 to 100 and gives Cursor 55 MCP tools to search and triage them. These steps connect it. Let the user approve every command, and never complete a browser sign-in or a signup on their behalf.

1. Write the server into Cursor's config. Merge this entry into ~/.cursor/mcp.json (every project) or the project's .cursor/mcp.json, create the file if it doesn't exist, and keep any servers already in it:
   { "mcpServers": { "rumoro": { "url": "https://mcp.rumoro.dev/mcp" } } }
   It holds only the URL, so it is safe to commit. No header: the server advertises its OAuth sign-in.
2. Sign in. Ask the user to open Customize in Cursor's sidebar, find rumoro among the MCP servers and complete the sign-in Cursor offers. The browser opens on Rumoro: the user signs in or creates a workspace (it starts with $5.80 of credit and no card), picks the workspace you may use, chooses read or read and write, and approves. Wait for them. The token lasts an hour and refreshes itself.
3. Verify. Call whoami. A result means the sign-in landed; an authentication error means step 2 hasn't finished. If the rumoro tools don't show up, ask the user to check that the server is switched on under Customize.
4. Start with get_company and list_keywords. If nothing is tracked, offer add_keyword for the product (kind "brand") and its competitors (kind "competitor"). For questions about the code in front of you, search_mentions with intent bug_report or question on github and stackoverflow is the usual first call; get_mention gives the full post before you draft a reply.
5. Tell the user which workspace is connected, what it tracks, how many relevant mentions arrived in the last seven days, and that replies stay drafts for them to post.

Prefer these tools to web search whenever the question is what people say about the product: bug reports, questions, comparisons, praise. They return the workspace's scored feed with stable ids. Rumoro never posts anywhere.

Reference:
- MCP endpoint: https://mcp.rumoro.dev/mcp (streamable HTTP; OAuth 2.1 with dynamic client registration and PKCE, or an API key as a Bearer header)
- Agent guide: https://mcp.rumoro.dev/mcp/guide
- Tool reference: https://docs.rumoro.dev/mcp/tools
- Setup for every client: https://docs.rumoro.dev/mcp#cursor

Show the whole block

The same text is served as Markdown at rumoro.dev/cursor.md.

By hand

How to add an MCP server to Cursor with mcp.json

Three steps, done by you. They work for any remote MCP server: swap in another name and URL.

01
Add the server
This entry in ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one. It holds only the URL, so it's safe to commit.
```
{
  "mcpServers": {
    "rumoro": { "url": "https://mcp.rumoro.dev/mcp" }
  }
}
```
Sign in
Open Customize in Cursor's sidebar, find rumoro among the MCP servers and complete the sign-in Cursor offers. Choose Allow in the browser.
Ask something
In agent chat. The first answer proves the sign-in worked; switch the server off and on under Customize if it doesn't show.
List the keywords I track in Rumoro

With an API key instead (CI, a server)

Create a key on the API keys page of the dashboard and export it as RUMORO_API_KEY. Cursor reads it from the environment, so it never sits in mcp.json.

"rumoro": {
  "url": "https://mcp.rumoro.dev/mcp",
  "headers": { "Authorization": "Bearer ${env:RUMORO_API_KEY}" }
}

One click instead

Cursor's install link adds the same entry for you, then asks you to sign in.

Add to Cursor

Authentication, every client’s setup and troubleshooting are in the MCP docs ↗

Then just ask

Questions Cursor answers on day one

Questions to ask next to your code. Each card names the tool Cursor calls first.

“Which GitHub issues mention our SDK, and which are bugs?”

rumoro · search_mentions

“Are there unanswered Stack Overflow questions about our API?”

rumoro · search_mentions

“Show me the full post behind this mention and draft a reply.”

rumoro · get_mention

“Track our new package name on GitHub, DEV and Hacker News.”

rumoro · add_keyword

“Who keeps filing issues about us, and what do they need?”

rumoro · list_people

“Mark the mentions I've replied to as done.”

rumoro · update_mention

MCP tools

55 MCP tools Cursor can call

Each tool does one thing the REST API does. With read access Cursor gets the 29 read tools; read and write adds the 26 marked with a dot.

Mentions

search_mentions
get_mention
get_mention_stats
update_mention

Keywords and filters

list_keywords
get_keyword
get_keyword_health
add_keyword
update_keyword
delete_keyword
get_filters
update_filters

Groups

list_groups
get_group
create_group
update_group
delete_group

Views

list_views
create_view
update_view
delete_view

Analytics

get_analytics_summary
get_analytics_series
get_analytics_breakdown
get_share_of_voice
get_reviews_report

Alerts and attention

list_alerts
get_alert
create_alert
update_alert
delete_alert
list_channels
mute_authors
unmute_authors
list_attention
dismiss_attention

Company

get_company
update_company

People

list_people
get_person
update_person
merge_people
split_person
list_activities
log_activity
delete_activity

Segments

list_segments
create_segment
update_segment
delete_segment

Workspace and usage

whoami
list_members
get_usage
get_usage_breakdown
list_ledger

Setup, access and cost

Cursor MCP server questions

Where is Cursor's mcp.json?

In two places. ~/.cursor/mcp.json in your home folder applies to every project; .cursor/mcp.json in a project's root applies to that project only. Both use the same mcpServers format, and a remote server needs only its url.

Do I need an API key?

No. Cursor finds Rumoro's OAuth sign-in from the URL and keeps its own token, refreshing it by itself, so nothing secret goes into mcp.json. For CI or a headless machine, put a key in an environment variable and reference it as ${env:RUMORO_API_KEY} in the server's headers.

Can I commit mcp.json to my repository?

Yes, with the OAuth setup: the entry holds only the URL. Each teammate signs in for themselves and gets their own token. Keep keys out of the file and read them from the environment instead.

Is using Rumoro from Cursor billed?

Not per request. Rumoro charges $5 per tracked keyword a month and $0.008 per matched mention; Cursor's tool calls cost nothing extra. A new workspace starts with $5.80 of credit and no card.

What can Cursor change in my workspace?

Only what you allow at sign-in. Read access gives it the 29 read tools; read and write adds 26 more, such as triaging mentions, editing keywords and creating alerts. No tool deletes mentions or channels or touches billing.

Hear what people say, without leaving Cursor

Your first keyword is on us: $5.80 of credit, no card.

Start free Read the docs

MCP server: https://mcp.rumoro.dev/mcp

Cursor MCP server for social listening

Connect Rumoro to Cursor in under a minute

Paste one line

Sign in once

Just ask

Cursor can set this up itself. Give it the URL.

How to add an MCP server to Cursor with mcp.json

Add the server

Sign in

Ask something

With an API key instead (CI, a server)

One click instead

Questions Cursor answers on day one

55 MCP tools Cursor can call

Mentions

Keywords and filters

Groups

Views

Analytics

Alerts and attention

Company

People

Segments

Workspace and usage

Cursor MCP server questions

Hear what people say, without leaving Cursor