mcp_toolkit extracts the shared MCP-server framework that Smily's apps grew independently: a Streamable-HTTP transport, cache-backed sessions, central-app token introspection (satellite + authority roles), a registry-driven "generic tools over N resources" dispatcher, and an injectable serializer DSL. It wraps the official `mcp` gem as the JSON-RPC core so each app ships only its serializers, resource registrations, and scope blocks.

Load any Thor CLI directly as a StdIO MCP server

MCP servers focused on fetching and presenting information from Obsidian vaults

A unified DSL for exposing structured data and operations across analytics tools (PowerBI), no-code platforms (PowerAutomate), and AI agents (via MCP).

A Rails blog engine with reader pages, revision history, and agent publishing interfaces.

Model Context Protocol server for Panda CMS. Provides tools for managing pages, posts, and collections via Claude Desktop and other MCP clients.

CLI toolkit providing memory, hooks, and MCP servers for Claude Code personality system

Phronomy is a Ruby AI agent framework that provides composable building blocks — Agents, Workflows, Tools, Filters, and Tracing — for building AI agents in Ruby. Powered by RubyLLM for LLM abstraction.

pikuri-mcp adds Model Context Protocol support to pikuri-core agents: a +Pikuri::Mcp::Registry+ for declaring stdio + HTTP MCP servers, the +Pikuri::Mcp::Servers+ runtime that spawns them, a +Pikuri::Mcp::Synthesizer+ that LLM-fills missing server descriptions, a +Pikuri::Mcp::Verifier+ that screens server surfaces for prompt-injection patterns before any tool is advertised to the LLM, and a +Pikuri::Mcp::Extension+ that wires everything into a +Pikuri::Agent+ via +c.add_extension(...)+ in the +Agent.new+ block.

Pinmark adds a dev-only floating overlay to any Rails app. Click a component or any element on the page, leave a comment, and Claude Code consumes the queue via MCP — closing the loop between visual feedback and source edits. Works with Phlex, ViewComponent, and ERB partials.

Protocol-only core gem: Adapter contract, capability registry, manifest builder, and an MCP server wrapper. No commerce-backend deps.

Every other portage-ucp gem lets a Ruby program expose a commerce backend to agents (server side). This gem is the other direction: connect to somebody else's /.well-known/ucp manifest, or drive your own Adapter directly, and place an order as the client. Three transports behind one interface (loopback over an in-process Adapter, stdio, Streamable HTTP) — callers never know which they got. Depends only on portage-ucp, the mcp gem's client half, and faraday (the HTTP transport's backend); no adapter gem is a dependency.

Maps a Rails app so assistants stop guessing — static context files and a read-only MCP server.

Rails Engine that captures exceptions, stores them in your database with rich context, and exposes error data via a bundled MCP server so AI agents can triage, resolve, and fix errors autonomously.

MCP server that indexes codebases using AST-aware chunking and vector embeddings, providing semantic search for Claude Code and other MCP clients.

An MCP (Model Context Protocol) server that gives AI assistants (Claude, Cursor, Copilot, VS Code) deep, intelligent understanding of any Rails application. 15 tools covering routes, models, controllers, security, testing, and full request lifecycle tracing.

A comprehensive Rails profiler with web debug toolbar, profiling UI, SQL analysis, performance timeline, and MCP server integration

RailVerdict collects evidence from established Ruby and Rails quality tools, normalizes it into stable findings, applies project policy, and returns a deterministic merge gate for humans, CI, and coding agents. The core is offline, fail-closed, and independent of AI and hosted services.

CLI utility and Ruby API for generating structured release notes and changelog documents from various issue-tracking platforms or YAML definitions into plaintext drafts (<strong>AsciiDoc</strong>, <strong>Markdown</strong>, <strong>YAML</strong>) and rich-text output (<strong>HTML</strong> and <strong>PDF</strong>).

Exposes Resque queues, workers, and failed jobs to MCP clients via a Streamable HTTP endpoint mounted in the host Rails app.