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.
@dundas
基本信息
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.
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"thinkbrowse": {
"command": "npx",
"args": [
"@thinkbrowse/mcp"
]
}
}
}工具列表暂未提供
当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。
点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。
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.
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.
It uses real browser sessions and cookies, avoiding headless conflicts and the need to manage separate browser profiles.
No, ThinkBrowse works alongside your existing browser without profile fights or forcing fresh sessions.
Yes, it uses real sessions and cookies from your Chrome browser, preserving authentication state.
ThinkBrowse works with Claude Code, Cursor, and any MCP client that supports the Model Context Protocol.

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U
OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.


Agent-Native Terminal

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.
评论