Discover +318 AI Coding apps & tools

Pros: Bridges AI agents to 22+ enterprise tools including Jira and Slack. Built-in PII sanitization to reduce sensitive data exposure. Write-safety and audit logs provide monitored, reviewable interactions. User-level YAML policy hooks enable per-account policy enforcement.

Cons: Requires MCP-compatible environment and on-premises operations expertise. Policy and connector setup needs YAML and integration knowledge. Geared toward IT and developer teams, not non-technical end users.

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: 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: Automatically captures stdout and stderr from terminal commands. Fans out the same build output to multiple AI agents in parallel. Deduplicates and tags multi-source output from local and remote hosts. Go-based binary runs on macOS, Linux, and Windows.

Cons: Full automation requires an MCP-compliant host. CLI fallback reduces unattended behavior for non-MCP agents. Oriented toward developer workflows, not general users.

Pros: Fetches schemas directly from the loft-sh/vcluster GitHub repository. Accepts an optional version parameter for release-specific queries. Runs via npx or remote HTTP without local schema management. Formats schema data with type context and relevance ranking for LLMs.

Cons: AI-generated manifests require human verification for production use. 15-minute in-memory cache can delay visibility of very recent changes. Integration requires an MCP-compliant client or the included CLI.

Pros: Local-first operation keeps prompts and code on the developer's machine. Turn-by-turn token breakdown shows input, output, cache reads, and thinking-budget tokens. Context-fill prediction flags approaching limits at 55–79% to avoid interruptions. CI/CD gates can fail pull requests that trigger unexpected billing spikes.

Cons: Requires MCP-compliant clients to integrate with existing agents. Source builds need Rust 1.88+ for compilation. Local-first model limits automatic, centralized, cross-team aggregation. Per-turn billing metrics require human interpretation before action.

Pros: Implements a sample MCP server for Gemini CLI tool integration. Provides gemini-extension.json and example server code for customization. Supports single-command install and Node.js local testing. Includes GitHub Actions workflows for automated builds and releases.

Cons: Contains a single proof-of-concept tool, not a catalog of utilities. Requires Node.js and a configured Gemini API key to run. Documentation assumes developer familiarity with MCP and Node.js.

Pros: Runs embeddings locally with ONNX Runtime, keeping code on-device. AST-aware chunking returns logical code blocks for tighter context. Hybrid search combines vector similarity with BM25 keyword matches.

Cons: Requires an MCP host environment and Node.js runtime. Depends on local compute for embedding generation via ONNX. Integration needs ongoing service administration and model files.

Pros: Marked speed gains for repeated queries compared to linear search. LLM-optimized output with Markdown and token-aware truncation. Git-aware filters, including changed-files and recent-commit scopes.

Cons: Not intended as a drop-in replacement for one-off ripgrep searches. Requires Rust 1.85 or newer to build from source. Initial automatic index build can delay the very first search.

Pros: Centralized dashboard that avoids manual JSON file edits. Supports desktop, web, and Docker deployments. Manages environment variables and API keys securely. Modular clean-architecture simplifies adding integrations.

Cons: Requires developer expertise for custom extensions. Discovery depends on quality of external MCP endpoints. Not targeted at non-technical end users.

Pros: Implements MCP server for direct model-to-project communication. Parses UE5 C++ reflection data and macros for context-aware retrieval. Companion Unreal Editor plugin extracts .uasset metadata for models. Compatible with MCP clients such as Claude Desktop and Claude Code.

Cons: Requires JetBrains Rider and an Unreal Editor bridge. Relies on local project integration, limiting quick ad hoc use. Generated code still needs human verification for build/runtime correctness.

Pros: Exposes all ten core spec-kit tools via MCP access. Rust core with Tokio for efficient, asynchronous tool invocation. Available through Cargo and npm for multiple developer environments.

Cons: Requires GitHub spec-kit Python CLI and uv package manager. Depends on an MCP-compatible host environment for AI agent access. Initial dependency setup may require internet connectivity.

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: 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: 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.