Discover +326 AI Coding apps & tools

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: 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: MCP bridge connects AI models directly to VICE's binary monitor. Enables low-level memory and register experimentation inside an emulator. Supports automated breakpoint-driven debugging and live execution. Runs in Node.js and integrates with MCP-compatible hosts like Claude Desktop.

Cons: Requires VICE configured with the binary monitor; extra emulator setup. Depends on external model quality for accurate 6502 opcode generation. Basic command-line and Node.js knowledge required to run.

Pros: Open-source codebase allows community review and contributions. Supports Sublime Text 3 and 4 on Windows, macOS, and Linux. Exposes editor content and project metadata to MCP workflows.

Cons: Requires an external MCP-compliant server to function. Server connections configured via JSON, needing manual edits. No bundled AI model; models run on external servers.

Pros: Native Model Context Protocol implementation for MCP compatibility. Direct GitHub API access for repository and issue operations. Open-source project with community-driven development and transparency. Compatible with MCP clients such as Claude Desktop.

Cons: Requires a GitHub Personal Access Token for authenticated operations. Needs Node.js and MCP host setup knowledge to deploy. Automated repository changes require human review to avoid unintended edits.

Pros: Displays raw JSON-RPC payloads for direct debugging. Passes traffic unchanged while recording exchanges. Runs on-demand and integrates into existing server commands. Compatible with Windows, macOS, and Linux via stdio.

Cons: Primarily limited to stdio transport for local MCP servers. Requires a Node.js runtime in the environment. Scope is niche, focused on the MCP ecosystem.

Pros: Finds exact symbol definitions across a repository. Provides type-aware answers using local Go analysis. Integrates with MCP clients such as Claude Desktop. Open-source codebase hosted on GitHub.

Cons: Requires a local Go installation to analyze code. Depends on MCP client configuration for model connectivity. Adds setup steps to developer workflow. Focused on Go; not for other languages.

Pros: MCP-native design for integration with MCP-compliant hosts like Claude Desktop. Exposes member authorization and metadata updates via natural-language commands. Node.js implementation, described as lightweight and straightforward to deploy.

Cons: Primarily built for the hosted Central API, limited self-hosted controller support. Requires an MCP client and Node.js environment to operate. Authorization commands perform live changes; test before production use.

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: Direct memory Peek/Poke access for programmatic read/write and code injection. Real-time execution control: start, stop, and single-step from MCP clients. Screen buffer and CPU register access let agents observe visual and processor state. Node.js architecture and open-source code allow community extension and auditing.

Cons: Requires VICE x64sc with remote monitor and Node.js setup before use. Focuses on C64 (x64sc); other Commodore machines are not currently supported. Documentation does not specify data retention or whether messages train models.

Pros: Decorator-based API reduces boilerplate for MCP endpoints. Automatic schema generation from Python type hints. Supports both synchronous and asynchronous handlers. Compatible with standard MCP transports including stdio.

Cons: Targeted to the MCP ecosystem, limiting general applicability. Requires Python 3.10 or higher at runtime. Abstracts the SDK, reducing low-level protocol access.

Pros: Produces machine-readable structures from fetched web pages. Designed specifically for the Model Context Protocol (MCP) integration. Runs locally, enabling in-environment processing and auditing. Open-source repository allows code inspection and custom parsing.

Cons: Extraction degrades on sites with heavy anti-bot or client-side rendering. Requires MCP-compatible host and Node.js configuration. Focused scope, not a full web-browsing replacement.

Pros: MCP compliance enables direct integration with clients like Claude Desktop. Exposes traceroute, ping, DNS lookup, and whois to AI assistants. Lightweight TypeScript/Node.js server with extensible design.

Cons: ICMP-based probes may require elevated OS privileges. Requires a Node.js environment and an MCP-compliant client. Limited to MCP-enabled AI workflows rather than generic remote services.

Pros: Allows AI assistants to query Trunk.io logs and distributed traces. Supports targeted event and error search for focused troubleshooting. Open-source server lets teams inspect proxy behavior and contribute.

Cons: Requires an MCP-compatible client like Claude Desktop or Cursor. Depends on Trunk.io API access; no telemetry without account access. Assistant outputs require manual verification against original logs.