Andrea9293 MCP vs Mydisease — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Andrea9293 MCP vs Mydisease
In-depth architectural comparison of the Andrea9293 MCP and Mydisease 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
Andrea9293 MCP
Developer Tools · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Mydisease
Developer Tools · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Andrea9293 MCP if you need specialized Developer Tools tools running via a local process. Choose Mydisease if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Andrea9293 MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Andrea9293 MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Mydisease belongs to Developer Tools using local stdio subprocess. Select Andrea9293 MCP when you need capabilities focused on developer tools and Mydisease when you require tools for developer tools.
Lists files in the uploads folder with size and format info
get_ui_url
Returns the Web UI URL (e.g. http://localhost:3080) — useful to open the dashboard or to locate the uploads folder from the browser
search_documents
Semantic vector search within a specific document
search_all_documents
Hybrid (full-text + vector) cross-document search
get_context_window
Returns a window of chunks around a given chunk index
search_documents_with_ai
🤖 AI-powered search using Gemini (requires `GEMINI_API_KEY`)
Mydisease Tools (3)
query
Search MyDisease.info for diseases by free-text name or fielded query. Returns matching hits, each keyed by a MONDO disease id (e.g. "MONDO:0015967") with the best-matching ontology and annotation keys. Use this to resolve a disease name to canonical ontology ids before calling the "disease" tool.…
disease
Fetch the full aggregated annotation object for a single disease id. Accepts MONDO ("MONDO:0015967"), DOID ("DOID:9351"), OMIM ("OMIM:125853") and other supported ontology ids. Returns cross-referenced data including MONDO ontology (labels, synonyms, xrefs, parents/children), gene-disease associati…
metadata
Returns MyDisease.info build metadata: total disease document count, available annotation sources (MONDO, DOID, OMIM, DisGeNET, HPO, CTD), and their current release versions.