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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@iflow-mcp/url-context-mcp

v1.0.1

Published

The URL-Context-MCP MCP Server provides a tool to analyze and summarize the content of URLs using Google Gemini's URL Context capability via the Gemini API.

Readme

URL-Context-MCP MCP Server

The URL-Context-MCP MCP Server provides a tool to analyze and summarize the content of URLs using Google Gemini's URL Context capability via the Gemini API.

Now also supports optional grounding with Google Search alongside URL Context. The server is designed to follow prompt-only orchestration: control whether to search or scrape via the instruction text you provide.

Installation

Prerequisites

  • Node.js 18+
  • Set GOOGLE_API_KEY in your environment

Get a Gemini API key

  • Sign in to Google AI for Developers and create an API key
  • Copy the generated key and set it as GOOGLE_API_KEY for this server
    • Cursor (project): add to .cursor/mcp.json under env
    • Claude CLI one-liner example: shown below
    • Or set it in your shell before launching

Published Package

This MCP server is now available as a published npm package: @taiyokimura/url-context-mcp

  • No need to clone the repository locally
  • Can be run directly via npx @taiyokimura/url-context-mcp@latest
  • See setup instructions below for Cursor and Claude Code

Build locally

cd /Users/kimurataiyou/url-context-mcp
npm i
npm run build

Setup: Claude Code (CLI)

Use this one-line command (replace with your real API key):

claude mcp add URL-Context-MCP -s user -e GOOGLE_API_KEY="sk-your-real-key" -- npx @taiyokimura/url-context-mcp@latest

To remove the server from Claude Code:

claude mcp remove URL-Context-MCP

Setup: Cursor

Create .cursor/mcp.json at your repository root:

{
  "mcpServers": {
    "URL-Context-MCP": {
      "command": "npx",
      "args": ["@taiyokimura/url-context-mcp@latest"],
      "env": { "GOOGLE_API_KEY": "sk-your-real-key" },
      "autoStart": true
    }
  }
}

Other Clients and Agents

Install in VS Code
Install in VS Code Insiders

Or add via CLI:

code --add-mcp '{"name":"URL-Context-MCP","command":"npx","args":["@taiyokimura/url-context-mcp@latest"],"env":{"GOOGLE_API_KEY":"sk-your-real-key"}}'

Follow the MCP install guide and use the standard config above:

  • Guide: https://modelcontextprotocol.io/quickstart/user

Add MCP Server with:

  • Command: npx
  • Args: ["@taiyokimura/url-context-mcp@latest"]
  • Env: GOOGLE_API_KEY=sk-your-real-key

Advanced settings → Extensions → Add custom extension:

  • Type: STDIO
  • Command: npx
  • Args: @taiyokimura/url-context-mcp@latest
  • Enabled: true

Example ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "url-context-mcp": {
      "type": "local",
      "command": [
        "npx",
        "@taiyokimura/url-context-mcp@latest"
      ],
      "enabled": true
    }
  }
}

Open Qodo Gen (VSCode/IntelliJ) → Connect more tools → + Add new MCP → Paste the standard config JSON → Save.

Follow Windsurf MCP documentation and use the standard config above:

  • Docs: https://docs.windsurf.com/windsurf/cascade/mcp

Configuration (Env)

  • GOOGLE_API_KEY: Your Gemini API key

Available Tools

  • analyze_urls
    • inputs:
      • urls: string | string[] (1-20 total)
      • instruction?: string
      • model?: string (default: gemini-2.5-flash)
      • use_google_search?: boolean (default: false) — enable grounding with Google Search in addition to URL Context

Prompt recipes (prompt-only orchestration)

  • Scraping-only (user provided URLs). Example instruction:
    • "ユーザーが貼ったこれらのURLのみをURLコンテキストで解析し、要約・キーファクト・引用URLを日本語で提示。外部検索は禁止。取得失敗は明示。"
  • Research with search + scraping, iterative up to 5 rounds. Example instruction:
    • "以下のテーマを調査。まずGoogle検索で候補を収集し、引用する全URLは必ずURLコンテキストで取得・要約・統合。カバレッジ不十分なら最大5回まで再検索・再収集して補完。日本語で簡潔に要約・キーファクト・引用URLを提示。"

Example invocation (MCP tool call)

{
  "name": "analyze_urls",
  "arguments": {
    "urls": "https://note.com/hawk735/n/nbc585d0774df",
    "instruction": "日本語で、要約・キーファクト・引用URLを簡潔に",
    "use_google_search": true
  }
}

Scraping-only example

{
  "name": "analyze_urls",
  "arguments": {
    "urls": ["https://example.com/post1", "https://example.com/post2"],
    "instruction": "ユーザーが貼ったこれらのURLのみをURLコンテキストで解析し、要約・キーファクト・引用URLを日本語で提示。外部検索は禁止。取得失敗は明示。"
  }
}

Research + scraping (iterative) example

{
  "name": "google_search",
  "arguments": {
    "query": "最新のNext.js 14のApp Routerのベストプラクティス",
    "instruction": "まずGoogle検索で候補を収集し、引用する全URLは必ずURLコンテキストで取得・要約・統合。カバレッジ不十分なら最大5回まで再検索・再収集して補完。日本語で簡潔に要約・キーファクト・引用URLを提示。"
  }
}

Troubleshooting

  • 401 auth errors: verify GOOGLE_API_KEY
  • Ensure Node 18+
  • For npx usage: npx @taiyokimura/url-context-mcp@latest should work without local build
  • For local development: use absolute path to build/index.js

References