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