Cite Caddy vs Tooluniverse — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cite Caddy vs Tooluniverse
In-depth architectural comparison of the Cite Caddy and Tooluniverse MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Cite Caddy
Research · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Tooluniverse
Research · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Cite Caddy if you need specialized Research tools running via a local process. Choose Tooluniverse if your workspace requires Research integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cite Caddy when:
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
query` defaults to Zotero's quick search (title/creator/year); `full_text=True` also matches indexed content of attached files/notes (`qmode="everything"`), requires non-empty `query`. Each result's `creators` is a list of `{creatorType, firstName, lastName}` (or `{creatorType, name}` for single-fi…
get_item
creators` shape as above.
list_collections
list_tags
list_trash
creators` shape as above.
list_saved_searches
list_groups
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Cite Caddy is categorized under Research and uses a local stdio subprocess. In contrast, Tooluniverse belongs to Research using local stdio subprocess. Select Cite Caddy when you need capabilities focused on research and Tooluniverse when you require tools for research.