ThinkBrowse
@dundas
About ThinkBrowse
Connect Claude Code, Cursor, and any MCP client to your real Chrome browser. Real sessions, real cookies, no headless conflicts. Works alongside your browser — no profile fights, no fresh sessions.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"thinkbrowse": {
"command": "npx",
"args": [
"@thinkbrowse/mcp"
]
}
}
}Tools
No tools detected
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Overview
What is ThinkBrowse?
ThinkBrowse is an MCP server that connects MCP clients like Claude Code and Cursor to a real Chrome browser, using actual browser sessions and cookies without headless conflicts. It works alongside your existing browser, eliminating profile fights and the need for fresh sessions.
How to use ThinkBrowse?
Add ThinkBrowse as an MCP server in your supported client (e.g., Claude Code or Cursor). Once configured, it connects directly to your real Chrome browser, allowing clients to interact with live sessions and cookies.
Key features of ThinkBrowse
- Connects MCP clients to a real Chrome browser
- Uses real browser sessions and cookies
- Avoids headless conflicts
- No profile fights or session resets
- Works alongside your existing browser
Use cases of ThinkBrowse
- Automate web tasks in Claude Code with real browser state
- Use Cursor to interact with web apps that require authentication
- Connect any MCP client to a live browser session
- Run browser automation without headless mode issues
FAQ from ThinkBrowse
How is ThinkBrowse different from headless browser tools?
It uses real browser sessions and cookies, avoiding headless conflicts and the need to manage separate browser profiles.
Do I need to create a separate browser profile?
No, ThinkBrowse works alongside your existing browser without profile fights or forcing fresh sessions.
Does ThinkBrowse support real cookies and sessions?
Yes, it uses real sessions and cookies from your Chrome browser, preserving authentication state.
Which MCP clients are compatible?
ThinkBrowse works with Claude Code, Cursor, and any MCP client that supports the Model Context Protocol.
Frequently asked questions
How is ThinkBrowse different from headless browser tools?
It uses real browser sessions and cookies, avoiding headless conflicts and the need to manage separate browser profiles.
Do I need to create a separate browser profile?
No, ThinkBrowse works alongside your existing browser without profile fights or forcing fresh sessions.
Does ThinkBrowse support real cookies and sessions?
Yes, it uses real sessions and cookies from your Chrome browser, preserving authentication state.
Which MCP clients are compatible?
ThinkBrowse works with Claude Code, Cursor, and any MCP client that supports the Model Context Protocol.
Basic information
More Developer Tools MCP servers
BetterBugs
BetterBugsThe BetterBugs MCP (Model Context Protocol) enables you to load BetterBugs bug reports (via report links) directly to your preferred AI Agents and developer environments with MCP Client capabilities (such as Cursor, VS C
Sentry
modelcontextprotocolModel Context Protocol Servers
TranscriptFetch MCP Server
TranscriptFetchModel Context Protocol (MCP) server for TranscriptFetch: fetch YouTube transcripts, search, channels, and playlists from any MCP client.
MCP Inspector
modelcontextprotocolVisual testing tool for MCP servers
discoverGPT
Joe MonastierodiscoverGPT is visualAI's unified MCP gateway for AI commerce, exposing 29 tools across four capabilities on one canonical product catalog: trimodal search (natural-language, precise-color, and image-similarity), AI cata
Comments