Upriver vs Scholar MCP
A side-by-side look at the Upriver and Scholar MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Upriver for research work over a hosted endpoint; choose Scholar MCP for research as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Upriver when
- You need dedicated capabilities in the Research domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
breakout_search_topics, breakout_list_topics.
Choose Scholar MCP when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 47/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Upriver | View Scholar MCP |
Tools & capabilities
Upriver tools 2
breakout_search_topicsSearch breakout topics by keyword.breakout_list_topicsBrowse breakout topics gaining traction right now.
Scholar MCP 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.
Upriver
{
"mcpServers": {
"upriver": {
"url": "https://mcp.upriver.ai/icon.png"
}
}
}
Scholar MCP
{
"mcpServers": {
"scholar-mcp": {
"command": "uvx",
"args": [
"scholar-mcp"
]
}
}
}
Frequently asked questions
Upriver is categorized under Research and uses a remote HTTP/SSE transport. Scholar MCP belongs to Research and uses a local stdio subprocess. Pick Upriver for research work and Scholar MCP for research.
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.
Upriver has no declared pricing — check the project's own site. Scholar MCP 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 upriver and scholar-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Upriver has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Scholar MCP has 41/100 (Fair) with 0 views, 0 installs and 5 GitHub stars.