Discover +337 AI Coding apps & tools

Pros: Implements MCP to present infrastructure context to AI clients. Allows discovery and inspection of Akamai Functions workloads. Supports macOS installation via Akamai Developers Homebrew tap. Maintained by Akamai, ensuring platform compatibility.

Cons: Limited to Akamai Functions and WebAssembly workloads. Requires an MCP-compliant client to consume context. Runs in Node.js or as a binary, requiring local setup. Does not replace human verification or CI/CD safeguards.

Pros: TOON format reduces token usage for model inputs. Add new tools by editing YAML without changing code. Runs via npx or Docker on Node.js hosts.

Cons: Token-optimized outputs can reduce human readability. Requires Node.js and an MCP-compatible environment. Automated decisions need schema validation for safety.

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: Compact JSON output reduces LLM token usage. Supports WIQL for custom work item queries. Uses local Azure CLI credentials for setup. Pre-built binaries for Windows, macOS, Linux.

Cons: Requires an MCP-compliant client to operate. Depends on local Azure credentials for authentication. Self-hosted server model needs developer configuration. Focused solely on Azure DevOps Boards workflows.

Pros: Consolidates multiple MCP servers behind one endpoint, reducing per-client configuration. Preset filtering limits tools sent to agents, cutting context noise and token use. Supports STDIO, HTTP, SSE, and WebSocket transports for mixed-protocol toolsets. Hot reloading plus dynamic OAuth registration eases runtime updates and onboarding.

Cons: Requires MCP-compatible clients; not useful outside the MCP ecosystem. Local deployment needs ongoing administration and MCP workflow knowledge. OAuth automation requires careful scope and credential management.

Pros: Shared console shows AI-generated commands in real time. Supports bash, PowerShell (pwsh), and Windows cmd shells. Session persistence keeps state across multiple interactions. Handles interactive CLI prompts that break one-shot integrations.

Cons: Requires an MCP-compatible host application to operate. Shared-session model may not suit strict separation or sandboxing needs. Built with ConPTY-based emulation, implying specific terminal emulation choices.

Pros: Sub-0.5 second full-project scans for large codebases. Bridges C++ source and binary engine assets for cross-boundary tracing. Operates entirely locally with no cloud calls or telemetry. Confidence Tiers label analysis reliability for agent consumption.

Cons: Requires an MCP-compatible agent or integration to unlock full value. CLI and server setup needs familiarity with Node.js or Python environments. LLM-powered architectural advice requires human verification before changes.

Pros: Executes native iOS gestures, not synthetic pointer events. Provides real-time UI element inspection and hierarchy data. Integrates with MCP-compatible clients such as Claude Desktop. Distributed under Apache-2.0, allowing contribution and inspection.

Cons: Requires iOS simulator or physical device for execution. Needs Node.js plus Swift components for full setup. Automation fragile when app UI changes frequently. Targeted to iOS only, not cross-platform mobile control.

Pros: Local SQLite storage preserves project context across sessions.. Rust binary keeps CLI overhead low during operations.. Includes clx-rules for project-specific policy management.. clx-doctor diagnoses empty-recall problems in long sessions..

Cons: Specialized for Claude Code, limited value outside that CLI ecosystem.. Requires a working Claude Code install and MCP support.. Installs as a system binary, adding an extra setup step.. Independent open-source project, not an official Anthropic product..

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: BM25, semantic vector, and regex search combined for precise retrieval. Indexes PDFs, Office files, images, and source code for unified lookup. Runs locally with built-in embedding model and SQLite storage. Implements MCP for compatibility with Claude Desktop, Cursor, and others.

Cons: Output reliability depends on freshness and curation of indexed repositories. Large multimodal archives increase indexing time and storage demands. Enterprise scale requires external vector databases and additional infrastructure.

Pros: Implements the Model Context Protocol for AI access to Bitbucket Cloud. Supports pull request creation, retrieval, and comment reading via API. Authentication via Bitbucket App Passwords or personal access tokens. Open-source codebase permits community inspection and security audits.

Cons: Limited to Bitbucket Cloud; no Server/Data Center support. Requires a Node.js runtime and MCP-compatible client. Repository deletion intentionally not exposed through provided endpoints.

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.