action_mcp and mcp_on_ruby
One is a Rails Engine implementing the Model Context Protocol (MCP) specification, while the other is a Ruby gem providing a general implementation of the same MCP, making them ecosystem siblings where one could potentially leverage the other for its protocol implementation.
About action_mcp
seuros/action_mcp
Rails Engine with MCP compliant Spec.
Provides base classes for building MCP servers in Rails with JSON-RPC 2.0 transport, supporting capability negotiation, session management, and change notifications per MCP 2025-06-18 spec. Exposes three core abstractions—Prompt, Tool, and ResourceTemplate—allowing developers to declaratively define LLM-accessible capabilities with built-in validation and consent management for sensitive operations. Designed exclusively for production network deployments; STDIO transport is intentionally excluded in favor of robust server architectures.
About mcp_on_ruby
rubyonai/mcp_on_ruby
💎 A Ruby implementation of the Model Context Protocol
Provides a Rails-native DSL for exposing tools and resources to AI clients via the Model Context Protocol, with built-in JSON Schema validation, URI templating, and authentication. Uses HTTP/SSE transport with production-grade security features including DNS rebinding protection and token authentication, integrating directly with Rails generators and middleware for seamless server setup.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work