Social BrowserProfiles, AI & automation
⌕
Download Free

Model Context Protocol · MCP AI

Give your AI real browser control.

Connect any MCP AI-compatible clients to a persistent Social Browser session. Search and read the web, control real logged-in Profiles, automate browser work, manage proxies and run long tasks from one endpoint.

Connect your AI See capabilities Read MCP AI guide
Persistent ProfilesStreamable HTTPHTTPS · TLS 1.2+Agent DiscoveryWeb Intelligence
MCP AI Permissions

See the product

Give AI controlled access to the real browser.

Choose what AI can read, automate, and control through MCP AI permissions.

Download FreePlans
One endpointBrowser, Profiles, automation and research.
Persistent stateUse real cookies, sessions and Profile context.
Full-control designThe user chooses operation policies.
Agent-readyDiscovery, schemas, verification and evidence.

MCP AI connection

HTTP or HTTPS. Same MCP AI tools, different transport.

Both endpoints are local-only by default. Use HTTP for maximum local client compatibility, or HTTPS when your AI client requires an encrypted secure URL.

Primary transport

HTTP endpoint

Recommended

Best local compatibility for MCP AI clients running on the same computer as Social Browser.

http://127.0.0.1:60080/mcp
  • Streamable HTTP
  • Local-only by default
  • No certificate setup required
Secure URL

HTTPS endpoint

TLS 1.2+

Encrypted local MCP AI transport for clients and runtimes that require an HTTPS URL.

https://127.0.0.1:60081/mcp
  • TLS 1.2 or newer
  • Unique certificate per installation
  • Same MCP AI capabilities as HTTP

HTTPS certificate

Trust the local certificate in strict clients.

Social Browser generates a unique local self-signed certificate for each installation. Open Settings → MCP AI Permissions, then use Download certificate (.crt) or Copy PEM. If your AI client performs strict TLS validation, import that public certificate into the client runtime trust store.

The private key is never exported.Certificate covers localhost and loopback addresses.HTTPS encrypts transport; it does not grant extra MCP AI permissions.
Remote access is off by default. Do not simply replace 127.0.0.1 with the PC IP. Remote listening must be enabled explicitly and secured for the network you trust. The default local HTTPS certificate is intended for localhost and loopback addresses.
Transport compatibility Streamable HTTP is the primary MCP AI transport. Social Browser also keeps compatibility paths for legacy HTTP/SSE and local stdio or named-pipe integrations.

Why Social Browser MCP AI

Not just remote clicks. Give AI first-class web intelligence.

Normal browser-control integrations often expose low-level actions and leave the AI to assemble everything itself. Social Browser MCP AI adds higher-level discovery, research, automation and verification on top of real persistent browser Profiles.

01

Real authenticated Profiles

AI can work inside persistent Profiles with the browser state already used by the user, including cookies, local storage, settings and user-supplied proxy context.

02

Search and read the web

Search engines, clean URL reading, semantic page snapshots, in-page find, structured extraction and concurrent multi-page research are first-class MCP AI operations.

03

Automation that can prove results

Workflows, tasks, waits, verification, evidence, recovery and execution receipts help agents check what actually happened instead of trusting a toast message.

04

You decide the policy

MCP AI operation settings can allow actions automatically, ask first or block them. This keeps unattended tasks practical while leaving the final policy with the device owner.

Capabilities

One MCP AI connection. The whole Social Browser workflow.

The catalog is discoverable by the AI, so clients do not need to memorize every operation name before they can work.

P

Profiles & browser control

  • Create, edit, open and organize persistent Profiles
  • Control tabs, windows, popups and downloads
  • Click, fill, type, scroll and execute JavaScript
  • Use real authenticated browser context
W

Web Intelligence

  • search.web structured web search
  • web.read clean URL reading
  • web.snapshot, web.find and web.extract
  • web.readMany and searchAndRead
A

Automation & tasks

  • Canonical Workflow action DSL
  • Automations define where and how work runs
  • Tasks bind, schedule and persist execution
  • Conditions, loops, variables and checkpoints
B

Bulk operations & jobs

  • Filter or ID-based bulk selection
  • Preview / dry-run before execution
  • Safe batch actions across mutable lists
  • Background jobs with progress, results and cancel
X

Proxy control

  • Import, edit, organize and assign proxies
  • Parallel testing with configurable concurrency
  • Editable free-proxy sources
  • Long-running test jobs without holding MCP AI requests open
AI

Agent runtime & verification

  • Capability discovery and semantic tool search
  • Schema lookup before execution
  • Inspect, wait, verify and recover
  • Evidence, receipts, Capability Truth and diagnostics
S

Scripts, settings & resources

  • User Scripts and compatible extensions
  • User-Agent, bookmarks, history and modes
  • Cookies, 2FA resources and browser state
  • Downloads and other list resources
OS

System layer & operation policies

  • HTTP fetch and system capability contracts
  • Operation-level Allow / Ask / Block settings
  • Temporary and persistent grants
  • Unattended-readiness checks before long tasks
V

Visual understanding & screenshots

  • browser.tabs.screenshot for managed tab content
  • browser.desktop.sources.list for monitors and app windows
  • browser.desktop.screenshot for a screen or selected window
  • PNG/JPEG, crop regions and native MCP AI image content
R

Recorder, actions & conditions

  • Record browser interaction events for reusable automation
  • Run maintained browser actions through the shared action layer
  • Evaluate, assert and wait for conditions
  • Combine recorded interaction with Workflows and verification

Capability Truth

Know what is actually implemented before an agent claims it can run.

Social Browser separates tool discovery from implementation truth. An agent can check whether an operation is registered, implemented, executable under the current policy, blocked, waiting for approval or exposed only as a stable contract.

browser.agent.capability.truth browser.agent.capability.check browser.agent.runtime.verify browser.agent.unattended.check
01Discovered

Is the operation exposed to MCP AI?

02Implemented

Does a real executor exist in this version?

03Policy-ready

Is it allowed now, approval-required or blocked?

04Verified

Can the runtime preflight it without pretending an external result happened?

This prevents a schema or authorization result from being mistaken for proof that a host action actually executed.

Two-tier web reader

Read fast when possible. Use the real browser when needed.

web.read starts with a fast direct HTTP reader for ordinary public pages. When JavaScript rendering, cookies, authenticated state, a Profile proxy, geographic context or other browser state is required, Social Browser can read the page through a real persistent Profile.

URL→Direct reader→Structured content
Protected / dynamic URL→Profile reader→Rendered page state
Example research request
searchAndRead({ query: "browser automation MCP", maxResults: 5, read: { mode: "auto", profileId: "my-profile" } })

Search → choose result URLs → read pages concurrently → return structured content to the AI.

Quick setup

Connect an MCP AI client in minutes.

Social Browser exposes local Streamable HTTP and HTTPS MCP AI endpoints. HTTP is the recommended default for maximum compatibility; HTTPS is available when the client requires a secure URL.

1

Run Social Browser

Keep Social Browser open on the computer that owns the Profiles and browser state you want the AI to use.

2

Choose HTTP or HTTPS

Use HTTP for the simplest local setup, or HTTPS when the client requires TLS. Both expose the same MCP AI tools.

http://127.0.0.1:60080/mcp
https://127.0.0.1:60081/mcp
3

Reconnect, then ask normally

Reconnect after MCP AI updates so the client reloads the tool catalog, then describe the task in normal language. Agent Discovery can find the right tools and schemas automatically.

Ready to try it?Download Social Browser, connect your AI client, and start with a real persistent Profile.Download Social Browser

Codex

Streamable HTTP

Add this to %USERPROFILE%\.codex\config.toml, then restart Codex.

[mcp_servers.social_browser] enabled = true url = "http://127.0.0.1:60080/mcp"

If Codex or another client requires HTTPS, use https://127.0.0.1:60081/mcp and trust the public certificate from Social Browser MCP AI Settings if the runtime validates local certificates strictly.

Other MCP AI clients

Standard endpoint

Choose a Streamable HTTP MCP AI server and use the same endpoint. Client UI and configuration file names differ between products.

http://127.0.0.1:60080/mcp
https://127.0.0.1:60081/mcp

Remote connections require explicit server binding and network security configuration. They are not enabled by changing the endpoint IP alone.

Recommended agent flow

Discover → understand → execute → verify.

The AI does not need to guess operation names or assume an action worked.

  1. Discover capabilitiesStart with browser.agent.guide and capability discovery.
  2. Search toolsUse browser.agent.tools.search to find the best operation for the goal.
  3. Get the schemaUse browser.agent.tools.get before calling unfamiliar tools.
  4. ExecuteCall the exact browser, automation, research or bulk operation.
  5. Verify the outcomeInspect page state, resource state or evidence instead of trusting a visual notification.

MCP AI operation policies

Built for automation that can keep running when you are away.

Social Browser uses operation-level policies. You decide which operation categories run automatically, which require approval and which are blocked. That means repetitive trusted tasks do not need to stop only because the user is not sitting at the computer.

Allow AutomaticallyRun this operation category without asking.
Ask Before ExecutionAllow once, temporarily or always when prompted.
BlockDo not execute this operation category.

Policies belong to the Social Browser user. An AI client cannot silently rewrite its own approval policy.

What can I ask it to do?

Use normal language. Let the MCP AI expose the right tools.

“Open my Client A Profile, go to the dashboard, export the current report and confirm the download finished.”
“Search the web for changes in these five competitors, read the most relevant pages and summarize only what changed this week.”
“Test every proxy in the list in parallel, keep the healthy and slow ones, and bulk-delete the failed results.”
“Create a Workflow that opens this page, fills the form, waits for the result, extracts the confirmation ID and verifies it was saved.”
“Find every Profile tagged Marketing, open the same URL in each one and run this approved workflow.”
“Inspect the current tab, find the correct submit button by role or label, click it, then verify the page state changed.”
“Capture the current tab, then capture the application window if needed, inspect what is visible and tell me what changed.”

FAQ

Common MCP AI questions

Does Social Browser MCP AI only control tabs and clicks?

No. Low-level page actions are available, but MCP AI also exposes Profiles, automation, tasks, proxy management, bulk operations, semantic page understanding, web search, clean URL reading, extraction, verification, recovery and diagnostics.

Can AI use an already logged-in browser session?

Yes. Profile-backed operations can use persistent Social Browser Profile state. This is useful when a page depends on cookies, an authenticated session, JavaScript rendering, Profile settings or user-supplied proxy context.

Can it work without me watching every action?

Yes. Operation-level MCP AI policies are designed for unattended tasks. You choose what runs automatically, what asks first and what is blocked.

Does Social Browser provide proxies?

No. Social Browser lets you add and manage your own proxies. The Proxy Manager can also work with editable public free-proxy list sources, but public proxies can be unstable and should be tested before use.

How does the AI know which MCP AI tool to use?

The Agent Discovery layer provides a guide, searchable tool catalog, schemas, capability truth and plan validation so compatible agents can discover operations instead of relying on a hard-coded list.

What happens after Social Browser MCP AI is updated?

Restart or reconnect the MCP AI client if it still shows an old tool catalog. Many clients cache tool definitions for the lifetime of the connection.

Can I use HTTPS for MCP AI?

Yes. Use https://127.0.0.1:60081/mcp. Social Browser creates a unique local certificate for the installation and lets you download the public .crt file or copy its PEM from MCP AI Settings.

Do HTTP and HTTPS expose different MCP AI tools?

No. HTTP and HTTPS expose the same MCP AI operation catalog. HTTPS encrypts the local transport; it does not unlock additional tools or change your operation policies.

Why can a strict HTTPS client reject the local certificate?

The default HTTPS endpoint uses a per-installation self-signed local certificate. Clients with strict certificate validation may need that public certificate imported into their runtime trust store. The private key is never exported.

Can I connect from another computer by replacing 127.0.0.1?

No. Remote access is disabled by default and requires explicit server binding plus appropriate network security. The default local HTTPS certificate is intended for localhost and loopback addresses.

Does every discovered MCP AI schema mean the action is implemented?

No. Capability Truth distinguishes registered tools from implemented executors and current policy state. Agents can check capability truth and runtime readiness before claiming that an operation can execute.

Browser control for AI

Give your AI a persistent browser, not a disposable session.

Download Social Browser, connect your MCP AI client and let your automation work with the same Profiles and browser state you already use.

Download Social BrowserExplore Automation StudioRead MCP AI guide

MCP reference

Discover the live capability surface

Use the capability catalog for tool domains and contract rules, then use the client setup guide to connect a compatible MCP client.

MCP Tools Catalog

Capability truth, stable resource identity, executor truth, and runtime discovery.

Open MCP Tools →

MCP Client Setup

Connect Streamable HTTP clients to the local Social Browser MCP endpoint.

Open MCP Clients →