SuperAPI AI Directory

moth

Structured bug-fix analysis and project-local memory of verified fixes for coding agents.

Open website

About this tool

Purpose: Moth is a lightweight MCP server for project-local bug-fix analysis and verified fix memory, turning terminal errors into source-backed fix suggestions for AI coding agents.

Main capabilities: It receives error output via MCP, first redacts suspected secrets, then normalizes the failure information, identifies the likely tech stack, checks project-local fix memory, and finally returns a structured fix brief. It exposes only two MCP tools: analyze_error (analyzes the provided error output before attempting a fix, and can include context such as package_context, relevant_files, prior_project_fixes) and remember_fix_result (records verified project-local fix memory, requiring verification_command and verification_result, with values passed or failed; worked is derived from verification_result, and a public worked input will be rejected). Verified memory is stored project-locally, and there is also a small Moth-owned analysis registry kept outside the project to map analysis_id back to the correct project path after the MCP server restarts. It also includes skills for compatible agents: moth-debug-first-fix, moth-source-backed-research, moth-verify-fix.

Usage: Requires Node.js 18+, can be installed globally, and connected to supported AI agents via the general MCP configuration; when using it, you can attach a prompt next to the error message, for example "Use Moth to analyze this error before fixing it." Call remember_fix_result only when a fix was actually attempted, the verification command actually ran, and the result is clearly passed or failed; suggestions, skipped changes, missing verification, ambiguous results, or guesses should not be recorded.

Limitations: Moth does not edit code, does not execute shell commands, does not crawl repositories, does not require a backend, and does not maintain a global bug database; by default it is read-only, with no source code modification, no repository-level scanning, no background listening, and no external service dependencies. The MCP server itself does not perform real-time web retrieval; compatible agents can use their own search tools under the guidance of Moth skills to obtain externalsources. In supported clients, "local plugin ready" means the integration wrapper is already included and can be tested locally, but marketplace submission and approval are not yet included.