In-depth architectural comparison of the Andrea9293 MCP and Wikipedia Trends MCP 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: 61/100 (Good) | Auth: No auth required
Wikipedia Trends MCP
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Andrea9293 MCP if you need specialized Developer Tools tools running via a local process. Choose Wikipedia Trends MCP if your workspace requires Developer Tools integration with remote web transport. 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, Wikipedia Trends MCP belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Andrea9293 MCP when you need capabilities focused on developer tools and Wikipedia Trends MCP 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`)
Wikipedia Trends MCP Tools (3)
get_time_series
Weekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.
get_growth
Point-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.
get_top_trends
Live ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).