Pulse MCP vs Rumoro
A side-by-side look at the Pulse MCP and Rumoro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RumoroSocial Media · Remote HTTP/SSETrack what people say about your product on Reddit, X, Hacker News, GitHub and more40FairAuth: not declaredVerdict: choose Pulse MCP for social media work as a local process; choose Rumoro for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Pulse MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PULSE_API_URL. - You want tools like
metrics, metrics_batch, history.
RChoose Rumoro when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
RUMORO_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R Rumoro | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 36/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | PULSE_API_URL | RUMORO_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Pulse MCP | View Rumoro |
Tools & capabilities
Pulse MCP tools 5
metrics{ platform, views, likes, comments, shares, quotes, bookmarks, publishedAt, title, author, thumbnail }metrics_batchthe same, one per URL (partial failures don't fail the batch)historythe recorded growth curve — `{ count, points }` (posts: `{ t, views, likes, comments }`, profiles: `{ t, followers, posts }`), a snapshot per fresh fetchprofileaccount-level metrics — `{ handle, name, followers, following, posts, verified, avatar }` (YouTube, TikTok, Instagram, X, Bluesky, Mastodon)profile_batchsame as `profile`, one per URL — order preserved; partial failures don't fail the batch. Compare follower counts across a list of creators.
Rumoro tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Pulse MCP
{
"mcpServers": {
"pulse-mcp": {
"command": "npx",
"args": [
"-y",
"pulse-mcp"
],
"env": {
"PULSE_API_URL": "YOUR_PULSE_API_URL_HERE"
}
}
}
}
Rumoro
{
"mcpServers": {
"rumoro": {
"url": "https://mcp.rumoro.dev/mcp"
}
}
}
Frequently asked questions
Pulse MCP is categorized under Social Media and uses a local stdio subprocess. Rumoro belongs to Social Media and uses a remote HTTP/SSE transport. Pick Pulse MCP for social media work and Rumoro for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Pulse MCP has no declared pricing — check the project's own site. Rumoro has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add pulse-mcp and rumoro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pulse MCP has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Rumoro has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.