rails-mcp-server 1.1.3 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 02c77d8a0a509c668fbac9499082d11ab59e3acc3e8e06f9dcb932c37344efdb
-  data.tar.gz: 50ee750a4af047013fa27db79a82007c59668593f9b5efbb67fa2e5024df37e8
+  metadata.gz: d223ba6b32da76211f1b0316c76156453acfc25f86a2b2750949b5747cf4c2b2
+  data.tar.gz: c3bfbaa694738d88186f761c6053edffed7324d3a68a9168c91b63757250ad49
 SHA512:
-  metadata.gz: 83d380f54c9ad929e20a14f755d641687bced98349b6c7f1b8931077b55fab5a4f63992163ff017d836eb3ae67368573af88957c571fb13e1f8da2fdd9670451
-  data.tar.gz: 0aba6aa7ba7c0bb3e6e8439b60326a64bcbee080d81d981771857d12323ae522483464d1daae0a87f38d8abd115516a21f28c4880205a08316ccec596d17453f
+  metadata.gz: '08cf5e172f3ad00d8e8fbcca061bd5c06fd3a6dfcac6610849f3cf9dda86a10a4bfa6c254804309e421bc64370382fe4a90e0456b82c3aa1aa14214d5f0a8be8'
+  data.tar.gz: 6c8a18e379e46f5c3a55554f244b48b1f01477dc1283911f198c0876cbeeaa6fccb8dccb6a972cdc2a7a218b42a8e07e9928a3a2d8a457eafad4b33f625e995d

data/CHANGELOG.md

@@ -0,0 +1,209 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.2.0] - 2025-06-03
+
+### Added
+
+- **Comprehensive Resources and Documentation System**: Complete access to Rails ecosystem documentation
+  - `load_guide` tool for accessing official framework documentation
+  - Support for Rails, Turbo, Stimulus, and Kamal documentation
+  - Custom markdown file import capabilities
+  - Automatic resource downloading via `rails-mcp-server-download-resources` command
+  - Resource storage in XDG-compliant directories with manifest tracking
+- **Five Resource Categories**:
+  - **Rails Guides**: Official Ruby on Rails 8.0.2 documentation (50+ guides)
+  - **Turbo Guides**: Complete Hotwire Turbo framework documentation
+  - **Stimulus Guides**: Full Stimulus JavaScript framework documentation  
+  - **Kamal Guides**: Comprehensive Kamal deployment tool documentation
+  - **Custom Guides**: Import and manage your own markdown documentation
+- **Direct Resource Access**: MCP clients can query resources using URI templates
+  - `rails://guides/{guide_name}` for Rails documentation
+  - `turbo://guides/{guide_name}` for Turbo guides
+  - `stimulus://guides/{guide_name}` for Stimulus documentation
+  - `kamal://guides/{guide_name}` for Kamal guides
+  - `custom://guides/{guide_name}` for custom imports
+- **Advanced Resource Management**:
+  - Force download options (`--force`) for updating resources
+  - Verbose logging (`--verbose`) for troubleshooting
+  - Batch import support for directory structures
+  - Filename normalization for custom imports
+  - Version tracking and update management
+
+### Improved
+
+- **Enhanced Documentation**: All tools now include comprehensive natural language examples
+- **Resource Integration**: Seamless integration with existing MCP tool ecosystem
+- **File Organization**: Better project structure with XDG Base Directory compliance
+- **Error Handling**: Improved validation and error messages across resource operations
+
+### Technical
+
+- URI templating support for direct resource access
+- Enhanced manifest management for resource tracking
+- Integration with FastMCP for robust resource handling
+- Simplified guides configuration and management
+
+## [1.1.4] - 2025-05-02
+
+### Fixed
+
+- **HTTP Mode Issues**: Resolved Puma server startup failures in HTTP mode
+- **Rails Command Execution**: Fixed issues with executing Rails commands in certain environments
+- **Logger Configuration**: Fixed logger initialization when no config file exists (thanks to @justwiebe)
+
+### Changed
+
+- Improved dependency version constraints for better compatibility
+- Enhanced error handling for HTTP server operations
+
+## [1.1.0] - 2025-04-20
+
+### Added
+
+- **HTTP Server-Sent Events (SSE) Support**: Real-time communication capabilities
+  - HTTP mode with JSON-RPC and SSE endpoints (`--mode http`)
+  - Custom port configuration with `-p/--port` option
+  - SSE endpoint at `/mcp/sse` for real-time updates
+  - JSON-RPC endpoint at `/mcp/messages`
+- **New Analysis Tools**:
+  - `analyze_controller_views`: Analyze relationships between controllers, actions, and views
+  - `analyze_environment_config`: Compare environment configurations for inconsistencies and security issues
+- **Enhanced Integration**:
+  - MCP Inspector compatibility for testing and debugging
+  - Improved client compatibility through HTTP endpoints
+  - Better support for multiple LLM clients
+
+### Improved
+
+- **Code Organization**: Major refactoring using FastMCP gem
+  - Transition from mcp-rb to fast-mcp for better protocol support
+  - Enhanced modular architecture for better maintainability
+  - Improved error handling and validation across all tools
+- **File System Respect**: All tools now respect `.gitignore` files when scanning codebases
+- **Tool Enhancements**: Comprehensive review and improvement of all existing tools
+  - Better edge case handling for large projects
+  - Performance improvements for file operations
+  - Enhanced logging and debugging capabilities
+
+### Technical
+
+- **FastMCP Integration**: Complete migration to FastMCP gem for robust MCP protocol implementation
+- **Rack-based Architecture**: HTTP server implementation using Rack
+- **Event-driven Communication**: Real-time event handling for SSE support
+- **Improved Connection Management**: Better handling of client connections and message processing
+
+### Changed
+
+- **Internal Architecture**: Complete refactoring to use FastMCP instead of mcp-rb
+- **Command-line Interface**: Enhanced CLI with mode selection and configuration options
+- **Documentation**: Updated with detailed tool descriptions and usage examples
+
+## [1.0.0] - 2025-03-20
+
+### Added
+
+- **Initial Release**: Rails MCP Server for AI-assisted Rails development
+- **Core Tools** (8 tools):
+  - `switch_project`: Change active Rails project for multi-project support
+  - `project_info`: Get comprehensive Rails project information and structure
+  - `list_files`: Browse project files with glob pattern matching
+  - `get_file`: Retrieve file contents with syntax highlighting
+  - `get_routes`: Display all Rails routes (equivalent to `rails routes`)
+  - `analize_models`: Analyze Active Record models, associations, and relationships
+  - `get_schema`: Retrieve database schema information and table structures
+  - Basic file and project analysis capabilities
+- **Project Management System**:
+  - Multi-project support through `projects.yml` configuration
+  - XDG Base Directory Specification compliance for configuration
+  - Automatic project detection and setup
+  - Cross-platform compatibility (macOS, Windows)
+- **Claude Desktop Integration**:
+  - STDIO mode communication for direct integration
+  - Automatic setup script (`rails-mcp-setup-claude`)
+  - Ruby version manager compatibility documentation
+  - JSON-RPC 2.0 protocol implementation
+- **Developer Experience**:
+  - Comprehensive logging system with configurable levels
+  - Debug mode and verbose output options
+  - Robust error handling and validation
+  - Clear documentation and setup guides
+
+### Features
+
+- **Rails-Specific Intelligence**: Deep understanding of Rails application architecture
+  - Model relationships and Active Record associations analysis
+  - Controller and route mapping
+  - Database schema exploration and relationship discovery
+  - Rails convention-based file discovery
+- **Smart File System Integration**:
+  - Intelligent file discovery with glob pattern support
+  - Automatic respect for Rails conventions and `.gitignore`
+  - Syntax highlighting for various file types
+  - Efficient handling of large codebases
+- **Configuration Management**:
+  - Platform-specific configuration directories
+  - Project-based organization and switching
+  - Automatic initialization and setup
+  - Secure and isolated project environments
+
+### Technical Foundation
+
+- **Model Context Protocol (MCP)**: Full MCP specification implementation
+- **Communication**: JSON-RPC 2.0 protocol over STDIO
+- **Architecture**: Modular, extensible design for future enhancements
+- **Distribution**: Ruby gem packaging for easy installation and updates
+- **Compatibility**: Cross-platform support with platform-specific optimizations
+
+---
+
+## Version History Summary
+
+- **v1.2.0** (2025-06-03): Major documentation and resource system addition
+- **v1.1.4** (2025-05-02): Critical bug fixes for HTTP mode and Rails commands
+- **v1.1.0** (2025-04-20): HTTP SSE support and new analysis tools with FastMCP migration
+- **v1.0.0** (2025-03-20): Initial release with core Rails MCP functionality
+
+## Development Guidelines
+
+### Version Numbering
+
+This project follows [Semantic Versioning](https://semver.org/):
+
+- **MAJOR** version for incompatible API changes
+- **MINOR** version for backwards-compatible functionality additions  
+- **PATCH** version for backwards-compatible bug fixes
+
+### Release Process
+
+1. Update version in `lib/rails-mcp-server/version.rb`
+2. Update this CHANGELOG.md with new features and changes
+3. Update README.md and documentation if needed
+4. Create a git tag: `git tag -a v1.2.0 -m "Release version 1.2.0"`
+5. Push tags: `git push origin --tags`
+6. Build and publish gem: `gem build rails-mcp-server.gemspec && gem push rails-mcp-server-1.2.0.gem`
+
+### Changelog Categories
+
+- **Added** for new features
+- **Changed** for changes in existing functionality
+- **Deprecated** for soon-to-be removed features
+- **Removed** for now removed features
+- **Fixed** for any bug fixes
+- **Security** for vulnerability fixes
+- **Technical** for internal/technical improvements
+- **Improved** for enhancements to existing features
+
+---
+
+## Links
+
+- [Repository](https://github.com/maquina-app/rails-mcp-server)
+- [Releases](https://github.com/maquina-app/rails-mcp-server/releases)
+- [Issues](https://github.com/maquina-app/rails-mcp-server/issues)
+- [Documentation](https://github.com/maquina-app/rails-mcp-server#readme)
+- [Resources Guide](docs/RESOURCES.md)

data/README.md

@@ -1,6 +1,6 @@
 # Rails MCP Server
 
-A Ruby implementation of a Model Context Protocol (MCP) server for Rails projects. This server allows LLMs (Large Language Models) to interact with Rails projects through the Model Context Protocol.
+A Ruby implementation of a Model Context Protocol (MCP) server for Rails projects. This server allows LLMs (Large Language Models) to interact with Rails projects through the Model Context Protocol, providing capabilities for code analysis, exploration, and development assistance.
 
 ## What is MCP?
 
@@ -13,11 +13,13 @@ This Rails MCP Server implements the MCP specification to give AI models access
 - Manage multiple Rails projects
 - Browse project files and structures
 - View Rails routes
-- Inspect model information
+- Inspect model information and relationships
 - Get database schema information
 - Analyze controller-view relationships
 - Analyze environment configurations
+- Access comprehensive Rails, Turbo, Stimulus, and Kamal documentation
 - Follow the Model Context Protocol standard
+- Seamless integration with LLM clients
 
 ## Installation
 
@@ -45,10 +47,45 @@ To configure your projects:
 ```yaml
 store: "~/projects/store"
 blog: "~/projects/rails-blog"
+ecommerce: "/full/path/to/ecommerce-app"
 ```
 
 Each key in the YAML file is a project name (which will be used with the `switch_project` tool), and each value is the path to the project directory.
 
+## Usage
+
+### Starting the server
+
+The Rails MCP Server can run in two modes:
+
+1. **STDIO mode (default)**: Communicates over standard input/output for direct integration with clients like Claude Desktop.
+2. **HTTP mode**: Runs as an HTTP server with JSON-RPC and Server-Sent Events (SSE) endpoints.
+
+```bash
+# Start in default STDIO mode
+rails-mcp-server
+
+# Start in HTTP mode on the default port (6029)
+rails-mcp-server --mode http
+
+# Start in HTTP mode on a custom port
+rails-mcp-server --mode http -p 8080
+```
+
+When running in HTTP mode, the server provides two endpoints:
+
+- JSON-RPC endpoint: `http://localhost:<port>/mcp/messages`
+- SSE endpoint: `http://localhost:<port>/mcp/sse`
+
+### Logging Options
+
+The server logs to a file in the `./log` directory by default. You can customize logging with these options:
+
+```bash
+# Set the log level (debug, info, error)
+rails-mcp-server --log-level debug
+```
+
 ## Claude Desktop Integration
 
 The Rails MCP Server can be used with Claude Desktop. There are two options to set this up:
@@ -69,10 +106,10 @@ The script will:
 
 After running the script, restart Claude Desktop to apply the changes.
 
-### Option 2: Manual configuration
+### Option 2: Direct Configuration
 
 1. Create the appropriate config directory for your platform:
-   - macOS: `$XDG_CONFIG_HOME/rails-mcp` or `~/.config/rails-mcp`
+   - macOS: `$XDG_CONFIG_HOME/rails-mcp` or `~/.config/rails-mcp` if XDG_CONFIG_HOME is not set
    - Windows: `%APPDATA%\rails-mcp`
 
 2. Create a `projects.yml` file in that directory with your Rails projects.
@@ -102,48 +139,47 @@ Claude Desktop launches the MCP server using your system's default Ruby environm
 
 If you are using a Ruby version manager such as rbenv, you can create a symbolic link to your Ruby shim to ensure the correct version is used:
 
-```
-
+```bash
 sudo ln -s /home/your_user/.rbenv/shims/ruby /usr/local/bin/ruby
-
 ```
 
 Replace "/home/your_user/.rbenv/shims/ruby" with your actual path for the Ruby shim.
 
-## Usage
+### Using an MCP Proxy (Advanced)
 
-### Starting the server
+Claude Desktop and many other LLM clients only support STDIO mode communication, but you might want to use the HTTP/SSE capabilities of the server. An MCP proxy can bridge this gap:
 
-The Rails MCP Server can run in two modes:
-
-1. **STDIO mode (default)**: Communicates over standard input/output for direct integration with clients like Claude Desktop.
-2. **HTTP mode**: Runs as an HTTP server with JSON-RPC and Server-Sent Events (SSE) endpoints.
+1. Start the Rails MCP Server in HTTP mode:
 
 ```bash
-# Start in default STDIO mode
-rails-mcp-server
-
-# Start in HTTP mode on the default port (6029)
 rails-mcp-server --mode http
-
-# Start in HTTP mode on a custom port
-rails-mcp-server --mode http -p 8080
 ```
 
-When running in HTTP mode, the server provides two endpoints:
+2. Install and run an MCP proxy. There are several implementations available in different languages. An MCP proxy allows a client that only supports STDIO communication to communicate via HTTP SSE. Here's an example using a JavaScript-based MCP proxy:
 
-- JSON-RPC endpoint: `http://localhost:<port>/mcp/messages`
-- SSE endpoint: `http://localhost:<port>/mcp/sse`
+```bash
+# Install the Node.js based MCP proxy
+npm install -g mcp-remote
 
-### Logging Options
+# Run the proxy, pointing to your running Rails MCP Server
+npx mcp-remote http://localhost:6029/mcp/sse
+```
 
-The server logs to a file in the `./log` directory by default. You can customize logging with these options:
+3. Configure Claude Desktop (or other LLM client) to use the proxy instead of connecting directly to the server:
 
-```bash
-# Set the log level (debug, info, error)
-rails-mcp-server --log-level debug
+```json
+{
+  "mcpServers": {
+    "railsMcpServer": {
+      "command": "npx",
+      "args": ["mcp-remote", "http://localhost:6029/mcp/sse"]
+    }
+  }
+}
 ```
 
+This setup allows STDIO-only clients to communicate with the Rails MCP Server through the proxy, benefiting from the HTTP/SSE capabilities while maintaining client compatibility.
+
 ## How the Server Works
 
 The Rails MCP Server implements the Model Context Protocol using either:
@@ -151,7 +187,7 @@ The Rails MCP Server implements the Model Context Protocol using either:
 - **STDIO mode**: Reads JSON-RPC 2.0 requests from standard input and returns responses to standard output.
 - **HTTP mode**: Provides HTTP endpoints for JSON-RPC 2.0 requests and Server-Sent Events.
 
-Each request includes a sequence number to match requests with responses, as defined in the MCP specification.
+Each request includes a sequence number to match requests with responses, as defined in the MCP specification. The server maintains project context and provides Rails-specific analysis capabilities across multiple codebases.
 
 ## Available Tools
 
@@ -163,7 +199,7 @@ The server provides the following tools for interacting with Rails projects:
 
 **Parameters:**
 
-- `project_name`: (String, required) Name of the project to switch to, as defined in the projects.yml file
+- `project_name`: (String, required) Name of the project as defined in the projects.yml file (case-sensitive)
 
 #### Examples
 
@@ -179,7 +215,7 @@ I'd like to analyze my "blog" application. Please switch to that project first.
 Switch to the "ecommerce" project and give me a summary of the codebase.
 ```
 
-### 2. `get_project_info`
+### 2. `project_info`
 
 **Description:** Retrieve comprehensive information about the current Rails project, including Rails version, directory structure, API-only status, and overall project organization. Useful for initial project exploration and understanding the codebase structure.
 
@@ -205,8 +241,8 @@ I'd like to understand the high-level architecture of this project. Can you prov
 
 **Parameters:**
 
-- `directory`: (String, optional) Directory path relative to the project root (e.g., 'app/models', 'config')
-- `pattern`: (String, optional) File pattern using glob syntax (e.g., '.rb' for Ruby files, '.erb' for ERB templates)
+- `directory`: (String, optional) Directory path relative to the project root (e.g., 'app/models', 'config'). Leave empty to list files at the root.
+- `pattern`: (String, optional) File pattern using glob syntax (e.g., '*.rb' for Ruby files, '*.erb' for ERB templates, '*_controller.rb' for controllers)
 
 #### Examples
 
@@ -232,7 +268,7 @@ List all the JavaScript files in the app/javascript directory.
 
 **Parameters:**
 
-- `path`: (String, required) File path relative to the project root (e.g., 'app/models/user.rb', 'config/routes.rb')
+- `path`: (String, required) File path relative to the project root (e.g., 'app/models/user.rb', 'config/routes.rb'). Use list_files first if you're not sure about the exact path.
 
 #### Examples
 
@@ -272,13 +308,13 @@ I need to understand the API endpoints available in this project. Can you list t
 Show me the routing configuration for this Rails app so I can see how the URLs are structured.
 ```
 
-### 6. `analyze_models`
+### 6. `analize_models`
 
 **Description:** Retrieve detailed information about Active Record models in the project. When called without parameters, lists all model files. When a specific model is specified, returns its schema, associations (has_many, belongs_to, has_one), and complete source code.
 
 **Parameters:**
 
-- `model_name`: (String, optional) Class name of a specific model to get detailed information for (e.g., 'User', 'Product'). Use CamelCase, not snake_case.
+- `model_name`: (String, optional) Class name of a specific model to get detailed information for (e.g., 'User', 'Product'). Use CamelCase, not snake_case. If omitted, returns a list of all models.
 
 #### Examples
 
@@ -304,7 +340,7 @@ What are all the models in this application, and can you then show me details fo
 
 **Parameters:**
 
-- `table_name`: (String, optional) Database table name to get detailed schema information for (e.g., 'users', 'products'). Use snake_case, plural form.
+- `table_name`: (String, optional) Database table name to get detailed schema information for (e.g., 'users', 'products'). Use snake_case, plural form. If omitted, returns complete database schema.
 
 #### Examples
 
@@ -338,6 +374,14 @@ I need to understand the database design. Can you first list all tables and then
 Can you analyze the Users controller and its views to help me understand the UI flow?
 ```
 
+```
+Show me how the ProductsController connects to its views and what actions are available.
+```
+
+```
+I want to understand the entire controller-view structure of this application.
+```
+
 ### 9. `analyze_environment_config`
 
 **Description:** Analyze environment configurations to identify inconsistencies, security issues, and missing variables across environments.
@@ -350,14 +394,70 @@ Can you analyze the Users controller and its views to help me understand the UI
 Can you analyze the environment configurations to find any security issues or missing environment variables?
 ```
 
-## Integration with LLM Clients
+```
+Check the configuration files for any inconsistencies between development and production environments.
+```
 
-This server is designed to be integrated with LLM clients that support the Model Context Protocol, such as Claude Desktop or other MCP-compatible applications.
-To use with an MCP client:
+### 10. `load_guide`
 
-1. Start the Rails MCP Server (it will use STDIO mode by default)
-1. Connect your MCP-compatible client to the server
-1. The client will be able to use the available tools to interact with your Rails projects
+**Description:** Load documentation guides from Rails, Turbo, Stimulus, Kamal, or Custom. Use this to get guide content for context in conversations.
+
+**Parameters:**
+
+- `guides`: (String, required) The guides library to search: 'rails', 'turbo', 'stimulus', 'kamal', or 'custom'
+- `guide`: (String, optional) Specific guide name to load. If not provided, returns available guides list.
+
+#### Examples
+
+```
+Can you load the Rails getting started guide?
+```
+
+```
+Show me the available Turbo guides and then load the one about Turbo Frames.
+```
+
+```
+I need help with Stimulus. Can you load the hello_stimulus guide?
+```
+
+```
+Load the Kamal installation guide so I can understand deployment options.
+```
+
+## Resources and Documentation
+
+The Rails MCP Server provides access to comprehensive documentation through both the `load_guide` tool and direct MCP resource access. You can access official guides for Rails, Turbo, Stimulus, and Kamal, as well as import your own custom documentation.
+
+### Available Resource Categories
+
+- **Rails Guides**: Official Ruby on Rails 8.0.2 documentation
+- **Turbo Guides**: Official Turbo (Hotwire) framework documentation  
+- **Stimulus Guides**: Official Stimulus JavaScript framework documentation
+- **Kamal Guides**: Official Kamal deployment tool documentation
+- **Custom Guides**: Your imported markdown files
+
+### Getting Started with Resources
+
+Before using resources, you need to download them:
+
+```bash
+# Download Rails guides
+rails-mcp-server-download-resources rails
+
+# Download Turbo guides
+rails-mcp-server-download-resources turbo
+
+# Import custom markdown files
+rails-mcp-server-download-resources --file /path/to/your/docs/
+```
+
+### Resource Access Methods
+
+1. **Tool-based access**: Use the `load_guide` tool in conversations
+2. **Direct resource access**: MCP clients can query resources using URI patterns like `rails://guides/{guide_name}`
+
+For complete information about downloading, managing, and using resources, see the [Resources Guide](docs/RESOURCES.md).
 
 ## Testing and Debugging
 
@@ -365,7 +465,7 @@ The easiest way to test and debug the Rails MCP Server is by using the MCP Inspe
 
 To use MCP Inspector with Rails MCP Server:
 
-```
+```bash
 # Install and run MCP Inspector with your Rails MCP Server
 npm -g install @modelcontextprotocol/inspector
 
@@ -375,8 +475,8 @@ npx @modelcontextprotocol/inspector /path/to/rails-mcp-server
 This will:
 
 1. Start your Rails MCP Server in HTTP mode
-1. Launch the MCP Inspector UI in your browser (default port: 6274)
-1. Set up an MCP Proxy server (default port: 6277)
+2. Launch the MCP Inspector UI in your browser (default port: 6274)
+3. Set up an MCP Proxy server (default port: 6277)
 
 In the MCP Inspector UI, you can:
 
@@ -387,6 +487,16 @@ In the MCP Inspector UI, you can:
 
 The Inspector UI provides an intuitive interface to interact with your MCP server, making it easy to test and debug your Rails MCP Server implementation.
 
+## Integration with LLM Clients
+
+This server is designed to be integrated with LLM clients that support the Model Context Protocol, such as Claude Desktop or other MCP-compatible applications.
+
+To use with an MCP client:
+
+1. Start the Rails MCP Server (it will use STDIO mode by default)
+2. Connect your MCP-compatible client to the server
+3. The client will be able to use the available tools to interact with your Rails projects
+
 ## License
 
 This Rails MCP server is released under the MIT License, a permissive open-source license that allows for free use, modification, distribution, and private use.
@@ -397,7 +507,7 @@ Permission is hereby granted, free of charge, to any person obtaining a copy of
 
 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 ## Contributing