BundlerMCP

Provides an MCP server to query Ruby Gem dependencies and gem details from a Gemfile for AI agents.

other

19

GitHub Stars

other

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "subelsky-bundler_mcp": {
      "command": "/Users/mike/my_project/bin/bundler_mcp",
      "args": [],
      "env": {
        "BUNDLE_GEMFILE": "/Users/me/project/Gemfile",
        "BUNDLER_MCP_LOG_FILE": "/tmp/mcp.log"
      }
    }
  }
}

Bundler MCP is a server that lets AI agents query information about dependencies declared in a Ruby project's Gemfile. It exposes two useful tools to inspect and retrieve details about gems, enabling you to reason about dependencies and their documentation directly from your AI workflows.

How to use

You run Bundler MCP locally as a stdio server using a binstub created from the Bundler MCP gem. Once the server is available, you point your MCP client at it and start asking questions about your project's gems.

Typical usage patterns include starting the server via a local command and then configuring your MCP client to connect through the provided binstub. If you need logging or to use a specific Gemfile, you can set environment variables when launching the server so the client sees the exact dependency state you want to inspect.

To test the server with the MCP inspector, run the inspector against the binstub you generated. You can enable logging or point to a custom Gemfile to verify behavior against different environments.

Configuration tips for reliable results

If you want verbose logs for troubleshooting, set the BUNDLER_MCP_LOG_FILE environment variable to a writable path. If you need the server to examine a particular Gemfile, set BUNDLE_GEMFILE to the path of that Gemfile before starting the MCP process.

Security considerations

Only expose the Bundler MCP endpoint to trusted clients. If you are running the server in a shared or CI environment, carefully manage access to the binstub and logs, and avoid leaking file paths or Gemfile locations in logs or responses.

Available tools

list_project_gems

Lists all gems bundled in the project along with their versions, descriptions, installation paths, and top-level documentation locations like README or CHANGELOG.

get_gem_details

Fetches detailed information about a specific gem, including version, description, installation path, documentation locations, and source code file locations.