Doc Scraper vs Sem — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Doc Scraper vs Sem
In-depth architectural comparison of the Doc Scraper and Sem 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
Doc Scraper
Developer Tools · Remote HTTP/SSE
Quality: 41/100 (Fair) | Auth: No auth required
Sem
Developer Tools · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Doc Scraper if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Sem 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 Doc Scraper when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Doc Scraper is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Sem belongs to Developer Tools using local stdio subprocess. Select Doc Scraper when you need capabilities focused on developer tools and Sem when you require tools for developer tools.