Discover +326 AI Coding apps & tools

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: Automatically generates OpenAPI documentation for connected MCP tools. Built-in OAuth 2.1 support secures exposed endpoints. Handles multiple MCP server configurations in one instance. Hot-reloading applies configuration changes without service interruption.

Cons: Requires a functioning MCP-compliant server and host environment. Deployments depend on host Node.js or container setup. Focuses on protocol bridging, not model-level feature additions.

Pros: Provides direct access to DevDocs.io documentation for models. Implements the Model Context Protocol for client compatibility. Installs via npm or runs with npx for quick setup.

Cons: Requires an active internet connection to query DevDocs API. Needs an MCP-compatible client such as Claude Desktop. Coverage limited to documentation present on DevDocs.io.

Pros: Exposes ZenML pipeline and run metadata to MCP clients for natural language queries. Provides model registry and artifact discovery through the MCP interface. Built on the Model Context Protocol for broad MCP client compatibility. Open-source codebase maintained by the ZenML team, enabling extensions.

Cons: Primarily read-only, no automated stack modification available currently. Requires an existing ZenML installation and Python environment. Accuracy of assistant explanations still depends on the connected LLM and prompts.

Pros: Automatically converts OpenAPI/Swagger into MCP tools. Loads specifications from local JSON/YAML or remote URLs. Supports API key and Bearer token authentication. Real-time synchronization keeps definitions current.

Cons: Generated tools mirror OpenAPI quality; incomplete specs reduce reliability. Requires an MCP host environment and a Node.js runtime. Generated endpoints need validation before production use.

Pros: Executes Qore snippets through MCP for live validation. Exposes runtime objects, classes, and global variables to clients. Uses standardized MCP tool definitions for client compatibility.

Cons: Requires a local Qore runtime installation to execute code. Needs an MCP-compliant client and configuration changes. Targeted solely at developers working within the Qore ecosystem.

Pros: Runs locally, keeping dataset files on the user’s machine. Native MCP integration enables direct AI-to-Stata command execution. Captures and returns Stata console output and error messages. Maintains session state across multiple turns for iterative work.

Cons: Requires a licensed local Stata installation. Installation and client setup use Node.js/npm and MCP configuration. Large-dataset performance depends on local hardware and model context limits.

Pros: Implements the Model Context Protocol for cross-client compatibility. Extensible architecture allows adding custom tool integrations. Runs on Node.js or Python, fitting common developer stacks. Developer-focused configuration simplifies server management.

Cons: Requires MCP-compatible clients; excludes non-MCP assistants. Installation relies on repository cloning and manual client configuration. Functionality depends on the client’s tool-invocation behavior.

Pros: Exposes stdio MCP servers via HTTP and Server-Sent Events. Supports multiple concurrent clients against one server instance. Configurable with JSON or YAML command and argument definitions. Runs cross-platform on any environment supporting Node.js.

Cons: Requires a Node.js runtime for deployment. Proxying preserves underlying server behaviour, not correcting outputs. Does not translate non-MCP protocols into MCP. Network exposure requires explicit deployment and access controls.

Pros: Graph-based indexing maps function, class, and variable relationships across projects. Uses tree-sitter parsers for accurate syntax and symbol extraction. Provides semantic, project-wide search results rather than isolated text hits. Runs locally and supplies graphs to MCP clients without cloud uploads.

Cons: Requires Node.js and an MCP-compatible client for full deployment. Value depends on using an AI assistant that accepts MCP data. Local server setup adds operational overhead for small projects.

Pros: Reduces invented APIs by supplying documentation context. Connects with MCP-compatible hosts like Claude Desktop and Cursor. Open-source, community-recognized tool for Roblox workflows.

Cons: Requires an MCP host and Node.js environment. Not an official Roblox product. Generated suggestions still require developer review.

Pros: Adds live Google search context to MCP-based agent workflows. Exposes news, image, video, and shopping search verticals. Simple environment-variable configuration for API key and CX. Lightweight Node.js server designed for embedded deployment.

Cons: Depends on Google Custom Search API availability and quotas. Requires an MCP-compatible host application to function. Returned results require downstream verification for accuracy.

Pros: MCP-native server enables standard AI-to-file-system communication. Semantic search finds code by meaning rather than keywords. Open-source design allows customization and community contributions. Compatible with Windows, macOS, and Linux environments.

Cons: Embedding generation requires an external API key, sending embedding requests off-host. Indexing time and performance scale with repository size and file count. Requires a Node.js environment and manual configuration in an MCP client.

Pros: MCP-native design lets AI clients invoke process management directly. Exposes PID-based termination and detailed CPU/memory inspection endpoints. Lightweight, focused utility with a public GitHub codebase.

Cons: Termination commands act immediately, requiring strict client approval. Process enumeration behavior can vary across operating systems. Requires a Node.js host and an MCP-compatible client.

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: MCP-native server for direct integration with MCP clients. Allows file I/O and code search from the local workspace. Open source on GitHub for inspection and contribution. Lightweight Node.js process suitable for local development.

Cons: Requires a Node.js environment to run. Local command execution demands active supervision. Depends on an MCP-compliant client for model access.

Pros: Produces structural metadata for classes, interfaces, traits, and methods. Searchable index avoids sending entire repositories to models. Integrates with MCP clients such as Claude Desktop. Open-source design allows code inspection and adaptation on GitHub.

Cons: Metadata accuracy depends on the local parsing engine and PHP version. Requires an MCP-compatible client and a local PHP environment. No automated refactoring; analysis and retrieval only.

Pros: Brings Orbit workspace queries into MCP-enabled assistants and editors. Exposes member notes, identities, and tags for direct lookups. Includes endpoints to create members and log activities via the API. Configurable as a tool inside MCP clients such as Claude Desktop.

Cons: Requires an MCP-compatible host such as Claude Desktop, Cursor, or Windsurf. Setup depends on Node.js and familiarity with npx or local builds. Modifying Orbit data succeeds only if the API key has permissions. Geared toward developer workflows rather than non-technical users.