Side-by-Side Model Context Protocol Comparison
DidWork vs Evidence
In-depth architectural comparison of the DidWork and Evidence 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
DidWork
Developer Tools · Remote HTTP/SSE
Quality: 30/100 (Emerging) | Auth: No auth required
Evidence
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose DidWork if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Evidence 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?
D
Choose DidWork 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).
E
Choose Evidence 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).
Feature & Specification Comparison
Tools & Capabilities Breakdown
DidWork Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Evidence Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
DidWork Configuration
Evidence Configuration