In-depth architectural comparison of the Andrea9293 MCP and Proxy4agents 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
Proxy4agents MCP
Developer Tools · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Andrea9293 MCP if you need specialized Developer Tools tools running via a local process. Choose Proxy4agents MCP 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, Proxy4agents MCP belongs to Developer Tools using local stdio subprocess. Select Andrea9293 MCP when you need capabilities focused on developer tools and Proxy4agents 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`)
Proxy4agents MCP Tools (9)
novada_proxy_fetch
Fetch any URL through a residential proxy. Returns structured JSON with content, status code, and metadata. Auto-retry on network errors. Caches repeated calls (default 300s TTL — `meta.cache_hit: true` means no proxy credit used).
novada_proxy_batch_fetch
Fetch 2–20 URLs concurrently through residential proxy. Up to 5x faster than sequential fetches. Per-URL errors are captured individually — the batch itself succeeds even if some URLs fail. Reuses response cache for URLs already fetched.
novada_proxy_extract
Extract structured fields from any URL using heuristic pattern matching (meta tags, Open Graph, JSON-LD, Schema.org). Lightweight — no LLM needed. Set `render_fallback: true` to automatically retry via real Chromium if the proxy fetch fails.
novada_proxy_map
Crawl a URL and return all internal links as a structured JSON array. Use as the discovery step before `novada_proxy_batch_fetch` to crawl an entire site without guessing URLs.
novada_proxy_session
Sticky session fetch — every call with the same `session_id` uses the same residential IP. Essential for login flows, paginated scraping, and price monitoring. Supports `verify_sticky: true` to confirm IP consistency before relying on it.
novada_proxy_search
Structured Google search via Novada Scraper API. Returns titles, URLs, and snippets as clean JSON — no HTML parsing needed.
novada_proxy_crawl
Recursively crawl a website via BFS traversal. Starts from a URL, discovers links at each depth level, and returns the full URL tree with metadata.
novada_proxy_research
One-shot research tool — searches the web, fetches top results, and returns structured findings with source previews. The agent can analyze the findings for deeper synthesis.
novada_proxy_status
Check proxy network connectivity and version. Makes a live proxy call to verify the connection is working. No credentials required.