npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@move32/mcp-server-drive

v0.1.3

Published

Google Drive MCP server. Per-user OAuth, read-only, exports Google Docs/Sheets/Slides as text.

Readme

mcp-server-drive

A Google Drive MCP server. Runs locally as a subprocess of any MCP client (Claude Code, etc.), authenticates the user with their own Google account via OAuth, and exposes three read-only tools.

Tools

| Tool | What it does | |---|---| | search_files | Run a Drive query string (name = '…' and mimeType = '…' and trashed = false). Returns id, name, mimeType, parents, modifiedTime. | | read_file_content | Fetch a file's content. Google Docs auto-export to text/markdown, Sheets to text/csv, Slides to text/plain. Override with mime_type. Non-native files come back via alt=media. | | get_file_metadata | Full Drive metadata for a file: name, mimeType, parents, modified/created time, size, owners, webViewLink. |

Scope: https://www.googleapis.com/auth/drive.readonly. The server never writes to Drive.

Setup

  1. Register an OAuth client in Google Cloud Console:

    • Create a project (or reuse one).
    • Enable the Google Drive API.
    • APIs & Services → Credentials → Create credentials → OAuth client ID → Application type: Desktop app.
    • Click Download JSON.
  2. Save the downloaded file as ~/mcp-server-drive-tokens.json on every machine that will run the server. The server reads Google's JSON as-is and accepts the three shapes Google produces: {installed: {...}} (Desktop apps), {web: {...}} (Web apps), or a flat {client_id, client_secret, ...} blob.

The file holds the OAuth client credentials (one per Cloud project, shared across users of that client). It is NOT the per-user refresh token — that's written separately after the consent flow; paths below.

Install

npx -y @move32/mcp-server-drive

Or wire it into a plugin's .mcp.json:

{
  "mcpServers": {
    "gdrive": {
      "command": "npx",
      "args": ["-y", "@move32/mcp-server-drive"]
    }
  }
}

On first tool call, a browser tab opens for Google's consent screen. The user signs in with their personal Google account, grants read access, and the server stores the refresh token. Subsequent calls reuse the token silently. Access-token refresh is automatic.

Development

npm install
npm run lint          # ESLint 9 flat config, zero warnings
npm run format:check  # Prettier
npm run typecheck     # tsc --noEmit
npm test              # Vitest unit tests
npm run test:coverage # with v8 coverage
npm run build         # emit to dist/