get_rubygem_infoLABSCO SUMMARY
Reverse dependencies is the tool that answers the question you cannot answer from the gem's own page.
"Who relies on this" decides whether a gem is safe to depend on and how bad a breaking change would be, and the registry page shows you the opposite direction. Having it as a first-class query — alongside an owner's full list, which is how you judge whether a maintainer is a going concern — makes this a due-diligence tool rather than a lookup. Small, read-only, cheap to keep connected.
What it is
A reader for the RubyGems registry, exposing the queries you actually make when evaluating or tracing a gem.
What you get
- get_rubygem_info — one gem's metadata
- search_rubygems — find gems matching a query
- get_gem_versions — every published version
- get_gem_reverse_dependencies — what depends on this gem
- get_owner_gems — everything a given owner publishes
Requirements
Node.
Setup effort
Build from source
USE CASES
01
Judging whether to depend on a gem
Who else already does.
02
Checking a maintainer
Everything that owner publishes.
03
Pinning a version
The full version list rather than the latest.
6 tools
Listed in project docs. Your client may show a different list.
search_rubygemsget_gem_versionsget_gem_reverse_dependenciesget_owner_gemsget_gem_ownersBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/6/mcp-server-rubygems
cd mcp-server-rubygems
npm install
npm run buildAdd the mcpServers block below to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows)
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"mcp-server-rubygems": {
"command": "<YOUR_PATH_TO_MCP_SERVER_RUBYGEMS>/build/index.js"
}
}
}
