MCP Pointer

Combines a Chrome extension with a local MCP server so AI coding assistants can inspect DOM elements a developer points to in the browser, receiving rich context including text, CSS classes, computed styles, attributes, and React component metadata.

Evaluated Mar 06, 2026 (0d ago) vlatest
Homepage ↗ Repo ↗ Developer Tools dom chrome-extension web-development react css agentic-coding claude-code cursor
⚙ Agent Friendliness
71
/ 100
Can an agent use this?
🔒 Security
70
/ 100
Is it safe for agents?
⚡ Reliability
63
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
75
Error Messages
50
Auth Simplicity
80
Rate Limits
65

🔒 Security

TLS Enforcement
82
Auth Strength
68
Scope Granularity
60
Dep. Hygiene
75
Secret Handling
65

MCP routing/discovery tool. Routes tool calls to appropriate MCP servers. Security depends on connected MCP servers. Audit tool routing decisions.

⚡ Reliability

Uptime/SLA
65
Version Stability
65
Breaking Changes
60
Error Recovery
62
AF Security Reliability

Best When

You are actively developing a web UI and want your AI coding assistant to see exactly what you see in the browser without copy-pasting HTML snippets.

Avoid When

The workflow is fully automated or non-interactive; a human must manually hold Option/Alt and click to provide DOM context.

Use Cases

  • Point at a UI element in the browser to give an AI coding assistant precise DOM context for generating fix or styling code
  • Debug CSS issues by letting an AI see the full computed style tree of a selected element
  • Inspect React component hierarchy of a rendered element without manually digging through DevTools
  • Provide accurate selector context when writing automated tests or browser scripts

Not For

  • Headless or server-side workflows — requires a human to interact with a physical browser
  • Browsers other than Chrome/Chromium-based (Firefox not supported)
  • Production scraping or data collection pipelines

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: none
OAuth: No Scopes: No

No authentication required. Operates entirely locally over WebSocket on port 7007.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

MIT licensed, fully free. Chrome extension available via Web Store at no cost.

Agent Metadata

Pagination
none
Idempotent
Yes
Retry Guidance
Not documented

Known Gotchas

  • Requires a human to physically hold Option/Alt and click — not automatable without human in the loop
  • Port 7007 must be free; no configuration for alternate ports documented
  • React component detection is marked experimental and may not work on all React versions
  • Chrome extension must be manually installed and active before the MCP server can receive data

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for MCP Pointer.

$99

Scores are editorial opinions as of 2026-03-06.

5208
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered