Discover +335 AI Coding apps & tools

Pros: Schema introspection keeps API shape current for model clients. Read-only queries run dynamically against specified GraphQL endpoints. Environment variables support authenticated endpoints without code changes. Smithery install option for quick MCP server deployment.

Cons: Mutations disabled by default, need explicit environment toggle. Requires an MCP-compatible host to function. Deployment requires Node.js expertise and host configuration. Not a turnkey solution for unattended production write workflows.

Pros: Exposes MCP tools via an OpenAI-compatible /v1/chat/completions endpoint. Supports streaming and non-streaming chat completions for interactive sessions. Docker and Node.js installation options for cross-platform deployment. Open-source repository enables community auditing and customization.

Cons: Requires self-hosting; no official hosted service available. Depends on local MCP servers to provide tool behavior. Manual setup needs Node.js familiarity for non-container installs.

Pros: Project entities saved as Markdown inside the repository. Built-in MCP server lets agents read and update project state. Context layer compresses summaries to reduce token usage.

Cons: Compressed summaries can omit important details, needing review. Requires a Node.js environment to run locally. Works only with MCP-enabled clients or compatible extensions.

Pros: Causal chain analysis links CPU events to GPU execution.. Sub-microsecond tracing captures kernel-to-CUDA timelines.. Runs without modifying application code or container images.. MCP server lets AI agents query performance data directly..

Cons: Limited to NVIDIA GPUs in the CUDA ecosystem.. Requires Linux hosts for deployment.. Agent access to traces requires deliberate access controls.. Automated recommendations need human validation before rollout..

Pros: Provides 38 specialized tools for extracting Rails metadata. Verifies tables, columns, and indexes before migration suggestions. Maps model associations like has_many and belongs_to. Compatible with MCP clients such as Cursor and Windsurf.

Cons: Requires a Ruby on Rails environment and Node.js. Best suited to projects that follow standard Rails conventions. Interactive setup required before the MCP server runs. Read-only analysis, does not apply code changes automatically.

Pros: Generates images, video, music, and audio via Fal.ai models. Supports STDIO and HTTP/SSE transports for flexible client connections. Native asynchronous API with queue management for long-running jobs. Model discovery lets you browse over 600 available models.

Cons: Requires a Fal.ai API key; relies on external API for generation. Needs a Node.js environment for installation and deployment. Operations route through Fal.ai, so no documented local-only processing.

Pros: MCP Market enables browsing and one-click server installation. Visual configuration replaces manual .json file editing. Cross-client synchronization applies settings across clients like Claude Desktop. Multi-profile support for switching project-specific environments.

Cons: Preview phase, feature completeness and enterprise controls may be limited. Desktop-only on Windows and macOS; Linux not mentioned. Custom-server complexity and advanced workflow guarantees unspecified.

Pros: Uses Eclipse JDT for compiler-level type and binding resolution. Native support for Maven, Gradle, and Bazel project structures. Provides 63 specialized semantic analysis tools for deep inspection. Connects to MCP clients like Claude Desktop via executable configuration.

Cons: Requires a Java Runtime Environment and local server setup. AI-driven refactors still need human review for design correctness. Does not itself execute edits; an AI agent or user must apply changes.

Pros: OpenAI-compatible API lets existing clients work with local models. Dynamic worker discovery adds new local workers automatically. Least-busy routing balances requests across heterogeneous machines. Supports Ollama, vLLM, Docling, and Whisper integrations.

Cons: Requires operator familiarity with Docker and runtime deployment. Public server dependency for outbound connector tunnels. Not a turnkey SaaS, needs local maintenance and monitoring.

Pros: Instant Checkpoints let you snapshot project state before AI edits. One-Click Undo restores the project to the last stable state instantly. Secret Management masks API keys and sensitive credentials. Rust-powered core provides rapid file indexing and backup operations.

Cons: Native safety features require MCP-compliant AI tools for full integration. Not a substitute for full version control in production workflows.

Pros: Aggregates local and remote MCP servers into a single endpoint. Includes both a Terminal User Interface and a Web UI for monitoring. Supports stdio and Server-Sent Events transports for hybrid setups.

Cons: Requires a Node.js runtime on the host system. Best suited to users comfortable with server and namespace management. Operational governance needed to limit agent access across tools.

Pros: Generates local dependency manifests without uploading code. Interactive local web graphs for exploring architecture. Complexity audits identify technical debt and maintainability issues. Acts as an MCP server for AI-assisted tooling integration.

Cons: Language support currently limited to Python, C#, C, and Java. Automated findings require manual verification for large legacy codebases.

Pros: Supports Helm 3.x and Helm 4.x within a single binary. Implements credential memory zeroing for reduced sensitive-data retention. Accepts stdio and Server-Sent Events transports for local and web clients. Native Model Context Protocol integration for AI client compatibility.

Cons: Requires an MCP-compliant client to integrate with AI assistants. Needs a working Kubernetes environment and Helm installed locally. AI-generated operations require independent verification before apply.

Pros: Eleven retrieval tools provide focused document and sheet data. Read-only access protects document integrity during AI queries. Runs locally on Node.js across macOS, Linux, and Windows. Uses GCP OAuth2 credentials for authenticated API access.

Cons: Requires a Google Cloud project and credentials.json for authentication. Only compatible with MCP-compliant clients such as Claude Desktop. No write functions, so cannot automate document updates.

Pros: Roslyn-based C# parsing enables deep syntactic analysis. Custom XML resolver interprets ParentName and Name attributes. SQLite-based, high-concurrency indexing for rapid local searches. Local execution preserves privacy and offline core functions.

Cons: Requires an MCP-compatible client and a local RimWorld install. Specialized for RimWorld modding, not a general codebase searcher. LLM client may still require internet access for model queries. Setup and index maintenance require technical familiarity with .NET.

Pros: Stores all session logs locally in SQLite. Provider-agnostic summarization, supports OpenAI and Anthropic. Explicit start/end session markers for context recovery. Automates daily and weekly progress reports.

Cons: Requires an MCP host and a Node.js runtime. Summary accuracy depends on the selected external model. Installation can require cloning and building with TypeScript.

Pros: Reduces character count versus JSON, expanding usable LLM context windows. Optimized handling of tabular datasets commonly used in AI training. Strict TOON specification compliance enables cross-language parsing. Native support for Java 17 record types and modern collection APIs.

Cons: Requires Java 17 or newer runtime. Library-only model, not a standalone conversion service. Token savings are most pronounced with tabular data. Focused on MCP workflows, limited appeal outside that ecosystem.

Pros: MCP server enables AI assistants to access and analyze live logs. Multi-device sessions let you monitor several Android units simultaneously. Cross-platform GUI and CLI satisfy both visual and terminal workflows. Regex and fuzzy search help find variable or partial log matches.

Cons: AI-derived diagnoses require independent verification by developers. Relies on ADB connectivity and device permissions for log access. MCP mode exposes streamed logs to connected AI clients, requiring data-care decisions.

Pros: Local-first processing keeps repository source code on-device. Exposes a structured code graph to AI agents via MCP. Blast radius analysis highlights downstream impact across modules. Incremental indexing updates the dependency graph as edits occur.

Cons: Primary language support limited to Rust, Python, JavaScript/TypeScript. Requires an MCP-compatible client such as Claude Desktop to connect. Non-MCP workflows need custom integration to use the graph.