fast_mcp_jwt_auth 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a40c2263c74d33678f1b189fd831d51e5ea5ebf4e498fb3334e93f3763997e99
-  data.tar.gz: ef51aae1fa0e79848a23f67cf4a77194d67dfd244594edcc9f4ffcd356069249
+  metadata.gz: 70cd49312d3da735c0f936a67489255a0730fc343274690a616c4c3384be718e
+  data.tar.gz: 2df8782779b4f78566c81012ffe7f5e60a2c0df39c632ab568075195c85ee806
 SHA512:
-  metadata.gz: 357905685ab8feab45e48cfa5dc0b2c302b8e795c82038b98046f1ae732edbd6e685787e3b3b149c3967c4e4f711fab040fb95c489aceb1491448e65db248a0f
-  data.tar.gz: df3d0ace55cf03367db55b0c0cb290319d12b20a015f3ac771b4e72e0cbea499159ae6c684535507eea103f3afedd5dd8adaa070315985e2d679ee6578644976
+  metadata.gz: bf3afe9ede194bac8b594d2170c2185b73d1473b581d38f8f11644a886d955c504f98f7ebffa3c73d108b7c1f050b9993e35ede5aa882e7b8996cc2285e1f3c7
+  data.tar.gz: 96b43b0ecd17a55647de3fa48beed7d6b762315f1aad9bd658e0d0d51d14dd33a1a27a2f81dc2cb866ec8dec61d26758cf0d9fb11b00882492b91ba2ec748888

data/CHANGELOG.md

@@ -7,6 +7,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.0] - 2026-08-20
+
+Everything below reached consumers through the git source months ago but was
+never published: 0.1.0 on RubyGems is the `v0.1.0` tag, seven commits behind what
+projects actually run. This release closes that gap so the gem can be consumed
+from RubyGems instead of from GitHub.
+
+### Added
+- Comprehensive JWT authentication logging.
+
+### Fixed
+- Railtie class methods are public, as Rails initializer context requires.
+- Token validator lambda parameter mismatch.
+
+### Changed
+- Refactored towards Ruby Way idiom, with broader test coverage.
+- README documents MCP server configuration.
+
 ## [0.1.0] - 2025-08-19
 
 ### Added

data/lib/fast_mcp_jwt_auth/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module FastMcpJwtAuth
-  VERSION = "0.1.0"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: fast_mcp_jwt_auth
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - josefchmel
 bindir: exe
 cert_chain: []
-date: 2025-10-02 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -102,13 +102,7 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".DS_Store"
-- ".mcp.json"
-- ".mcp.json.example"
-- ".rubocop.yml"
-- ".ruby-version"
 - CHANGELOG.md
-- CLAUDE.md
 - LICENSE.txt
 - README.md
 - Rakefile
@@ -141,7 +135,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.6.2
+rubygems_version: 4.0.6
 specification_version: 4
 summary: JWT Authorization header authentication for FastMcp RackTransport
 test_files: []

data/.mcp.json

@@ -1,30 +0,0 @@
-{
-  "mcpServers": {
-    "workvector-production": {
-      "type": "sse",
-      "name": "WorkVector Production",
-      "url": "https://workvector.com/mcp/sse",
-      "headers": {
-        "Authorization": "Bearer ${WORKVECTOR_TOKEN}"
-      }
-    },
-    "filesystem-project": {
-      "type": "stdio",
-      "name": "Filesystem",
-      "command": "npx",
-      "args": [
-        "-y",
-        "@modelcontextprotocol/server-filesystem",
-        "${PWD}"
-      ]
-    },
-    "llmmn-production": {
-      "type": "sse",
-      "name": "LLM Memory Notes Production",
-      "url": "https://llm-memory.com/mcp/sse",
-      "headers": {
-        "Authorization": "Bearer ${LLMMN_TOKEN}"
-      }
-    }
-  }
-}

data/.mcp.json.example

@@ -1,30 +0,0 @@
-{
-  "mcpServers": {
-    "example-server": {
-      "type": "sse",
-      "name": "Example MCP Server",
-      "url": "https://example.com/mcp/sse",
-      "headers": {
-        "Authorization": "Bearer ${MCP_JWT_TOKEN}"
-      }
-    },
-    "workvector-production": {
-      "type": "sse",
-      "name": "WorkVector Production",
-      "url": "https://workvector.com/mcp/sse",
-      "headers": {
-        "Authorization": "Bearer ${WORKVECTOR_TOKEN}"
-      }
-    },
-    "filesystem-project": {
-      "type": "stdio",
-      "name": "Filesystem",
-      "command": "npx",
-      "args": [
-        "-y",
-        "@modelcontextprotocol/server-filesystem",
-        "${PWD}"
-      ]
-    }
-  }
-}

data/.rubocop.yml

@@ -1,34 +0,0 @@
-AllCops:
-  TargetRubyVersion: 3.1
-  NewCops: enable
-  SuggestExtensions: false
-
-plugins:
-  - rubocop-minitest
-
-Layout/LineLength:
-  Max: 200
-
-Style/StringLiterals:
-  EnforcedStyle: double_quotes
-
-Style/StringLiteralsInInterpolation:
-  EnforcedStyle: double_quotes
-
-# Relax some metrics for reasonable code
-Metrics/ClassLength:
-  Max: 150
-
-Metrics/MethodLength:
-  Max: 30
-
-Metrics/AbcSize:
-  Max: 35
-
-# Allow longer module for JWT authentication patch - it's a cohesive logical unit
-Metrics/ModuleLength:
-  Max: 130
-
-# Allow development dependencies in gemspec for gems
-Gemspec/DevelopmentDependencies:
-  Enabled: false

data/.ruby-version

@@ -1 +0,0 @@
-ruby-3.4.2

data/CLAUDE.md

@@ -1,148 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code when working with the `fast_mcp_jwt_auth` gem.
-
-## Gem Overview
-
-FastMCp Jwt Auth provides JWT authentication for FastMcp RackTransport, enabling secure user authentication in MCP requests.
-It integrates seamlessly with Rails, allowing you to authenticate users using JWT tokens in a Rails application.
-
-## Code Conventions
-
-### Code Quality
-- Max 200 chars/line (soft limit - prefer readability over strict compliance)
-  - breaking Ruby chain calls destroys the natural sentence flow and readability
-- 14 lines/method, 110 lines/class
-- Comments and tests in English
-- KEEP CODE DRY (Don't Repeat Yourself)
-
-### Ruby/Rails Philosophy
-- **DO IT RUBY WAY OR RAILS WAY** - it's not Python, Java or PHP!
-- Strong use of Ruby metaprogramming techniques
-- code line should look like human sentence (e.g. `3.times do` not `for i in 0..2 do` - Ruby syntax reads like English)
-- keep code raising exceptions when it's programmer's fault - DO NOT validate method parameters, expect them to be correct! Only validate user input
-- do not repeat name of parameter in method name (e.g. `def create_new_user_from_user(user)` should be `def create_new_user_from(user)`)
-- do not use extra variable if used only once - saves memory and reduces GC pressure under high traffic (e.g. `user = User.find(params[:id]); user.update(...)` should be `User.find(params[:id]).update(...)`) - use `.tap do` for chaining when you need to use the object later
-- use metaprogramming instead of case statements (e.g. `self.send(method_name, params)` instead of `case method_name; when "find_slot"...` - let Ruby handle method dispatch and NoMethodError)
-- PREFER FUNCTIONAL STYLE: use flat_map, map, select over loops and temp variables (e.g. `items.flat_map(&:children).uniq` not `results = []; items.each { |i| results.concat(i.children) }; results.uniq`)
-- USE PATTERN MATCHING: Ruby 3.0+ `case/in` for complex conditionals instead of if/elsif chains - more expressive and catches unhandled cases
-- ONE CLEAR RESPONSIBILITY: each method should do one thing well - if method has "and" in description, split it (e.g. `normalize_and_search` → `normalize` + `search`)
-- FOLLOW KISS PRINCIPLE: Keep It Simple, Stupid - avoid unnecessary complexity, use simple solutions first
-- ALWAYS TEST YOUR CODE
-
-### Error Handling
-- Use meaningful exception classes (not generic StandardError)
-- Log errors with context using the configured logger
-- Proper error propagation with fallback mechanisms
-- Use `rescue_from` for common exceptions in Rails integration
-
-### Performance Considerations
-- Use database connection pooling efficiently
-- Avoid blocking operations in main threads
-- Cache expensive operations
-- Monitor thread lifecycle and cleanup
-
-### Thread Safety
-- All operations must be thread-safe for cluster mode
-- Use proper synchronization when accessing shared resources
-- Handle thread lifecycle correctly (creation, monitoring, cleanup)
-- Use connection checkout/checkin pattern for database operations
-
-### Gem Specific Guidelines
-
-#### Configuration
-- Use configuration object pattern for all settings
-- Provide sensible defaults that work out of the box
-- Make all components configurable but not required
-- Support both programmatic and initializer-based configuration
-
-#### Rails Integration
-- Use Railtie for automatic Rails integration
-- Hook into appropriate Rails lifecycle events
-- Respect Rails conventions for logging and error handling
-- Provide manual configuration options for non-Rails usage
-
-#### Error Recovery
-- Implement automatic retry with backoff for transient errors
-- Provide fallback mechanisms when PubSub fails
-- Log errors appropriately without flooding logs
-- Handle connection failures gracefully
-
-#### Testing
-- Test all public interfaces
-- Mock external dependencies (PostgreSQL, FastMcp)
-- Test error conditions and edge cases
-- Provide test helpers for gem users
-- Test both Rails and non-Rails usage
-
-## Architecture
-
-### Components
-
-1. **FastMcpJwtAuth::Service** - Core JWT authentication service
-   - Handles JWT token generation and validation
-   - Integrates with FastMcp RackTransport for secure requests
-2. **FastMcpJwtAuth::Configuration** - Configuration management
-   - Manages settings like JWT secret, expiration, and algorithm
-3. **FastMcpJwtAuth::RackTransportPatch** - Monkey patch for FastMcp transport
-   - Overrides `send_message` to include JWT authentication
-4. **FastMcpJwtAuth::Railtie** - Rails integration and lifecycle management
-   - Automatically patches FastMcp::Transports::RackTransport during Rails initialization
-
-### Message Flow
-
-1. **MCP Request Received** - FastMcp RackTransport receives HTTP request with Authorization header
-2. **JWT Extraction** - Extract Bearer token from Authorization header (`HTTP_AUTHORIZATION`)
-3. **Token Decoding** - Use configured `jwt_decoder` callback to decode JWT token
-4. **Token Validation** - Validate token expiration and other claims using `token_validator` callback
-5. **User Lookup** - Find user from decoded token using `user_finder` callback
-6. **User Assignment** - Set current user in context using `current_user_setter` callback
-7. **Request Processing** - Continue with normal MCP request handling
-8. **Cleanup** - Clear current user context using `current_resetter` callback
-
-### Thread Management
-
-The gem is designed to be thread-safe for use in Rails applications:
-
-- **Request Isolation** - Each MCP request runs in its own thread context
-- **Current User Context** - Uses thread-local storage via Rails `Current` class for user context
-- **Monkey Patching Safety** - Patch is applied only once using thread-safe flag checking
-- **No Shared State** - All operations are stateless except for configuration (immutable after initialization)
-- **Callback Thread Safety** - User-provided callbacks (`jwt_decoder`, `user_finder`, etc.) must be thread-safe
-- **Automatic Cleanup** - Current user context is always cleared after request processing (even on exceptions)
-
-## Dependencies
-
-### Runtime Dependencies
-- **rails** (>= 7.0) - Required for Rails integration, Current class, and logger support
-
-### Development Dependencies
-- **jwt** (~> 2.0) - Used in tests for JWT token generation and decoding examples
-- **minitest** (~> 5.16) - Test framework
-- **rubocop** (~> 1.21) - Ruby code style enforcement
-- **rubocop-minitest** (~> 0.25) - Minitest-specific RuboCop rules
-- **rubocop-rails** (~> 2.0) - Rails-specific RuboCop rules
-
-### External Dependencies
-- **FastMcp** - The gem monkey patches `FastMcp::Transports::RackTransport` (not declared as dependency to avoid circular dependencies)
-- **JWT Library** - Users must provide their own JWT decoder implementation (commonly `jwt` gem)
-
-## Development
-
-### Running Tests
-```bash
-bundle exec rake test
-```
-
-### Linting
-```bash
-bundle exec rubocop
-```
-
-### Console
-```bash
-bundle exec rake console
-```
-
-## Project-Specific Info
-- **LLM Memory identifier**: `fast_mcp_jwt_auth`