head to head · open source

page-agent vs mcp

page-agent has 29,683 GitHub stars, 2,641 forks, 94 open issues and last shipped yesterday. mcp has 7,355 stars, 606 forks, 0 open issues and last shipped 2 days ago. page-agent leads on adoption by 304% (29,683 vs 7,355 stars). page-agent is written in TypeScript under MIT; mcp is written in TypeScript under Apache-2.0. page-agent has attracted 9% as many forks as stars, mcp 8%. page-agent was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (browser-automation, mcp), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

page-agent ★ 30K mcp ★ 7.4K category Data & Analytics

← all 20902 open source comparisons

Side by side

page-agent mcp
GitHub stars ★ 30K ★ 7.4K
License MIT Apache-2.0
Written in TypeScript TypeScript
Last push 2026-11-13 2026-11-12
Forks ⑂ 2.6K ⑂ 606
Self-hosting Yes Yes
Data ownership Your server Your server

pick page-agent if

  • You weight community size — 30K stars and counting
  • You want the MIT license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full page-agent profile →

pick mcp if

  • You want the mcp feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches TypeScript
  • You evaluated both and mcp fits your workflow better

full mcp profile →

About page-agent

Page Agent The GUI Agent Living in Your Webpage. One script gives any web page its own AI agent. 🌐 English 中文 🚀 Demo 📖 Docs 📢 HN Discussion 𝕏 Follow on X ✨ Features 🎯 Easy integration No need for browser extension / python / headless browser . Just in page javascript. Everything happens in your web page. 📖 Text based DOM manipulation No screenshots. No multi modal LLMs or special permissions needed. 🧠 Bring your own LLMs Works with most mainstream models, including locally deployed ones. See supported models. 🐙 Optional chrome extension for multi page tasks. And an MCP Server (Beta) to control it from…

read the full page-agent overview →

About mcp

Browser MCP Browser MCP lets AI apps (Claude Code, Cursor, VS Code, Codex, Claude Desktop…) use your own Chrome: your signed in sites, your profile, in tabs of their own. Everything runs on your computer. Website and docs : browsermcp.io, docs Extension : Chrome Web Store, or build it yourself MCP server : @browsermcp/mcp on npm How it works Each AI app runs the MCP server ( npx @browsermcp/mcp@latest ), a small process that starts one daemon per user and forwards the app's browser tool calls to it. The daemon drives the browser's tabs with Playwright, through the extension: a thin chrome.debugger relay that…

read the full mcp overview →

More in Data & Analytics

Related comparisons

More Data Extraction & Web Scraping projects

Compare either of these against the rest of the Data Extraction & Web Scraping field.

Frequently asked questions

Is page-agent or mcp more popular?

page-agent has 29,683 GitHub stars and mcp has 7,355. page-agent has the larger community by that measure.

Are page-agent and mcp free?

Both are open source. page-agent is licensed under MIT and mcp under Apache-2.0. Neither carries a licence fee.

What is the difference between page-agent and mcp?

page-agent is written in TypeScript and mcp in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, page-agent or mcp?

Choose page-agent if you want the larger community (29,683 stars) or its MIT licence terms. Choose mcp if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.