mcp_on_ruby 0.3.0 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 04166e9711a0a9c233c43a2f1bba53b27d0a716a7cc996c52f597433e559909d
-  data.tar.gz: 588bbbd27e9bc620e4cf4ea14b97b4e8c5cd869b672f8956a2a17b16b179afdb
+  metadata.gz: 41b083ae138856bff622b5bbdcaa2112ee08961b1eda6acec5a4bb5a7a6f0b04
+  data.tar.gz: e67b154ece12257fd300fd4824d25392a1a103de5ef0c8b0654fe17af970dd97
 SHA512:
-  metadata.gz: c22a5a6e40162c8754975bb89288ee5147314e41564a97ea25ab7b85fae03eecfcdc7246a0567520d6813ead8bc22e88ffcfa265ccf16653c2da8f06da8adb28
-  data.tar.gz: e16b57bd9c57d50f1f9f46328d29b94986e54785b166cbf321db1d06366fcd0fa2d43dd7206468ac3671219be7800c8a1f8ccbaaea2eaa77ca4e95217c32da2f
+  metadata.gz: a3927a0dbfba3cc726868a3f05690340d90bbd6a0715be53880bec3611f861bbf1cc7f817167e4df3373d6fd76e013575745a00c625e7a119f839683c7aa9166
+  data.tar.gz: 4e9b2179b6c709597b0fe6d8327f8e7d1539107d32d2f76c237a82e3e1d06c86dcc0ea1d17e2f226e5524cb1772e91fc0478c7e188d977252db9de51a57708a1

data/CHANGELOG.md

@@ -1,41 +1,69 @@
 # Changelog
 
-## [0.3.0] - 2023-05-01
+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.0.0] - 2025-01-28
 
 ### Added
-- ActiveRecord storage backend for database persistence
-- Support for Rails integration with ActiveRecord storage
-- Auto-creation of database tables with configurable prefixes
-- Proper handling of different data types (text, binary, JSON)
-- Symbolization of hash keys for consistent API
-- Comprehensive test suite for ActiveRecord storage
+- Production-ready MCP server implementation for Rails applications
+- Rails-native integration with generators, middleware, and Railtie
+- Full JSON-RPC 2.0 protocol support over HTTP transport
+- Rails generators for quick setup:
+  - `rails generate mcp_on_ruby:install` - Complete MCP server setup
+  - `rails generate mcp_on_ruby:tool` - Create new tools with templates
+  - `rails generate mcp_on_ruby:resource` - Create new resources with URI templates
+- Comprehensive security features:
+  - Bearer token authentication
+  - Rate limiting (configurable per minute)
+  - CORS support with configurable origins
+  - DNS rebinding protection
+  - Localhost-only mode for development
+- Automatic tool and resource discovery in Rails apps
+- JSON Schema validation for tool inputs
+- URI templating for resources
+- Error handling with proper JSON-RPC error codes
+- Claude Desktop integration with stdio bridge example
+- Extensive documentation and examples
 
 ### Changed
-- Enhanced `StorageFactory` to support ActiveRecord backend
-- Updated configuration system with ActiveRecord options
-- Improved documentation with ActiveRecord storage examples
+- Complete architectural rewrite focused on Rails integration
+- Simplified API following Rails conventions
+- Improved error handling and logging
+- Better security defaults
 
-## [0.2.0] - 2025-04-21
+### Fixed
+- Rails 8 compatibility issues with frozen arrays
+- Middleware initialization timing issues
+- Tool auto-registration in development mode
+- PostgreSQL parameter binding in tool examples
 
-### Added
-- Redis storage backend with comprehensive test coverage
-- Configurable TTL and namespace support for Redis keys
-- Rails integration with Redis storage examples
-- Wiki documentation for Redis storage setup and usage
+### Removed
+- Standalone client implementation (focus on server-side)
+- STDIO transport (HTTP-only, with bridge examples for stdio clients)
+- Prompts and roots features (not commonly used in Rails context)
 
-### Changed
-- Enhanced storage factory to support different backend types
-- Improved configuration API for more intuitive setup
-- Updated README with Redis storage documentation
+## [0.2.0] - 2024-07-24
 
-## [0.1.0] - 2025-04-18
+### Added
+- OAuth 2.1 authentication for secure remote connections
+- Permission-based access control for MCP methods
+- JWT token validation and management
+- Automatic token refresh mechanism
+- HTTP transport authentication integration
+- Middleware architecture for server authentication
+- Authentication examples and documentation
 
-Initial release of version 0.1.0 of the Ruby Gem. 
+## [0.1.0] - 2024-06-15
 
 ### Added
-- Core MCP implementation with Rack server
-- Provider support for OpenAI and Anthropic
-- In-memory storage backend
-- Context, message, and content management
-- Basic authentication support
-- Comprehensive test suite
+- Initial implementation of core MCP protocol
+- JSON-RPC 2.0 message format
+- HTTP and STDIO transports
+- Basic server and client functionality
+- Tool definition and execution
+- Resource management
+- Prompt handling
+- Root filesystem access

data/CODE_OF_CONDUCT.md

@@ -2,83 +2,55 @@
 
 ## Our Pledge
 
-We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
 
 ## Our Standards
 
-Examples of behavior that contributes to a positive environment for our community include:
+Examples of behavior that contributes to a positive environment:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall community
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
 
-Examples of unacceptable behavior include:
+Examples of unacceptable behavior:
 
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
+* The use of sexualized language or imagery, and sexual attention or advances
 * Trolling, insulting or derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+* Publishing others' private information without explicit permission
+* Other conduct which could reasonably be considered inappropriate
 
 ## Enforcement Responsibilities
 
-Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+Project maintainers are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
 
 ## Scope
 
-This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at nagendra.dhanakeerthi@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT EMAIL ADDRESS].
 
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the community.
+All complaints will be reviewed and investigated promptly and fairly.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
 
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
+[homepage]: https://www.contributor-covenant.org

data/CONTRIBUTING.md

@@ -1,92 +1,86 @@
-# Contributing to RubyMCP
+# Contributing to MCP on Ruby
 
-Thank you for considering contributing to RubyMCP! This document outlines the process for contributing to the project.
+We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
 
-## Code of Conduct
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+- Becoming a maintainer
 
-This project and everyone participating in it is governed by our [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
-
-## How Can I Contribute?
-
-### Reporting Bugs
-
-This section guides you through submitting a bug report for RubyMCP.
-
-Before creating bug reports, please check [the issue list](https://github.com/nagstler/mcp_on_ruby/issues) to avoid duplicating an existing report. When you create a bug report, include as many details as possible:
-
-* **Use a clear and descriptive title**
-* **Describe the exact steps to reproduce the bug**
-* **Provide specific examples**
-* **Describe the behavior you observed**
-* **Explain the behavior you expected**
-* **Include screenshots or animated GIFs** if possible
-* **Include details about your configuration and environment**
-
-### Suggesting Enhancements
-
-This section guides you through submitting an enhancement suggestion for RubyMCP.
-
-Enhancement suggestions are tracked as GitHub issues. When creating an enhancement suggestion:
-
-* **Use a clear and descriptive title**
-* **Provide a detailed description of the suggested enhancement**
-* **Explain why this enhancement would be useful**
-* **Specify which version you're using**
-* **Specify the name and version of the OS you're using**
+## Development Process
 
-### Pull Requests
+We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
 
-* Fill in the required template
-* Follow the Ruby style guide
-* Include tests for new features
-* Document new code based on the rest of the codebase
-* End all files with a newline
+## Pull Requests
 
-## Development Process
+1. Fork the repo and create your branch from `main`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. Make sure your code lints.
+6. Issue that pull request!
 
-### Setting Up Development Environment
+## Development Setup
 
 ```bash
-# Fork and clone the repository
-git clone https://github.com/yourusername/ruby_mcp.git
-cd ruby_mcp
+# Clone your fork
+git clone https://github.com/nagstler/mcp_on_ruby.git
+cd mcp_on_ruby
 
 # Install dependencies
 bundle install
 
-# Run tests
-bundle exec rspec
+# Run the generators to test Rails integration
+mkdir test_app && cd test_app
+rails new . --skip-git
+echo "gem 'mcp_on_ruby', path: '..' " >> Gemfile
+bundle install
+rails generate mcp_on_ruby:install
 
+# Test the gem
+cd .. && ruby -e "require './lib/mcp_on_ruby'; puts 'Gem loads successfully'"
+```
 
-### Testing
+## Code Style
 
-Write tests for all new features
-Ensure all tests pass before submitting a pull request
-Run the full test suite locally before submission
+- Follow standard Ruby conventions
+- Use meaningful variable and method names
+- Add documentation for public APIs
+- Keep methods focused and small
 
-```bash
-bundle exec rspec
-```
+## Testing
 
-### Style Guidelines
+Currently, we use manual testing and examples. In the future, we plan to add:
+- RSpec test suite
+- Integration tests with Rails
+- CI/CD pipeline
 
-Code should follow the Ruby style guide
-Run RuboCop to check your code style
+## Bug Reports
 
-```bash
-bundle exec rubocop
-```
+We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/nagstler/mcp_on_ruby/issues).
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+## Feature Requests
 
-### Release Process
+We use GitHub issues to track feature requests. Propose a feature by [opening a new issue](https://github.com/nagstler/mcp_on_ruby/issues).
 
-RubyMCP follows Semantic Versioning.
+**Great Feature Requests** include:
 
-- MAJOR version for incompatible API changes
-- MINOR version for backward-compatible functionality additions
-- PATCH version for backward-compatible bug fixes
+- Clear use case description
+- Why this feature would be useful
+- Proposed API or implementation approach
+- Examples of how it would be used
 
-### First-time Contributors
-If you're new to the project, look for issues labeled with good first issue which are ideal starting points for newcomers.
+## License
 
-### License
-By contributing to RubyMCP, you agree that your contributions will be licensed under the project's MIT License.
+By contributing, you agree that your contributions will be licensed under the same MIT License that covers the project.

data/LICENSE.txt

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2025 Nagendra Dhanakeerthi
+Copyright (c) 2024
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -18,4 +18,4 @@ 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.