Discover +299 AI Coding apps & tools

Pros: Exposes project structure so LLMs can reference in-session project state. Supports TypeScript and JavaScript script generation tied to engine APIs. Built on the Model Context Protocol for MCP client interoperability. Recognized by the Cocos Creator community for pioneering MCP integration.

Cons: Optimized for Cocos Creator 3.x, older projects may need adaptation. Requires an MCP-compatible host such as Claude Desktop for typical use. Generated code and scene edits require manual review and testing. Open-source community project, not an official Cocos product.

Pros: Fetches live documentation from the Terraform Registry API. Delivers resource and data source argument details to models. Supports retrieval for specific provider versions. Open-source codebase enabling community auditing.

Cons: Limited support for private registries in current implementation. Requires an MCP host and Node.js to run the server. Queries Registry API rather than validating local CLI state.

Pros: Programmatic access to Datadog telemetry for AI agents. Open-source implementation of the Model Context Protocol. Designed for integration with MCP-compatible clients. Supports region-specific Datadog endpoints.

Cons: Requires Node.js environment and developer setup. Depends on correct API and Application key management. Read-only focus limits in-place monitor modifications. Relies on agent query quality for accurate outputs.

Pros: Provides live crates.io lookups for assistants. Reads local project structure for context-aware suggestions. Integrates with Cargo for dependency-aware responses.

Cons: Requires an MCP-compliant client to operate. Internet required for external crate searches. Functionality is limited to the Rust ecosystem.

Pros: Exposes eBPF telemetry to MCP clients for live model analysis. Compatible with Kubernetes clusters and standalone Linux hosts. Registers existing Inspektor Gadget gadgets as callable functions. Built on a CNCF Sandbox project with community engagement.

Cons: Requires ig or kubectl-gadget binaries installed separately. Security hinges on granted execution permissions and network access. Needs an MCP-compatible client such as Claude Desktop. AI findings require human validation before production changes.

Pros: Native MCP integration for AI-assisted editors. Generates framework-ready component boilerplate. Lightweight server optimized for low-latency interactions. Open-source, developer-friendly implementation.

Cons: Requires an MCP-compatible host and Node.js runtime. Output quality depends on prompt clarity and model selection. Generated code commonly needs manual refinement before production.

Pros: Documentation authored by the Peacock extension's creator. Machine-readable docs let assistants reference official guidance. Multiple deployment paths: npx, Docker, or build from source. Designed to plug into existing MCP hosts for AI clients.

Cons: Scope limited to Peacock documentation and color configuration. Requires an MCP host plus Node.js/NPM or Docker environment. Companion tool only; does not replace the Peacock extension.

Pros: MCP-compatible, connects directly to clients like Claude Desktop. TypeScript codebase improves maintainability and type safety. Uses ConoHa API credentials for explicit authentication. Maintained under the official GMO Internet GitHub organization.

Cons: Limited to status retrieval and start/stop/reboot actions. Requires Node.js and an MCP-compatible client to run. No built-in lifecycle actions such as server deletion.

Pros: Native Model Context Protocol support for AI clients. Handles common configuration formats including JSON and YAML. Open-source design, allowing code inspection and extension.

Cons: Requires a Node.js runtime and an MCP-compatible client. Focused on configuration files, not general file management. Early MCP adopter, may need custom adapters for niche tools.

Pros: Direct access to Verse API documentation for model queries. Local Node.js server reduces latency for context retrieval. Provides curated Verse snippets and boilerplate patterns. MCP compatibility enables connection with Claude Desktop.

Cons: Requires Node.js and an MCP-compatible client to operate. Scope limited to Verse and UEFN, not general-purpose coding. Documentation currency depends on repository maintenance.

Pros: Uses local kubeconfig so actions respect existing RBAC. Integrates with MCP clients such as Claude Desktop for in-chat diagnostics. Go implementation aligns with Kubernetes client libraries for efficient execution.

Cons: Cluster compatibility depends on installed kubectl version. Mutating operations depend on tools exposed in the Go code, requiring review. Requires an MCP-compatible client and local kubectl to operate.

Pros: Automates Master Code detection, removing manual hexadecimal searches. Parses Action Replay, GameShark, and CodeBreaker into PNACH. Batch processing for handling multiple code strings at once. Portable Windows tool with no complex installation required.

Cons: Windows-only, requires a .NET-compatible runtime. Simple GUI may lack advanced code-editing controls. Users must understand PNACH usage to apply patches correctly.

Pros: Outputs Go Abstract Syntax Trees for machine-readable code representation. MCP-native, enabling direct connection with MCP-capable assistants. Read-only local file access preserves source integrity during parsing. Go-based server implementation reduces query latency for interactive sessions.

Cons: Requires the Go toolchain to resolve dependencies. Needs an MCP-capable client to be useful in workflows. Specialized to Go, not suited for multi-language repositories. Parsing completeness depends on local module resolution.

Pros: Unified API supporting OpenAI, Anthropic, Google Gemini, Mistral, and Groq. Native Model Context Protocol (MCP) server for tool and context sharing. Ollama integration enables running models on local hardware. Included CLI tools for direct experimentation and streaming output.

Cons: Generated output quality depends on the chosen model and prompt design. Requires a Go environment or the provided binaries for execution. Local model workflows need Ollama or equivalent runtime setup. Adoption requires familiarity with Go tooling and build processes.

Pros: File-system tools let models inspect and modify project files. Captures terminal output for traceable, reviewable action logs. Git-related utilities support commit and log inspection. Open-source repository allows community inspection and customization.

Cons: Requires an MCP-compliant host application and Node.js runtime. Grants powerful local access, so it needs trusted environments. Best for teams that can run and review a local server.

Pros: Implements MCP for direct AI-to-Revit connectivity. Exposes Revit API functions to AI clients for in-model queries. Open-source GitHub project allows code inspection and customization. Supports live interaction with MCP-compatible clients like Claude Desktop.

Cons: Requires an active Autodesk Revit installation. Intended for developers comfortable with Revit API and GitHub. Functions as a server/SDK, not a standalone end-user app.

Pros: Exposes NATS operations as standardized MCP tools for LLM invocation. Designed for low-latency use with NATS high-performance messaging. Compatible with any MCP host and with Claude Desktop integration. Open-source and extensible architecture for custom monitoring tools.

Cons: Current implementation focuses on core patterns; JetStream support unclear. Requires a running NATS cluster and a Node.js runtime. Assumes operator familiarity with MCP and messaging concepts.