In-depth architectural comparison of the Roslyn Codelens MCP and AI Dev Analytics 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
Roslyn Codelens MCP
Monitoring · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
AI Dev Analytics
Monitoring · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Roslyn Codelens MCP if you need specialized Monitoring tools running via a local process. Choose AI Dev Analytics if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Roslyn Codelens MCP when:
You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Roslyn-based semantic symbol analysis, Call graphs and type hierarchy inspection, Diagnostics, code fixes, and refactoring actions.
You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: NODE_ENV.
Primary tools included: One-stop governance skill to detect duplicate, conflicting, or obsolete AI rules, Layered decision memory with automatic loading in Claude Code, Local dashboard showing AI asset inventory including rules, skills, decisions, and plugins.
⃣ 🏠 🍎 🪟 🐧 - Roslyn-based MCP server with 22 semantic code intelligence tools for .NET. Type hierarchies, call graphs, DI registrations, diagnostics, code fixes, complexity metrics, and more. Sub-millisecond lookups via pre-built indexes.
An open-source observability layer for AI coding. Silently tracks dev tokens/time and auto-codifies AI deviations into persistent project rules.
Category & Scope
Tools & Capabilities Breakdown
Roslyn Codelens MCP Tools (6)
Roslyn-based semantic symbol analysis
Call graphs and type hierarchy inspection
Diagnostics, code fixes, and refactoring actions
Test coverage and skeleton generation
API, architecture, and code-quality audits
External assembly and IL inspection
AI Dev Analytics Tools (6)
One-stop governance skill to detect duplicate, conflicting, or obsolete AI rules
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).
Roslyn Codelens MCP is categorized under Monitoring and uses a local stdio subprocess. In contrast, AI Dev Analytics belongs to Monitoring using local stdio subprocess. Select Roslyn Codelens MCP when you need capabilities focused on monitoring and AI Dev Analytics when you require tools for monitoring.