CiteNexus vs ResearchZosho
A side-by-side look at the CiteNexus and ResearchZosho MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CiteNexus for research work as a local process; choose ResearchZosho 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 CiteNexus when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
Choose ResearchZosho when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RESEARCHZOSHO_DRIVE, RESEARCHZOSHO_MODEL, RESEARCHZOSHO_JUDGE_DRIVE, RESEARCHZOSHO_JUDGE_MODEL, RESEARCHZOSHO_EMBED, RESEARCHZOSHO_LIBRARY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 40/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | RESEARCHZOSHO_DRIVERESEARCHZOSHO_MODELRESEARCHZOSHO_JUDGE_DRIVERESEARCHZOSHO_JUDGE_MODELRESEARCHZOSHO_EMBEDRESEARCHZOSHO_LIBRARY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View CiteNexus | View ResearchZosho |
Tools & capabilities
CiteNexus tools
No tool names declared yet. Check the project README from the listing page.
ResearchZosho 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.
CiteNexus
{
"mcpServers": {
"citenexus": {
"command": "uvx",
"args": [
"--from",
"cite-nexus-mcp==0.2.3",
"cite-nexus-mcp"
]
}
}
}
ResearchZosho
{
"mcpServers": {
"researchzosho": {
"command": "npx",
"args": [
"-y",
"@wyrdsekai/researchzosho-mcp"
],
"env": {
"RESEARCHZOSHO_DRIVE": "YOUR_RESEARCHZOSHO_DRIVE_HERE",
"RESEARCHZOSHO_MODEL": "YOUR_RESEARCHZOSHO_MODEL_HERE",
"RESEARCHZOSHO_JUDGE_DRIVE": "YOUR_RESEARCHZOSHO_JUDGE_DRIVE_HERE",
"RESEARCHZOSHO_JUDGE_MODEL": "YOUR_RESEARCHZOSHO_JUDGE_MODEL_HERE",
"RESEARCHZOSHO_EMBED": "YOUR_RESEARCHZOSHO_EMBED_HERE",
"RESEARCHZOSHO_LIBRARY": "YOUR_RESEARCHZOSHO_LIBRARY_HERE"
}
}
}
}
Frequently asked questions
CiteNexus is categorized under Research and uses a local stdio subprocess. ResearchZosho belongs to Research and uses a local stdio subprocess. Pick CiteNexus for research work and ResearchZosho 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.
CiteNexus has no declared pricing — check the project's own site. ResearchZosho 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 citenexus and researchzosho as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CiteNexus has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. ResearchZosho has 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.