URL-Context-MCP MCP
Provides tools to analyze and summarize content from URLs using Google Gemini's URL Context capability, with optional grounding through Google Search for enhanced research capabilities.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@URL-Context-MCP MCP summarize this article about AI trends: https://example.com/ai-article"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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_KEYin 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_KEYfor this serverCursor (project): add to
.cursor/mcp.jsonunderenvClaude 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@latestSee setup instructions below for Cursor and Claude Code
Build locally
cd /Users/kimurataiyou/url-context-mcp
npm i
npm run buildRelated MCP server: Scrapi MCP Server
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@latestTo remove the server from Claude Code:
claude mcp remove URL-Context-MCPSetup: 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:
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:
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_KEYEnsure Node 18+
For npx usage:
npx @taiyokimura/url-context-mcp@latestshould work without local buildFor local development: use absolute path to
build/index.js
References
Available Tools
2 toolsanalyze_urlsC
Analyze and summarize the content of given URLs using Google Gemini URL Context. Provide an optional instruction and model.
Inputs: urls (required), instruction, model, use_google_search.
google_searchB
Search the web using Google Search grounding via Gemini API. Provides search results with sources and citations.
Inputs: query (required), instruction, model.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: analyze_urls is for summarizing content from specific URLs, while google_search is for performing web searches to find information. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
Both tool names follow a consistent verb_noun pattern (analyze_urls, google_search) with clear, descriptive verbs and nouns. The naming style is uniform and predictable across the set.
With only 2 tools, the server feels under-scoped for a URL and search context MCP. While the tools cover basic analysis and search, the lack of additional operations (e.g., URL validation, result filtering, or advanced search options) limits functionality and may require agents to work around gaps.
The tool set is severely incomplete for a URL and search domain. It lacks essential operations such as URL validation, content extraction beyond summarization, search result refinement, or integration with other web tools. This will likely cause agent failures when handling more complex tasks.
Related MCP Connectors
One MCP URL for web search, page reading, pay-per-result data tools and a browser agent.
Unified 15-tool SEO, SERP, clean Markdown & GEO (LLM citation Share-of-Voice) MCP server.
Jina AI Reader/Search MCP — turn any URL into clean LLM-ready markdown, plus web search.
Related MCP Servers
- AlicenseAqualityDmaintenanceImplementation of Model Context Protocol (MCP) server that provides tools for accessing Google Cloud's Vertex AI Gemini models, supporting features like web search grounding and direct knowledge answering for coding assistance and general queries.20393 npm88MIT
- AlicenseAqualityDmaintenanceMCP server that converts URLs to clean Markdown/Text for LLM agents.579 npm5MIT
- AlicenseAqualityBmaintenanceMCP server for AI-powered research using Gemini. Provides fast grounded web search, deep autonomous research, URL extraction, and session management.988 PyPI10MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that fetches raw HTML content from a given URL to provide web context to LLMs.1-