Tech Radar
Curated list of MCPs, plugins, and hooks evaluated in practice.
| Ring | Meaning |
|---|---|
| Adopt | In production, predictable behavior |
| Trial | Actively tested, value likely |
| Assess | To explore, not enough hindsight |
| Hold | Identified issues — do not generalize |
Adopt
- context7 MCP
Fetches up-to-date library documentation from source. Replaces web search for versioned libraries (Leptos, Tokio…).
Trial
- LSP Plugin
Language server integration — type info, diagnostics, cross-file navigation on large codebases.
⚠ LSP server can fall out of sync after large refactors. Restart the server to recover.
- RTK Hook
CLI proxy that filters command output to reduce token consumption on repetitive dev operations.
⚠ Over-filtering on some commands causes Claude to rerun them differently, negating the savings.
Assess
- Serena MCP
Symbol-aware code intelligence via LSP as MCP tools (find_symbol, insert_after_symbol…). Potential replacement for the LSP plugin.
- Playwright MCP
Browser automation — navigation, clicks, screenshots, network interception. Cross-browser, test-oriented.
- Chrome DevTools MCP
Low-level browser access via CDP — console logs, network inspection, performance tracing. Complements Playwright for debugging.
- markitdown MCP
Converts PDF, Word, Excel, HTML, images to Markdown for LLM consumption.
- github MCP
PR management and issue tracking from Claude. Caution — actions are visible to others.
- postgres / mongodb MCP
Direct database queries. Useful for debugging and migration validation. Read-only access recommended.
Hold
- sequential-thinking MCP
Forces step-by-step decomposition. Sonnet and Opus already do this natively — adds token overhead with no observed benefit.