PRACTICAL GUIDE · DEVELOPER PREVIEW
Connect an AI agent to your real browser with MCP
Nabsun exposes browser tools through the Model Context Protocol (MCP). An external agent can read pages and use browser controls in the tabs you already have open.
Connect your agent
- Install and open Nabsun.
- Open Settings → Integrations → Connect an external agent.
- Copy the configuration generated by your installation into your MCP-compatible client. Use the client’s instructions for where to place it.
- Keep Nabsun running, then reconnect the client so it discovers the tools.
- Start with a read-only task on a public page before trying changes to an account.
The generated configuration contains a local bridge URL and token. Keep that token private. Use the current configuration from Nabsun rather than copying someone else’s port, token, or installation path.
A first task to try
Read the public documentation page open in Nabsun. List the installation requirements and link each finding to its source. Ask before navigating or changing anything.
Why use existing tabs?
The agent can work with the pages and signed-in sessions already in Nabsun. That can help with comparing open documentation or completing a workflow without setting up a separate automation browser. Review any proposed account changes carefully.
Approvals and limits
MCP browser calls use the same approval settings as the built-in assistant. Always allow and Autopilot change those permissions. Install only clients and tools you trust. Some websites will not work reliably with automation, and an agent can misunderstand a page.
External agent or built-in assistant?
Use MCP when you want your editor or another MCP client to operate Nabsun. To chat inside the browser instead, open the assistant or connect Codex or Claude Code through Extensions → Assistants. These are separate ways to use Nabsun.
Try Nabsun
MIT licensed. Windows x64 and Apple-silicon Mac builds. Cloud providers may require paid accounts. See the security documentation and current limits.