Manceps – Ruby Client for the Model Context Protocol (MCP)

Name: Manceps – Ruby Client for the Model Context Protocol (MCP)
Availability: InStock
Author: obiefernandez

by obiefernandez·Apr 7, 2026·1 point·0 comments

Visit Project View on HN

AI Analysis

●●SolidNiche GemShip It

Ruby MCP client with httpx persistence when other options break persistent connections.

Strengths

•httpx-backed Streamable HTTP transport handles MCP's session-to-connection binding correctly
•Framework-agnostic design avoids coupling to specific LLM SDKs like LangChain
•Experimental OAuth 2.1 with PKCE and automatic token refresh already implemented

Weaknesses

•Ruby >= 3.4 requirement excludes many production apps still on 3.1 or 3.2
•OAuth flow untested against diverse authorization servers beyond the author's setup

Post Description

I built this because existing Ruby options for MCP either don't handle persistent connections properly (MCP servers bind sessions to TCP connections) or couple you to a specific LLM framework.

Manceps is a pure protocol client. Two transports (Streamable HTTP and stdio), built-in auth (bearer, API key, experimental OAuth 2.1 with PKCE), and full 2025-11-25 spec support including protocol negotiation, elicitation, structured output, and notifications.

It uses httpx under the hood for connection persistence. No LLM opinions -- just MCP.

Ruby >= 3.4, MIT licensed.