Point to browser DOM elements for agentic coding tools via MCP!
MCP Pointer is a local tool combining an MCP Server with a Chrome Extension:
- 🖥️ MCP Server (Node.js package) - Bridges between the browser and AI tools via the Model Context Protocol
- 🌐 Chrome Extension - Captures DOM element selections in the browser using Option+Click
The extension lets you visually select DOM elements in the browser, and the MCP server makes this textual context available to agentic coding tools like Claude Code, Cursor, and Windsurf through standardized MCP tools.
- 🎯 Option+Click Selection - Simply hold Option (Alt on Windows) and click any element
- 📋 Complete Element Data - Text content, CSS classes, HTML attributes, positioning, and styling
- ⚛️ React Component Detection - Component names and source files via Fiber (experimental)
- 🔗 WebSocket Connection - Real-time communication between browser and AI tools
- 🤖 MCP Compatible - Works with Claude Code and other MCP-enabled AI tools
See MCP Pointer in action: Option+Click any element in your browser, then ask your AI assistant to analyze it. The AI gets complete context about the selected element including CSS properties, React source files, and more.
Note: Chrome extension is not yet published on Chrome Web Store. You'll need to build and install it manually for now.
Use npx to automatically configure the MCP server with your AI tool:
# Configure MCP Pointer for your AI tool
npx -y @mcp-pointer/server config claude # Automatically configures Claude Code
npx -y @mcp-pointer/server config cursor # Opens Cursor deeplink for automatic installation
npx -y @mcp-pointer/server config windsurf # Automatically updates Windsurf config file
npx -y @mcp-pointer/server config manual # Shows manual configuration for other tools
Optional: You can install globally with
npm install -g @mcp-pointer/server
to usemcp-pointer
instead ofnpx -y @mcp-pointer/server
Current method (Chrome Web Store not available yet):
- Download the latest release from GitHub Releases (coming soon)
- Or build from source: Follow the build instructions in CONTRIBUTING.md
Load in Chrome:
- Open Chrome → Settings → Extensions → Developer mode (toggle ON)
- Click "Load unpacked"
- Select the
packages/chrome-extension/dist/
folder - The MCP Pointer extension should appear in your extensions list
- Navigate to any webpage
- Option+Click any element to select it
- Ask your AI to analyze the targeted element!
Your AI tool will automatically start the MCP server when needed using the npx -y @mcp-pointer/server start
command.
Available AI Tools:
getTargetedElement
- Get comprehensive info about the selected elementclearTargetedElement
- Clear the current selectiongetPointerStatus
- Check system status and statistics
- Element Selection: Content script captures Option+Click events
- Data Extraction: Analyzes element structure, CSS, and framework info
- WebSocket Transport: Sends data to MCP server on port 7007
- MCP Protocol: Makes data available to AI tools via MCP tools
- AI Analysis: Your assistant can now see and analyze the element!
- Basic Info: Tag name, ID, classes, text content
- CSS Properties: Display, position, colors, dimensions
- Component Info: React component names and source files (experimental)
- Attributes: All HTML attributes
- Position: Exact coordinates and dimensions
- Source Hints: File paths and component origins
- ⚛️ React - Component names and source files via Fiber (experimental)
- 📦 Generic HTML/CSS/JS - Full support for any web content
- 🔮 Planned - Vue component detection (PRs appreciated)
- ✅ Chrome - Full support (tested)
- 🟡 Chromium-based browsers - Should work (Edge, Brave, Arc - load built extension manually)
- Make sure MCP server is running:
npx -y @mcp-pointer/server start
- Check browser console for WebSocket errors
- Verify port 7007 is not blocked by firewall
- Restart your AI assistant after installing
- Check MCP configuration:
mcp-pointer config <your-tool>
- Verify server is running:
npx -y @mcp-pointer/server start
- Some pages block content scripts (chrome://, etc.)
- Try refreshing the page
- Check if targeting is enabled (click extension icon)
- LLM-configurable detail levels (visible text only, all text, CSS levels)
- Progressive refinement options
- Token-conscious data fetching
- Vue.js component detection
- Better React support (React 19 removed
_debugSource
, affecting source mapping in dev builds)
- Base64 encoding for images (img tags)
- Screenshot capture of selected elements
- Separate MCP tool for direct visual content retrieval
MIT License - see LICENSE file for details
We welcome contributions! Please see our CONTRIBUTING.md guide for development setup and guidelines.
Made with ❤️ for AI-powered web development
Now your AI can analyze any element you point at! 👆