ai-dev-analytics
Related Servers
Alternatives to ai-dev-analytics
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA local-first MCP server that gives AI coding agents runtime visibility and AI-managed debug logging. It replaces blind print() debugging by turning runtime execution into causal chains, allowing agents to instantly locate bugs by finding missing .success events in Python and TypeScript code. Single binary with MCP, CLI, and HTTP interfaces.-
- AlicenseNot gradedqualityCmaintenanceContext intelligence for AI coding sessions. 7 MCP tools to score, compare, compress, build, and scan prompts across 9 AI tools. Rule-based, <5ms/prompt, all analysis runs locally.46MIT
- AlicenseNot gradedqualityDmaintenanceA 100% local development monitoring tool that captures browser console logs, network requests, and backend server output for analysis by AI assistants via MCP. It enables LLMs to debug applications by providing structured, real-time access to full-stack log data and persistent local storage.5 npm7MIT

Vibgrate AI Contextofficial
AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that gives AI assistants codebase intelligence—code graph, drift analysis, vulnerability attribution, and version-correct library docs—all from the user's machine.1,569 npm3Apache 2.0- FlicenseNot gradedqualityAmaintenanceProvides real-time monitoring of AI agents, context, usage limits, workflows, files, Git, tests, builds, errors, secrets, and model-economy advice for tools like Claude Code, Codex, and Cursor, with 30 MCP tools for comprehensive observability.1-
- AlicenseBqualityDmaintenanceLocal production engineering platform that indexes Python codebases and exposes semantic code analysis, git risk scoring, and log correlation through MCP tools for AI assistants.19MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose with no overlap: bug fixing, highlighting achievements, logging bugs/deviations/files/reviews/rules, checking status, and managing tasks. The descriptions explicitly define when to use each tool, eliminating any ambiguity.
All tools follow a consistent 'aida_' prefix with descriptive snake_case names (e.g., aida_log_bug, aida_task_start). The naming pattern is uniform throughout, making it easy to predict and understand tool functions.
With 10 tools, the server is well-scoped for AI development analytics, covering key aspects like bug tracking, task management, file logging, and rule documentation. Each tool serves a specific, necessary function without bloat.
The tool set provides complete coverage for the AI development lifecycle, including task initiation/completion, bug logging/fixing, file change tracking, code review logging, deviation analysis, rule documentation, status checks, and highlighting achievements. No obvious gaps exist for this domain.