Most of my day is spent with Claude Code, and the browser was always the weak spot. Tools built on Playwright start a fresh profile, so the agent is logged out of everything. Pointing an agent at my main Chrome felt like a bad idea. So I built my own browser, Kinaya , and gave it an MCP server.

Adding it to Claude Code is one line:

claude mcp add kinaya -- /Applications/Kinaya.app/Contents/MacOS/kinaya —mcp

Enter fullscreen mode

Exit fullscreen mode

The browser starts itself if it isn't running. Getting from "the agent can click things" to "I actually let it use my accounts every day" took a few decisions that I think apply to anyone building agent tooling.

1. Every session gets its own background tab

Driving whatever tab is in front doesn't work once you want to keep browsing while an agent works, or when two Claude Code sessions run at once and fight over the same page.

So each MCP session opens its own background tab and all later calls act on it. The tab I'm looking at never moves.…