RubyGems MCP for AI. Audit ownership, track versions, and map dependencies.

Yo, check this out. This server lets your AI agent handle the whole Ruby ecosystem, straight up from the command line into natural conversation. You're not dealing with some clumsy API playground; you're managing gem metadata, ownership records, and download stats for the world’s largest package registry.

Gem Discovery & Metadata Retrieval

You can search active gems using search_gems; it returns results paginated at 30 per page based on a query string. Need basic info on one specific gem? Use get_gem. For a quick list of every registered gem name, get_compact_index_names gives you a newline-separated dump. If you need more detail on all available versions for a single package, run get_compact_index_info.

You can also grab a compact index containing the names, versions, and MD5s for every gem using get_compact_index_versions. To get the full rundown of version numbers for any given gem, call get_gem_versions; alternatively, you'll find the absolute most recent build number with get_latest_gem_version, or narrow down versions created between specific dates using get_timeframe_versions (you gotta use ISO8601 format for those dates).

You can get core information about a single gem version using API v2 via get_gem_version_details_v2.

Usage Tracking and Dependency Mapping

Want to know how popular stuff is? You can retrieve the total download count across every gem in the registry with get_downloads. For specific metrics, you'll get download statistics for a single gem and its exact version number using get_gem_downloads. To see which gems depend on yours, check the dependency graph using get_reverse_dependencies.

You can also pull usage data for all 50 most recently updated gems with get_just_updated_activity or see the 50 newest additions to the registry via get_latest_activity.

Ownership and Access Control

The server lets you audit who owns a gem. You can view every current owner or account for a package using get_gem_owners. If you need to change ownership, use add_gem_owner to bring on a new owner account, remove_gem_owner to take someone off the list, or update_gem_owner to modify an existing role.

You'll also see which gems your user account has permission to publish updates for by calling get_owner_gems, and you can get a complete list of all gems you have publishing access to using list_my_gems. If you want to see basic public info about any user, run get_profile; or check out your own credentials and MFA setup with get_my_profile.

Lifecycle Management and Publishing

You're managing the code base here. You can submit a brand new version of your gem by uploading its compiled, base64 encoded binary data (.gem file) using push_gem. If you need to remove a specific version from public resolution—like it had a bug—use yank_gem to take that version offline. For managing external connections, you can set up a webhook endpoint that triggers on specified gem events (it applies globally if you use *), and then test whether that setup actually works by manually firing the webhook with fire_webhook; you'll remove any configured hook using remove_webhook.

You can list all webhooks already registered for your account via list_webhooks.

Authentication & Account Management

Your AI client handles authentication too. You retrieve your personal API key using HTTP Basic Authentication credentials with get_api_key, and if you're dealing with OAuth, you can swap an OIDC ID token for a temporary, usable API key by calling exchange_oidc_token.