It is now easier to connect your own AI agent to a real browser without paying for the browser vendor’s AI plan.
In August 2026, Opera said Opera Neon, its AI browser, can connect external AI agents even without a subscription to Neon’s own AI features.
The two connection paths are MCP (Model Context Protocol) and the local Opera Browser CLI.
The point is not “the browser’s AI,” but “your AI using the browser as hands,” now available in the free tier.
What became free
Opera Neon is an experimental AI browser with its own features such as autonomous browsing, research, and generative agents.
Until now, it was easy to see it as a product that expected a subscription for serious use.
This announcement draws a clearer line:
- The Free plan lets you connect your own agents via MCP or CLI
- The paid Standard plan is needed when you want Neon’s own AI capabilities
Standard still covers Neon’s own services, including autonomous browsing, deep research, Skills, automation, and generative AI agents.
In other words, “buying Opera’s AI” and “letting your AI drive Opera” are now separate.
How MCP and CLI differ
MCP is a common protocol that lets AI tools talk to apps and services.
If Opera Neon acts as an MCP server, a compatible AI client can request live browser actions.
Its strength is headful control: working inside a logged-in, on-screen session.
The CLI, opera-browser-cli, is an official local tool.
Local agents and scripts can drive Neon by command, and cloud MCP clients cannot reach it by design.
The CLI also includes token compression to reduce how many tokens agents spend on browser use. Some reports say the cut can reach about 66%.
Opera’s setup flow is roughly:
- Download Opera Neon (Windows / macOS)
- Sign in with an Opera account for MCP (not required for CLI)
- Connect your own agent using the MCP or CLI instructions
What changes in practice
Until now, agent web automation often leaned on headless browsers or custom scrapers.
Neon’s free connection widens the path of letting an agent work as an extension of a normal browser.
- Let your agent operate logged-in admin screens or SaaS tools
- Carry research, input, and checks in a real on-screen browser
- Drive the browser from local AI coding tools via CLI
- Split paths: MCP from cloud AI, CLI from on-device AI
For development teams and IT, the design question is less “which AI” and more “how much control that AI should get.”
Checks before adoption
Free access does not mean you should hand over everything.
- Keep agent permissions minimal (tab reading, typing, purchases, and so on)
- Try with a test account, not a production account
- Keep screens with secrets or customer data out of the connection
- Protect MCP connection URLs and credentials
- Do not confuse the free browser-control path with paid Neon AI features
MCP is convenient, but it also opens an authenticated session to an external AI.
CLI stays local and unreachable from the cloud, yet the PC’s own permissions still move to the agent.
“It connects for free” and “it is safe to use” are different questions.
Summary
Opera Neon now lets you connect your own AI agents on the free plan.
MCP and CLI make it easier for both cloud AI and local AI to drive a real browser.
Paid plans remain for Neon’s own AI, so “borrowing the browser” and “using Opera’s AI” should be planned separately.
At Makoto Tejima, when planning AI agent adoption, we emphasize design that includes existing-system integration, permission management, and human confirmation points.
Please feel free to consult us about browser automation, MCP integration, or secure agent design.
