Browser automation · MCP server
Auth fetch MCP: MCP server, setup and security
Auth fetch MCP is an open-source MCP server published on GitHub that lets an AI agent fetch login-protected page content through a persistent authenticated browser session. Its repository has 36 stars and its last commit is from October 23, 2026 and it is licensed under MIT.
What Auth fetch MCP does
According to its repository: “Fetch content from login-protected pages such as Notion, Google Docs, Jira and Confluence via a real browser login with persistent session caching.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Auth fetch MCP is listed under Browser automation, a category of 109 servers in the directory, where it ranks #73 by stars.
Topics declared by the repository: claude, playwright, web-scrapper.
Installing and connecting Auth fetch MCP
No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript. Listed systems: macOS, Windows, Linux.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
Points found for Auth fetch MCP:
- System access: the Browser automation category gives the agent control over files, a terminal, code or a browser. A booby-trapped instruction in content the agent reads (prompt injection) can then turn into an action.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on March 25, 2026, the ymw0407/auth-fetch-mcp repository has 36 stars and 11 forks, with 0 open issues. It has more stars than 47% of the servers in the directory. It received changes this month.
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
Auth fetch MCP is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Permissive licence (MIT)
Limitations
- Install from source
Avoid if…
- You cannot isolate the agent (sandbox, container)
Alternatives
- Firecrawl MCP Server7.7K ★
- Browser use119K ★
- MCP server browser39.4K ★
- Playwright MCP38.6K ★
- SeleniumBase MCP13.1K ★
- Scrapling MCP Server89.4K ★
Learn more
Frequently asked questions
How do I install Auth fetch MCP?
No package is declared in the MCP registry: clone the ymw0407/auth-fetch-mcp repository, follow its README, then declare the start command in your client's MCP configuration.
Is Auth fetch MCP free?
The code is published under the MIT licence and can be used free of charge.
Is Auth fetch MCP safe?
Points to watch: system access. Give it minimum rights and approve sensitive actions.
Is it an official server?
Nothing says so: it is a project published by ymw0407 on GitHub. Check who maintains it before giving it access.
What are the alternatives to Auth fetch MCP?
In the same category: Firecrawl MCP Server, Browser use, MCP server browser, and Playwright MCP. Firecrawl MCP Server and Browser use score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score