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
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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
mcp-excalidraw
yctimlinMCP server and Claude Code skill for Excalidraw — programmatic canvas toolkit to create, edit, and export diagrams via AI agents with real-time canvas sync.
AptiBuild AI — Career Intelligence
ParklandBuildsAptiBuild AI MCP Server — career, labor market, and business idea intelligence for AI agents. 11 tools covering real-time FRED labor market signals, BLS wage data (126 occupations), AI-generated app ideas, career paths,
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
MCP-Scan: An MCP Security Scanner
invariantlabs-aiSecurity scanner for AI agents, MCP servers and agent skills.
TalkToFigma
sonnylazuardiTalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.
Comments