Experimental MCP Support

Author: obie

.rubocop.yml

@@ -36,7 +36,7 @@ Metrics/PerceivedComplexity:
 Metrics/ParameterLists:
   Enabled: false
 
-Style/FrozenLiteralComment:
+Style/FrozenStringLiteralComment:
   Enabled: false
 
 Style/MultilineBlockChain:

CHANGELOG.md

@@ -1,6 +1,6 @@
-## [0.8.0] - 2025-05-08
+## [0.8.0] - 2024-05-08
 ### Added
-* **MCP integration** — new `Raix::MCP` concern and `mcp` DSL for declaring remote MCP servers.
+* **MCP integration (Experimental)** — new `Raix::MCP` concern and `mcp` DSL for declaring remote MCP servers.
   * Automatically fetches `tools/list`, registers remote tools as OpenAI‑compatible function schemas, and defines proxy methods that forward `tools/call`.
   * `ChatCompletion#tools` now returns remote MCP tools alongside local `function` declarations.
 

Gemfile.lock

@@ -3,7 +3,6 @@ PATH
   specs:
     raix (0.8.0)
       activesupport (>= 6.0)
-      async-http-faraday (~> 0.21)
       faraday-retry (~> 2.0)
       open_router (~> 0.2)
       ruby-openai (~> 7)
@@ -24,38 +23,13 @@ GEM
     addressable (2.8.6)
       public_suffix (>= 2.0.2, < 6.0)
     ast (2.4.2)
-    async (2.23.1)
-      console (~> 1.29)
-      fiber-annotation
-      io-event (~> 1.9)
-      metrics (~> 0.12)
-      traces (~> 0.15)
-    async-http (0.88.0)
-      async (>= 2.10.2)
-      async-pool (~> 0.9)
-      io-endpoint (~> 0.14)
-      io-stream (~> 0.6)
-      metrics (~> 0.12)
-      protocol-http (~> 0.49)
-      protocol-http1 (~> 0.30)
-      protocol-http2 (~> 0.22)
-      traces (~> 0.10)
-    async-http-faraday (0.21.0)
-      async-http (~> 0.42)
-      faraday
-    async-pool (0.10.3)
-      async (>= 1.25)
     backport (1.2.0)
     base64 (0.2.0)
     benchmark (0.3.0)
     bigdecimal (3.1.8)
     coderay (1.1.3)
     concurrent-ruby (1.3.3)
     connection_pool (2.4.1)
-    console (1.30.2)
-      fiber-annotation
-      fiber-local (~> 1.1)
-      json
     crack (0.4.5)
       rexml
     diff-lcs (1.5.1)
@@ -74,10 +48,6 @@ GEM
       faraday (~> 2.0)
     ffi (1.17.2-arm64-darwin)
     ffi (1.17.2-x86_64-linux-gnu)
-    fiber-annotation (0.2.0)
-    fiber-local (1.1.0)
-      fiber-storage
-    fiber-storage (1.0.1)
     formatador (1.1.0)
     guard (2.18.1)
       formatador (>= 0.2.4)
@@ -96,9 +66,6 @@ GEM
     hashdiff (1.0.1)
     i18n (1.14.5)
       concurrent-ruby (~> 1.0)
-    io-endpoint (0.15.2)
-    io-event (1.10.0)
-    io-stream (0.6.1)
     jaro_winkler (1.6.0)
     json (2.7.1)
     kramdown (2.4.0)
@@ -111,7 +78,6 @@ GEM
       rb-inotify (~> 0.9, >= 0.9.10)
     lumberjack (1.2.10)
     method_source (1.1.0)
-    metrics (0.12.2)
     minitest (5.24.0)
     multipart-post (2.4.1)
     mutex_m (0.2.0)
@@ -136,13 +102,6 @@ GEM
       ast (~> 2.4.1)
       racc
     prism (0.30.0)
-    protocol-hpack (1.5.1)
-    protocol-http (0.49.0)
-    protocol-http1 (0.34.0)
-      protocol-http (~> 0.22)
-    protocol-http2 (0.22.1)
-      protocol-hpack (~> 1.4)
-      protocol-http (~> 0.47)
     pry (0.14.2)
       coderay (~> 1.1)
       method_source (~> 1.0)
@@ -236,7 +195,6 @@ GEM
       yard-sorbet
     thor (1.3.1)
     tilt (2.3.0)
-    traces (0.15.2)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
     unicode-display_width (2.5.0)

README.md

@@ -452,6 +452,50 @@ question.ask("Any question")
 # => RuntimeError: Please define a yes and/or no block
 ```
 
+## Model Context Protocol (Experimental)
+
+The `Raix::MCP` module provides integration with the Model Context Protocol, allowing you to connect your Raix-powered application to remote MCP servers. This feature is currently **experimental**.
+
+### Usage
+
+Include the `Raix::MCP` module in your class and declare MCP servers using the `mcp` DSL:
+
+```ruby
+class McpConsumer
+  include Raix::ChatCompletion
+  include Raix::FunctionDispatch
+  include Raix::MCP
+
+  mcp "https://your-mcp-server.example.com/sse"
+end
+```
+
+### Features
+
+- Automatically fetches available tools from the remote MCP server using `tools/list`
+- Registers remote tools as OpenAI-compatible function schemas
+- Defines proxy methods that forward requests to the remote server via `tools/call`
+- Seamlessly integrates with the existing `FunctionDispatch` workflow
+- Handles transcript recording to maintain consistent conversation history
+
+### Filtering Tools
+
+You can filter which remote tools to include:
+
+```ruby
+class FilteredMcpConsumer
+  include Raix::ChatCompletion
+  include Raix::FunctionDispatch
+  include Raix::MCP
+
+  # Only include specific tools
+  mcp "https://server.example.com/sse", only: [:tool_one, :tool_two]
+
+  # Or exclude specific tools
+  mcp "https://server.example.com/sse", except: [:tool_to_exclude]
+end
+```
+
 ## Response Format (Experimental)
 
 The `ResponseFormat` class provides a way to declare a JSON schema for the response format of an AI chat completion. It's particularly useful when you need structured responses from AI models, ensuring the output conforms to your application's requirements.