Antidetect browser MCP for zero-touch AI runs: the AI handles captchas, SMS codes and email checks
Your AI can already click buttons and fill in forms, yet the run still stops at a reCAPTCHA-style challenge, an SMS code or an email confirmation and waits for someone to supply a phone number, read a code or dig through an inbox. It looks automated, but a person still has to sit and watch. NexBrowser now plugs four of its own services into its AI MCP: NexCaptcha, NexSMS, NexMask and NexIP. Whatever check the AI hits, it calls the matching service and keeps going, so the whole run finishes unattended.
Free plan: 1 member and 10 windows that never expire. All four services draw on one account balance.
Called directly over MCP
MCPHuman hand-offsNone
BillingOne shared balance
ModeUnattended
It looks automated, until a checkpoint needs a human
Plenty of antidetect browsers expose MCP these days, and AI really can drive the browser. Give it real work, though, and these steps still need someone to step in.
Complex captchas the AI cannot solve alone
A reCAPTCHA-style challenge is beyond what the AI can work out on its own. The run halts right there: either someone clicks through it by hand, or the whole task fails and starts over.
SMS codes need someone to fetch them
When sign-up or login asks for phone verification, a person has to find a number, wait for the text and type the code back in. Until they do, the AI just sits idle.
Email checks need someone to read the inbox
Steps that ask for email confirmation need someone to supply an address, open the inbox, find the message or code and hand it back. If the email turns up a few minutes late, so does the rest of the run.
So someone stays glued to the screen
Every checkpoint means a person waiting at the keyboard. An overnight job or a flow dozens of steps long is not truly unattended if even one step is waiting on a human.
AI captcha and SMS verification: whatever the check, the AI calls the right service
NexBrowser's AI MCP connects four in-house services that the AI can call directly inside NexBrowser. When the AI meets a verification step mid-task, it no longer pauses for a person; it calls the matching service and finishes the step itself.
The four checkpoints in a single run
No human hand-off- 01reCAPTCHA-style challengeNexCaptchasolves it and the run continues
- 02SMS verificationNexSMSgets a cloud number, reads the code, fills it in
- 03Email verificationNexMaskcreates a temporary or long-term inbox and confirms the email
- 04Clean exit IP and isolated profileNexIPresidential IP inside an isolated NexBrowser profile
Each of these checks used to need a human: find a number, wait for the code, check an inbox, click through the captcha. Now they are tools the AI can call. When it sees a captcha, it calls NexCaptcha to solve it. When it needs a phone number, it takes one of the NexSMS cloud numbers and reads the incoming code. When it needs an email address, it creates a temporary or long-term inbox with NexMask and uses the link or code from the confirmation email.
The browser work itself always happens inside NexBrowser. Each task runs in its own fingerprint profile with separate cookies, local storage and fingerprint parameters, and its exit IP can come straight from NexIP residential proxies. With a stable environment underneath and the verification steps covered, the AI can take a long, multi-step flow from the first page to the last without anyone taking over halfway.
- Captcha, SMS and email checks are completed by the AI calling a service, not by a person
- All four services are NexBrowser's own and are called from inside the client
- Browser actions run in isolated profiles, with residential IPs available as the exit
NexCaptcha · Captcha handling
Built for reCAPTCHA-style challenges the AI cannot solve on its own. The AI calls it on the spot, the captcha is solved and the run moves on.
NexSMS · Cloud numbers for SMS codes
When a page asks for phone verification, the AI takes a number from NexSMS, reads the incoming code and enters it, with nobody holding a phone.
NexMask · Temporary and long-term inboxes
Creates a temporary or long-term inbox on demand, so the AI receives the confirmation email and finishes the check without anyone opening a mailbox.
NexIP · Residential proxy IPs
Gives the profile running the task a residential exit IP and, together with NexBrowser profile isolation, keeps every run in a stable environment.
Field test: 10 accounts on the second run took less time than 5 on the first
We ran an account sign-up flow with several verification steps twice to see how AI Autopilot behaves in practice.
In the first run the AI had no prior experience and no memory, and the job was to complete the sign-up for 5 accounts. The whole flow went through, with every verification step along the way handled by the AI calling the matching service and nobody stepping in. Because it was exploring for the first time (what to fill in on each page, where a check would pop up, where to land afterwards), this run took noticeably longer.
That exploration was not wasted: it left the AI with a working memory of the flow. In the second run, using that memory, the AI worked through a batch of 10 accounts, and the total time came in under what the first run needed for 5. Messy manual work that used to need someone watching every step became a repeatable, standard operation that behaves more and more like a pipeline.
We are deliberately not quoting minutes or success rates here. Sites and flows differ too much for a single number to say anything useful about yours. One run on your own workflow will tell you far more than any figure on this page.
Total time across two runs
IllustrativeBar lengths only show which run took longer overall. They are not to scale.
How AI Autopilot differs from the AI Agent and AI browser automation
All three involve AI, but each solves a different stage of the problem, and they stack.
AI Agent
Turns a task into a flow
Describe the job in a sentence; the AI breaks it into editable flow steps and runs them across many isolated profiles.
Explore the AI AgentAI browser automation
Gives agents a runtime
Use NexBrowser as a persistent runtime for agents such as browser-use or Playwright MCP, with sessions that survive restarts.
Explore AI browser automationAI Autopilot
Covers the last mile
The checkpoints that used to need a person (captchas, SMS codes, email verification, a clean exit IP) are handled by the AI calling Nex services over NexBrowser MCP, so the run stays unattended.
In short: the AI Agent answers "how do I describe this task and break it into steps", AI browser automation answers "what browser does my agent run in", and AI Autopilot answers "who takes over when the run reaches a verification step". The answer is the AI itself.
Zero-touch AI automation for the work you already run
Any settled workflow that keeps getting interrupted by captchas, SMS codes or email checks, and has always needed someone on standby, is a good fit.
Onboarding the accounts your team runs
When your team needs new accounts for the business it operates, the AI fills in the details and completes SMS and email confirmation, leaving a person to sign off on the result.
End-to-end QA of your own sign-up and login
Regression-test your own product's sign-up, login and verification flows without a tester stepping in for captchas, SMS codes and email checks, so the whole path finally runs on its own.
Routine posting, check-ins and form filling
Scheduled posts, daily check-ins, form submissions and data entry for accounts you operate keep going when a captcha, SMS code or email check pops up, because the AI calls the matching service itself, with no one parked in front of the screen.
Long multi-step back-office tasks
Back-office jobs spanning dozens of steps and pages used to need someone on call for the one step that asked for verification. Now you can queue them overnight and check the results in the morning.
Use AI Autopilot only on accounts and sites you are authorised to operate, and follow each platform's terms of service and local law. Fraud, impersonation, creating accounts where a platform prohibits it, and fake engagement are expressly prohibited; see our acceptable use policy.
Connect your AI to the antidetect browser MCP in four steps
All four services are called from inside NexBrowser and share one account balance.
- 01
Install and sign in to NexBrowser
Download the Windows client (macOS is in development) and sign in. The free plan gives you 1 member and 10 windows that never expire, which is enough to try a real flow.
- 02
Connect your AI over MCP
Follow the docs to connect your AI agent to NexBrowser MCP. Once it is connected, NexCaptcha, NexSMS, NexMask and NexIP can all be called from inside NexBrowser.
- 03
Top up the shared balance
Residential proxy IPs, NexSMS numbers, NexCaptcha and NexMask all draw on the same NexBrowser account balance, so one top-up covers all four services.
- 04
Describe the task and let the AI finish it
Spell out the goal, the steps and which profiles to use. The AI runs it in isolated profiles and calls the right service whenever a captcha, SMS code or email check appears; all you do is review the result.
Read the MCP setup docsExact setup steps live in the documentation.
Coming soon: turn a successful AI run into an RPA script
Working memory already makes repeat runs faster, and the next step goes further. NexBrowser is reworking its RPA so the AI can convert a flow it has completed successfully into an RPA script. From then on, the same task can run from the script instead of the AI reasoning through every step again.
We expect this to improve execution efficiency by 10x or more once it ships. It is still in development, so timing and real-world results will be confirmed at release. Until then, flows that have already settled can be built in the existing no-code RPA builder.
- AI completes the flow once
- Converted into an RPA script
- Script reruns the task
AI Autopilot FAQ
Which verification steps can the AI handle on its own?
The three that most often stop a run. NexCaptcha handles reCAPTCHA-style complex captchas, NexSMS supplies a number and receives the SMS code, and NexMask creates a temporary or long-term inbox for email verification. The browser work itself runs in an isolated NexBrowser profile, with NexIP residential IPs available as the exit.
How much do AI captcha solving and SMS verification cost?
NexCaptcha, NexSMS, NexMask and NexIP all draw on one shared NexBrowser account balance, so a single top-up covers captchas, SMS numbers, inboxes and residential proxy IPs. Per-service rates are not listed on this page, so get in touch if you need them before topping up. The antidetect browser itself has a free plan with 1 member and 10 windows that never expire.
How is AI Autopilot different from the AI Agent feature?
The AI Agent turns a one-line task into editable flow steps and runs them across many isolated profiles. AI Autopilot covers the steps inside a flow that used to need a person (captchas, SMS codes, email verification and a clean exit IP) by letting the AI call Nex services over NexBrowser MCP. The two work together.
Is the first AI automation run much slower than later runs?
Yes, but only the first time. On its first run the AI has no prior experience, so it explores as it goes and takes noticeably longer, but it leaves behind a working memory of the flow. In our field test, after completing a sign-up flow for 5 accounts, the second run used that memory to process 10 accounts in less total time than the first 5 took.
Can the AI save a successful run as an RPA script?
Not yet; it is planned. NexBrowser is reworking RPA so the AI can convert a flow it has completed into an RPA script that reruns the task, and we expect that to improve execution efficiency by 10x or more. Until it ships, you can build settled flows by hand in the existing no-code RPA builder.
Have other questions? We're here to help anytimeContact Support →
Keep reading about AI automation
- AI-powered antidetect browserOne sentence in, a flow across many profiles out
- AI browser automationA persistent runtime for browser-use and MCP agents
- Virtual numbers for SMS verificationNexSMS cloud numbers that receive the code
- Antidetect browser with residential proxiesBind NexIP residential IPs to any profile
- No-code browser automationBuild settled flows and run them on a schedule
- Antidetect browser APILocal API, free with unlimited calls
Ready to manage every account profile in one place?
Install in 3 minutes. 10 free windows on sign-up, no credit card.
Free Download for WindowsAlready have an account? Sign in to the client to sync all profiles.