Discover +306 AI Coding apps & tools

Pros: High-throughput Go capture engine for stable packet processing. Multi-protocol capture including HTTP, HTTPS, WebSocket, TCP, and UDP. MCP integration enables programmatic AI-driven analysis of captured data. Process-level filtering isolates traffic from specific applications.

Cons: Requires installing a local root certificate for HTTPS plaintext inspection. Windows-only, depends on the .NET framework for the UI. AI-driven analysis outputs require independent verification.

Pros: Accepts .pftrace and .perfetto-trace standard Perfetto formats. Allows AI agents to execute PerfettoSQL queries against loaded traces. Includes Chrome jank analysis and page-load summary tooling.

Cons: Requires an MCP-compliant client for full functionality. Needs Node.js or Rust environment for deployment. Specialized, not aimed at non-technical users.

Pros: Natural language control that edits Particle System parameters via conversational commands. Supports 24 core Particle System modules, covering emission, shape, velocity, and color. Applies changes instantly in the Unity scene for immediate visual feedback. Installs through OpenUPM or Unity Package Manager, fitting standard Unity workflows.

Cons: Requires an MCP-compatible host, so it is not a standalone Unity plugin. Edit precision depends on the AI model's understanding of Unity parameters. Command and file handling is governed by the chosen MCP host's policies. Complex or production-ready effects require manual artist refinement after generation.

Pros: Native Swift implementation using macOS system APIs. Exposes shortcuts as standard MCP tools for compatible clients. Runs locally, keeping shortcut data and execution on the host. Open-source codebase permits inspection and community contributions.

Cons: Requires macOS 14.5 or later to operate. Building from source requires Xcode 16.x. AI can trigger shortcuts but cannot inspect their internal logic. Only works with AI clients that support the Model Context Protocol.

Pros: OpenAI-compatible single endpoint eases migration for existing client libraries. Built in Rust, low resource overhead during API routing. Health monitoring exposes server availability for operational visibility. Supports local, air-gapped deployments to keep data on-premises.

Cons: Depends on LlamaEdge-compatible API servers, requiring backend setup. Custom web UI requires configuration before it is served. Gateway preserves backend outputs, necessitating independent model validation.

Pros: Exposes Frida functions to AI clients via the Model Context Protocol. Automated TypeScript agent scaffolding reduces boilerplate for new projects. Integrated REPL enables immediate script testing and iterative debugging. Unified CLI centralizes server, script, and process control.

Cons: Requires local Python 3.x and Node.js toolchain. Generated hooks need manual validation on complex targets. Functionality depends on correct Frida server setup on targets.

Pros: Processes data locally inside the browser, avoiding remote uploads. Single-file distribution supports offline use and fast loading. MCP integration lets AI models call specific utilities during sessions.

Cons: Large catalog requires time to locate the right utility. Not intended as production cryptographic key management. Interface density can overwhelm newcomers without curation.

Pros: Hot reloading applies saved script changes without restarting the server. Sandboxed Starlark runtime enforces deterministic, isolated execution. Built-in modules for HTTP, SQL, JSON, and time simplify integrations. Single portable executable across major desktop platforms.

Cons: Requires an MCP-compliant client for full functionality. System command execution requires explicit whitelist configuration. Starlark's simplified dialect omits some Python standard behaviors.

Pros: Local MCP server exposes saved snippets to desktop AI assistants. Supports JavaScript, Python, and Rust snippet storage. Native desktop client with automatic light and dark theme following. One-click clipboard integration for fast insertion into editors.

Cons: Requires a compatible desktop AI client to unlock AI-context features. Benefit depends on the quality and configuration of the external assistant. No cloud sync described, limiting seamless multi-device access.

Pros: Maintains a live shell session so state persists across turns. Provides structured table outputs that aid model parsing. Built-in modules for Kubernetes, Tmux, and Git extend automation. Rust implementation improves performance and memory safety.

Cons: Requires Nushell installed and present on the system PATH. Sandboxing reduces risk but does not replace manual command review. Needs an MCP-compliant client to connect, such as a desktop client.

Pros: Exposes GNS3 through MCP for direct LLM interaction. Supports CRUD plus batch and wildcard node operations. SSH automation for over 200 device types, multi-vendor coverage.

Cons: Needs a running GNS3 instance to operate. Automated outputs require operator validation before deployment. Optimized for Windows; other hosts need Docker or Python MCP setup.

Pros: Local operation keeps OmniFocus database access on the Mac. Project health detection surfaces active, on-hold, and stalled states. Time-aware queries respect deferred starts and due dates. Works with any MCP-compatible client such as Claude Desktop.

Cons: Primary focus is querying and retrieval, not task creation. Requires macOS with OmniFocus installed. Installation needs basic command-line edits to MCP settings. AI client may process queries off-machine for generation.

Pros: Real-time hit/miss analytics reveal cache behavior per session. Automated cache_control breakpoint injection reduces manual cache logic. Native MCP integration plugs into Claude Desktop and Cursor. Open-source codebase enables inspection and community contributions.

Cons: Limited to Anthropic models that support prompt caching. Requires an MCP-capable client plus a valid Anthropic API key. Session-level savings reporting may not reflect organization-wide usage.

Pros: Programmatic access to project internals for automated audits. Supports live editor routes and headless manipulation via MCP. Read-only HTTP dashboard provides real-time project status. Designed specifically for Godot 4.x projects and workflows.

Cons: Requires an MCP-compatible client to connect. Limited to Godot 4.x, not backward compatible with Godot 3.x. Server process setup adds deployment overhead for small teams. Generated edits require manual verification before committing.

Pros: Supports OpenAI, Anthropic, Google Gemini, and Mistral APIs. Native Ollama support enables local inference and offline runs. Acts as a Model Context Protocol server for editor integrations. Configurable via CLI commands or environment variables.

Cons: Requires a Node.js environment and npm or yarn familiarity. Command-line interface assumes developer experience, not casual users. Plugin extensibility requires custom development to add tools.

Pros: Self-hosted design keeps execution and data under local control. Horizontal scaling via worker nodes supports increased throughput. Native MCP integration for direct model-to-sandbox interactions. One-click Linux installer plus Docker deployment options.

Cons: Requires Linux hosting or Docker for straightforward deployment. Runtime library parity needed to reproduce outputs reliably. TLS is recommended for external traffic, adding operational steps. License specifics require review on the project repository.

Pros: Maps user journeys from source code and database schemas. Acts as an MCP server for AI assistants like Claude. Offers a Free Local Audit to keep code on-device. Installs via PyPI and runs on Python 3.x environments.

Cons: Business-centric focus may not replace dedicated security scanners. Generated plans require developer review before implementation. AI-assistant integration depends on MCP-enabled environments.

Pros: Lists and extracts VBA modules for code review. Writes or overwrites module source via MCP. Supports .xlsm, .docm, and .pptm file formats. Creates backups before modifying VBA components.

Cons: Macro execution still requires the Office host applications. Does not support Microsoft Access .accdb or .mdb files. Injected code depends on AI output quality and needs review.

Pros: Type-directed transpilation maps dynamic Python types to static Rust types. Memory-safety checks enforce ownership and borrowing before compilation. Single-command CLI generates native Rust binaries from Python files. MCP integration enables AI agents and IDEs to call the tool programmatically.

Cons: Approximately 20% of cases may require manual debugging after transpilation. Third-party C-extensions and highly dynamic libraries need manual adjustment. Requires an existing Rust toolchain (rustc and cargo) to produce binaries.