Browser MCP Agent vs Screenpipe MCP
Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.
Direct Answer
Browser MCP Agent suits teams needing open-source access, browser navigation focus, and 133,530 GitHub stars in current listing data. Screenpipe MCP suits teams needing freemium $25/month, streamable http focus, and 21,163 GitHub stars in current listing data. This summary reflects catalog metadata only for decision support, not independent testing.
What this comparison weighs
- Pricing and free-tier availability
- License model and deployment fit
- GitHub adoption and contributor depth
- Catalog tags, integrations, and supported workflows
| Metric | Browser MCP Agent | Screenpipe MCP |
|---|---|---|
| GitHub Stars | 133.5K | 21.2K |
| Contributors | 95 | 154 |
| Last Commit | Aug 22, 2026 | Aug 22, 2026 |
| Open Issues | 14 | 101 |
| License | open-source | source-available |
| Pricing | open-source | freemium |
| Free Tier | Yes | Yes |
| Category | mcp-servers | mcp-servers |
| Trending | No | No |
Choose Browser MCP Agent if you need
- • Browser MCP Agent is the better fit when you need open-source licensing instead of source-available terms.
- • Browser MCP Agent is the stronger pick when Browser Navigation matters because that capability is listed only on its profile.
- • Browser MCP Agent shows broader GitHub adoption with 133,530 stars versus 21,163 for Screenpipe MCP.
Choose Screenpipe MCP if you need
- • Screenpipe MCP stands out for Streamable Http workflows that are not listed for Browser MCP Agent.
- • Screenpipe MCP is the stronger pick when Screen History Search matters because that capability is listed only on its profile.
- • Screenpipe MCP has a larger visible contributor base (154 vs 95).
Meaningful differences
- • Pricing model: Browser MCP Agent is listed as open-source, while Screenpipe MCP is listed as freemium from $25/month.
- • License: Browser MCP Agent uses open-source, while Screenpipe MCP uses source-available.
- • Workflow emphasis: Browser MCP Agent highlights Stdio, while Screenpipe MCP highlights Streamable Http.
- • GitHub adoption: Browser MCP Agent shows 133,530 stars versus 21,163 for Screenpipe MCP.
- • Contributor count: Browser MCP Agent lists 95 contributors and Screenpipe MCP lists 154.
Shared capabilities
- • Mcp
Shared Tags
Only in Browser MCP Agent
Only in Screenpipe MCP
Limitations and evidence
- • DeepYard compares structured public metadata; this is not an independent benchmark unless a test record is shown.
- • Signals such as stars, contributors, and last commit indicate public activity, not purchase fit or runtime quality.
- • Pricing and feature coverage reflect the stored listing snapshot and may lag vendor changes between refreshes.
Source links
About Browser MCP Agent
A Model Context Protocol agent that provides browser automation capabilities to AI assistants. It can navigate to URLs, click elements, fill forms, take screenshots, and extract structured data from web pages. Built as an MCP server, it integrates with Claude Code, Cursor, and other MCP-compatible clients to give AI models real-time web interaction abilities. Part of the awesome-llm-apps collection.
View full listingAbout Screenpipe MCP
Screenpipe MCP connects AI agents to a locally recorded work history. Its tools search OCR, accessibility, input, and audio records; summarize application activity; find meetings; inspect UI elements; and export recorded video while keeping the underlying screenpipe data on the user's machine.
View full listing