{"id":"tma1-ai-devtap","name":"devtap","af_score":65.8,"security_score":54.5,"reliability_score":32.5,"what_it_does":"devtap captures stdout/stderr from local build/dev commands, stores pending output per AI adapter, and exposes those captured build errors to AI coding tools via an MCP-compatible stdio server (or via a CLI skill fallback). It can also fan out output to multiple agents and supports cross-machine workflows using an optional GreptimeDB-backed session store.","best_when":"You run AI coding tools that support MCP (or compatible adapters) and you want a tight feedback loop from build/dev stderr/stdout into automated error-fixing sessions, including multi-agent and cross-machine scenarios.","avoid_when":"You need hard guarantees about data sanitization against malicious log content, or you require a networked hosted API/web service rather than a local MCP/stdio workflow.","last_evaluated":"2026-03-30T15:39:37.197309+00:00","has_mcp":true,"has_api":false,"auth_methods":["No authentication for local stdio MCP (implicit trust in local user/process).","GreptimeDB credentials via environment variables (DEVTAP_GREPTIMEDB_USERNAME/DEVTAP_GREPTIMEDB_PASSWORD) when using the GreptimeDB store."],"has_free_tier":false,"known_gotchas":["MCP tool calls require running `devtap install --adapter <adapter>` in the project root and restarting the AI tool session.","Cross-machine/multi-source drain can emit warnings when some sources are unreachable; agents should handle partial availability.","Filtering options (regex/sql) are convenience features and not a security boundary; malicious content handling is not guaranteed."],"error_quality":null}