mcp-server-rubygems

Created By
6a year ago
A Model Context Protocol (MCP) server for fetching rubygems metadata via rubygems.org API
Overview

What is mcp-server-rubygems?

The mcp-server-rubygems is a Model Context Protocol (MCP) server designed to fetch RubyGems metadata using the RubyGems.org API.

How to use mcp-server-rubygems?

To use the mcp-server-rubygems, install the necessary dependencies, build the server, and configure it with your MCP client. You can also run it in development mode with auto-rebuild.

Key features of mcp-server-rubygems?

  • Fetch RubyGems metadata via the RubyGems.org API.
  • Tools for getting RubyGem information, searching for RubyGems, and retrieving gem versions.
  • Ability to find reverse dependencies and gem owners.

Use cases of mcp-server-rubygems?

  1. Developers can retrieve metadata for RubyGems to integrate into their applications.
  2. Users can search for specific RubyGems based on queries.
  3. Gem maintainers can check dependencies and ownership information.

FAQ from mcp-server-rubygems?

  • How do I install mcp-server-rubygems?

You can install it by running npm install and then build it using npm run build.

  • Can I run it in development mode?

Yes! You can run it in development mode with auto-rebuild using npm run watch.

  • What configuration is needed for MCP clients?

You need to add the server configuration to your MCP client, specifying the command to run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
6
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago