Model Context Protocol · MCP AI
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.
Mira el producto
Elige qué puede leer, automatizar y controlar la IA mediante permisos MCP.
Conexión MCP AI
Ambos endpoints son solo locales de forma predeterminada. Usa HTTP para la máxima compatibilidad local o HTTPS cuando tu cliente de IA requiera una URL segura y cifrada.
La mejor compatibilidad local para clientes MCP AI que se ejecutan en el mismo equipo que Social Browser.
http://127.0.0.1:60080/mcpTransporte MCP AI local cifrado para clientes y runtimes que requieren una URL HTTPS.
https://127.0.0.1:60081/mcpCertificado HTTPS
Social Browser genera un certificado local autofirmado y único para cada instalación. Abre Settings → MCP AI Permissions y usa Download certificate (.crt) o Copy PEM. Si tu cliente de IA aplica validación TLS estricta, importa ese certificado público en el almacén de confianza del runtime.
Why Social Browser MCP AI
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.
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.
Search engines, clean URL reading, semantic page snapshots, in-page find, structured extraction and concurrent multi-page research are first-class MCP AI operations.
Workflows, tasks, waits, verification, evidence, recovery and execution receipts help agents check what actually happened instead of trusting a toast message.
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
The catalog is discoverable by the AI, so clients do not need to memorize every operation name before they can work.
search.web structured web searchweb.read clean URL readingweb.snapshot, web.find and web.extractweb.readMany and searchAndReadbrowser.tabs.screenshot para el contenido de una pestaña administradabrowser.desktop.sources.list para monitores y ventanas de aplicacionesbrowser.desktop.screenshot para una pantalla o ventana seleccionadaVerdad de capacidades
Social Browser separa el descubrimiento de herramientas de la realidad de su implementación. Un agente puede comprobar si una operación está registrada, implementada, ejecutable según la política actual, bloqueada, pendiente de aprobación o expuesta solo como contrato estable.
browser.agent.capability.truth browser.agent.capability.check browser.agent.runtime.verify browser.agent.unattended.check ¿La operación está expuesta a MCP AI?
¿Existe un ejecutor real en esta versión?
¿Está permitida ahora, requiere aprobación o está bloqueada?
¿Puede el runtime comprobarlo previamente sin fingir que ocurrió un resultado externo?
Esto evita confundir un esquema o un resultado de autorización con la prueba de que una acción del host se ejecutó realmente.
Two-tier web reader
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.
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
Social Browser expone endpoints MCP AI locales mediante Streamable HTTP y HTTPS. HTTP es la opción recomendada por defecto para máxima compatibilidad; HTTPS está disponible cuando el cliente requiere una URL segura.
Keep Social Browser open on the computer that owns the Profiles and browser state you want the AI to use.
Usa HTTP para la configuración local más sencilla o HTTPS cuando el cliente requiera TLS. Ambos exponen las mismas herramientas MCP AI.
http://127.0.0.1:60080/mcphttps://127.0.0.1:60081/mcpReconnect 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.
Add this to %USERPROFILE%\.codex\config.toml, then restart Codex.
[mcp_servers.social_browser] enabled = true url = "http://127.0.0.1:60080/mcp"
Si Codex u otro cliente requiere HTTPS, usa https://127.0.0.1:60081/mcp y confía en el certificado público desde la configuración MCP AI de Social Browser si el runtime valida estrictamente los certificados locales.
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/mcphttps://127.0.0.1:60081/mcpLas conexiones remotas requieren un enlace explícito del servidor y configuración de seguridad de red. No se habilitan solo cambiando la IP del endpoint.
Recommended agent flow
The AI does not need to guess operation names or assume an action worked.
browser.agent.guide and capability discovery.browser.agent.tools.search to find the best operation for the goal.browser.agent.tools.get before calling unfamiliar tools.MCP AI operation policies
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.
Policies belong to the Social Browser user. An AI client cannot silently rewrite its own approval policy.
What can I ask it to do?
“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.”
«Captura la pestaña actual, luego la ventana de la aplicación si es necesario, inspecciona lo visible y dime qué cambió.»
Preguntas frecuentes
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.
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.
Yes. Operation-level MCP AI policies are designed for unattended tasks. You choose what runs automatically, what asks first and what is blocked.
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.
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.
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.
Sí. Usa https://127.0.0.1:60081/mcp. Social Browser crea un certificado local único para la instalación y permite descargar el archivo público .crt o copiar su PEM desde MCP AI Settings.
No. HTTP y HTTPS exponen el mismo catálogo de operaciones MCP AI. HTTPS cifra el transporte local; no desbloquea herramientas adicionales ni cambia tus políticas.
El endpoint HTTPS predeterminado usa un certificado local autofirmado por instalación. Los clientes con validación estricta pueden necesitar importar ese certificado público en el almacén de confianza del runtime. La clave privada nunca se exporta.
No. El acceso remoto está desactivado por defecto y requiere un enlace explícito del servidor y seguridad de red adecuada. El certificado HTTPS local predeterminado está pensado para localhost y direcciones loopback.
No. Capability Truth distingue las herramientas registradas de los ejecutores implementados y del estado actual de la política. Los agentes pueden comprobar la capacidad y la preparación del runtime antes de afirmar que una operación puede ejecutarse.
Browser control for AI
Download Social Browser, connect your MCP AI client and let your automation work with the same Profiles and browser state you already use.
MCP reference
Use the capability catalog for tool domains and contract rules, then use the client setup guide to connect a compatible MCP client.
Capability truth, stable resource identity, executor truth, and runtime discovery.
Open MCP Tools →Connect Streamable HTTP clients to the local Social Browser MCP endpoint.
Open MCP Clients →