In-depth architectural comparison of the AI Dev Analytics and Percept 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
AI Dev Analytics
Monitoring · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Percept
Monitoring · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose AI Dev Analytics if you need specialized Monitoring tools running via a local process. Choose Percept 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 AI Dev Analytics 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).
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.
An open-source observability layer for AI coding. Silently tracks dev tokens/time and auto-codifies AI deviations into persistent project rules.
AI-powered observability platform for agents. Auto-discovers and recommends MCP servers; built-in connectors for GA4, Vercel, GitHub, and Sentry with ROI tracking. npx -y @perceptdot/core
AI Dev Analytics is categorized under Monitoring and uses a local stdio subprocess. In contrast, Percept belongs to Monitoring using local stdio subprocess. Select AI Dev Analytics when you need capabilities focused on monitoring and Percept when you require tools for monitoring.