NextCore Browser

org.homestaynextcorePublished by homestaynextcore.orgv0.3.187Updated Nov 6, 2026

Multi-profile browser: AI agents create, open and drive isolated signed-in profiles with own proxy

The publisher's own server: core.blue

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

A local, desktop-only MCP server that lets an AI agent create, open and drive multiple isolated, signed-in browser profiles, each with its own proxy.

What you can do
  • Create and manage multiple isolated browser profiles.
  • Open profiles that are already signed in to sites.
  • Drive browsing inside a chosen profile, keeping sessions separate.
  • Route each profile through its own proxy.
  • No individual tools are documented in the supplied listing, so exact operations are unclear.
When to use it
Useful when an assistant needs to work across several separate browser identities or accounts at once, keep sessions and cookies apart, or send different browsing traffic through different proxies. Best suited to desktop setups where a local browser process can run.
Requirements
Runs as a local process on the user's machine over stdio; desktop only, with no web-hosted option. No packages, environment variables, headers or authentication are declared, so the runtime and browser it depends on are not specified in the listing.
Before you install
It drives signed-in browser profiles, so an agent can act inside accounts you are logged into, including actions that post, send or change data. Profiles are tied to proxies, and browsing traffic goes through those proxies, which may be third parties. Review which accounts and proxies you expose before connecting.

Installation

In SourceWeft

  1. Open NextCore Browser in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

12
  1. v0.3.187LatestNov 6, 2026
  2. v0.3.186Nov 6, 2026
  3. v0.3.185Nov 4, 2026
  4. v0.3.184Nov 4, 2026
  5. v0.3.183Nov 4, 2026
  6. v0.3.182Nov 4, 2026
  7. v0.3.181Nov 3, 2026
  8. v0.3.179Nov 3, 2026
  9. v0.3.173Nov 1, 2026
  10. v0.3.172Nov 1, 2026
  11. v0.3.170Nov 1, 2026
  12. v0.3.165Oct 30, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Core integrations