About mcp-server-rubygems
mcp-server-rubygems exposes RubyGems.org metadata lookup and search tools for developers and clients that need package information. Its tools cover gem details, versions, dependencies, and ownership.
Key features
- 01Search RubyGems
- 02Retrieve gem metadata
- 03List gem versions
- 04Find reverse dependencies
- 05Inspect gem ownership
Use cases
- 01Check a gem's metadata and available versions
- 02Find packages that depend on a gem
- 03Review gems owned by a user or organization
MCP support
Provides MCP tools that query the RubyGems.org API for package metadata, search results, versions, dependencies, and ownership.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEmcp-server-rubygems 
A Model Context Protocol server for fetching rubygems metadata via rubygems.org API.
Tools
This MCP server provides the following tools for interacting with the RubyGems.org API:
| Tool | Description |
|---|---|
get_rubygem_info | Get information about a RubyGem |
search_rubygems | Search for RubyGems matching a query string |
get_gem_versions | Get all available versions of a specific RubyGem |
get_gem_reverse_dependencies | Get gems that depend on a specific RubyGem |
get_owner_gems | Get all RubyGems owned by a specific user or organization |
get_gem_owners | Get the owners of a specific RubyGem |
Usage
Install dependencies:
npm install
Build the server:
npm run build
For development with auto-rebuild:
npm run watch
Installation
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-server-rubygems": {
"command": "/path/to/mcp-server-rubygems/build/index.js"
}
}
}
It should be similar on MCP clients like Cursor, Cline, etc -- just add the command from above in your config.
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspector
The Inspector will provide a URL to access debugging tools in your browser.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.