mcp-fetch-page
v0.3.1
Published
MCP Server for browser-based web page fetching with automatic cookie support
Maintainers
Readme
MCP Fetch Page
Browser-based web page fetching with automatic cookie support and CSS selector extraction.
Features
- 🤖 Browser Automation: Full JavaScript rendering with Puppeteer
- 🍪 Automatic Cookie Management: Loads all saved cookies automatically
- 🎯 CSS Selector Support: Extract specific content with selectors
- 🌐 Domain Presets: Built-in selectors for common websites
- 📱 SPA Support: Fully supports dynamic content and AJAX
Quick Start
1. Configure MCP Server
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"mcp-fetch-page": {
"command": "npx",
"args": ["-y", "mcp-fetch-page@latest"]
}
}
}Restart Claude Desktop.
2. Install Chrome Extension (Optional - for authenticated pages)
Download and install the Chrome extension to save cookies from authenticated sessions:
📥 Download Extension from Releases
Installation steps:
- Download
mcp-fetch-page-extension-vX.X.X.zipfrom the latest release - Unzip the file
- Open Chrome and go to
chrome://extensions/ - Enable "Developer mode" (top right)
- Click "Load unpacked" and select the unzipped folder
Usage
Basic Usage
- Login to a website in Chrome
- Click the "Fetch Page MCP Tools" extension icon
- Click "Save Cookies" button
- Use in Claude/Cursor:
fetchpage(url="https://example.com")
Advanced Usage
// Basic fetching with automatic cookie loading
fetchpage(url="https://example.com")
// Extract specific content with CSS selector
fetchpage(url="https://example.com", waitFor="#main-content")
// WeChat articles (automatic selector)
fetchpage(url="https://mp.weixin.qq.com/s/xxxxx")
// Run in non-headless mode for debugging
fetchpage(url="https://example.com", headless=false)Domain Presets
The system automatically uses optimized selectors for:
- mp.weixin.qq.com →
.rich_media_wrp(WeChat articles) - wx.zsxq.com →
.content(Knowledge Planet) - cnblogs.com →
.post(Blog Garden) - Add more in
mcp-server/domain-selectors.json
Debug Tools
# Standalone debug script (recommended for development)
cd mcp-server
node debug.js test-page "https://example.com"
node debug.js test-spa "https://example.com" "#content"
# MCP Inspector (for integration testing)
npx @modelcontextprotocol/inspector
# Then visit http://localhost:6274Parameters
url(required): The URL to fetchwaitFor(optional): CSS selector to extract specific contentheadless(optional): Run browser in headless mode (default: true)timeout(optional): Timeout in milliseconds (default: 30000)
File Structure
mcp-fetch-page/
├── package.json # npm package config
├── package-lock.json # npm lockfile
├── node_modules/ # npm dependencies
├── README.md # This file
├── README-zh.md # Chinese version
├── CLAUDE.md # Claude Code usage guide
├── chrome-extension/ # Chrome extension
│ ├── manifest.json
│ ├── popup.js
│ ├── popup.html
│ └── background.js
└── mcp-server/ # MCP server
├── server.js # Main server
├── debug.js # Debug tools
└── domain-selectors.json # Domain selector configTroubleshooting
- Extension not working: Make sure you're on a normal website (not chrome:// pages)
- No cookies found: Try logging in again and saving cookies
- MCP not connecting: Check Node.js installation and restart your editor
- Path error: Make sure to use full path
/Users/YOUR_USERNAME/...instead of~/... - CSS selector not working: Verify the selector exists on the page
That's it! 🍪
