Exploring RuboCop with MCP
summary
Built an MCP Ruby SDK that runs but stays Tier 3 experimental, with server-side conformance tests passing 100% while client features lag. Implements RuboCop --mcp via StandardIO (uses Open3) to expose the existing LSP runtime unchanged, and adds a Streamable HTTP as Rack app transport that uses an MCP-Session-ID header for bidirectional exchanges. Key limits: session state breaks across multiple processes, sampling and elicitation enable LLM and human callbacks, and RuboCop 1.85 ships the MCP hook.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker intro
- 3:50What is MCP and Ruby SDK
- 7:50Transport layers in MCP
- 13:05Streamable HTTP session management
- 19:26Summary of MCP fundamentals
- 19:50RuboCop MCP integration
- 24:13Combining RuboCop with LLMs
- 26:46Sampling and elicitation in MCP
- 29:46Future of AI-driven tooling
- 30:56Closing remarks and Q&A
related talks
15mFull Spec MCP: Hidden Capabilities of the MCP spec
55mYour MCP Server is Bad (and you should feel bad)
35mRuboCop Sent You a Friend Request
34mLLMs, Meet Your Tools: The Magic of Model Context Protocol
27mHow We Built Our First MCP Server: Lessons From the Trenches at Hud
43mLLMs, Meet Your Tools: The Magic of Model Context Protocol
29mAnalyzing an analyzer - A dive into how RuboCop works
17mMCP Is Not Good Yet