# MCP

- Page: https://shared.btbytes.com/p/mcp
- Date: 2025-07-10
- Tags: google-chrome

**Model Context Protocol** -  is designed to let a single agent securely access tools, APIs, and data sources in a standardized way.

> On average, RAG, MCP, and NLWeb reach about 0.75 F1, while HTML stays near 0.67 and misses more. HTML agents also burn more compute, needing about 3x more tokens and 5x more time per task than others. So the study recommends RAG agents, often with GPT5 or cheaper GPT5 mini, and keeping HTML browsing only as backup. -- ([Steiner et al. 2025](https://arxiv.org/abs/2511.23281))

--

[Let your Coding Agent debug your browser session with Chrome DevTools MCP  \|  Blog  \|  Chrome for Developers](https://developer.chrome.com/blog/chrome-devtools-mcp-debug-your-browser-session)

- "Let your AI agent see and interact with your **live Chrome session**" -- [GitHub - pasky/chrome-cdp-skill: Give your AI agent access to your live Chrome session — works out of the box, connects to tabs you already have open · GitHub](https://github.com/pasky/chrome-cdp-skill)

---

See also [A2A](https://shared.btbytes.com/p/a2a)

## References

- Steiner, Peeters, Bizer (2025). [MCP vs RAG vs Nlweb vs HTML: A Comparison of the Effectiveness and Efficiency of Different Agent Interfaces to the Web (Technical Report)](https://arxiv.org/abs/2511.23281).