Andrea9293 MCP vs Wick — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Andrea9293 MCP vs Wick
In-depth architectural comparison of the Andrea9293 MCP and Wick 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
Wick
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 Wick 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, Wick belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Andrea9293 MCP when you need capabilities focused on developer tools and Wick 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`)
Wick Tools (6)
wick_fetch
Fetch any URL and get clean, LLM-friendly markdown. Sites that block standard HTTP clients return full content because Wick uses Chrome's actual TLS fingerprint.
wick_crawl
Crawl a website starting from a URL. Follows same-domain links, fetches each page through Chrome's TLS pipeline, and returns markdown for every page.
wick_map
Discover all URLs on a site. Checks sitemap.xml first, then follows links.
wick_search
Search the web. Use `wick_fetch` to read any result in full.
wick_download
Download video and audio from Reddit, YouTube, Twitter, and 1000+ other sites. Powered by yt-dlp.