A
licenseD
qualityD
maintenanceA Model Context Protocol server that allows AI models to fetch detailed information about npm packages and discover popular packages in the npm ecosystem.
1
6 npm
1
ISC
MCP Server RubyGems
by 6
Provides tools for fetching RubyGems metadata, including gem information, searching for gems, retrieving version information, finding reverse dependencies, and looking up ownership details through the RubyGems.org API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Server RubyGems get info about the rails gem"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-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 information about a RubyGem |
| Search for RubyGems matching a query string |
| Get all available versions of a specific RubyGem |
| Get gems that depend on a specific RubyGem |
| Get all RubyGems owned by a specific user or organization |
| Get the owners of a specific RubyGem |
Related MCP server: GitHub Tools MCP Server
Usage
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchInstallation
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 inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Available Tools
6 toolsget_gem_ownersC
Get the owners of a specific RubyGem
Inputs: $schema, additionalProperties, properties, required, +1 more.
get_gem_reverse_dependenciesC
Get gems that depend on a specific RubyGem
Inputs: $schema, additionalProperties, properties, required, +1 more.
get_gem_versionsC
Get all available versions of a specific RubyGem
Inputs: $schema, additionalProperties, properties, required, +1 more.
get_owner_gemsC
Get all RubyGems owned by a specific user or organization
Inputs: $schema, additionalProperties, properties, required, +1 more.
get_rubygem_infoC
Get information about a RubyGem from the RubyGems.org API
Inputs: $schema, additionalProperties, properties, required, +1 more.
search_rubygemsA
Search for RubyGems matching a query string. The search matches against gem names and descriptions. Returns up to 10 results by default (customizable with limit parameter), ordered by relevance. Example queries: "authentication", "rails middleware", "aws sdk"
Inputs: $schema, additionalProperties, properties, required, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
A3.5/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no ambiguity: get_gem_owners retrieves owners of a gem, get_gem_reverse_dependencies finds dependent gems, get_gem_versions lists versions, get_owner_gems shows gems owned by a user/org, get_rubygem_info provides general gem information, and search_rubygems searches for gems. The descriptions clearly differentiate their functions, making misselection unlikely.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes followed by descriptive nouns (e.g., get_gem_owners, search_rubygems). The naming is uniform throughout, using snake_case consistently without any deviations or mixed conventions.
Tool Count5/5
With 6 tools, the count is well-scoped for a RubyGems server, covering key operations like searching, retrieving info, versions, dependencies, and ownership. Each tool earns its place without feeling excessive or insufficient for the domain's typical needs.
Completeness4/5
The tool set provides comprehensive read-only coverage for querying RubyGems, including search, info retrieval, version history, dependencies, and ownership. A minor gap exists in write operations (e.g., publishing or managing gems), but this is reasonable for a query-focused server, and agents can work around this limitation.
Maintenance
ActivityInactive
ResponsivenessOutdated data
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for Studex tools, notifications, and profile integrations
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceModel Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.1-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server for querying PyPI package information, dependencies, and compatibility checking. Supports advanced dependency analysis, download statistics, and trending analysis.281 PyPI19MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for querying package registries (npm, PyPI, crates.io) to retrieve metadata, release timelines, and maintenance signals.1MIT