discover the exact installed catalog from the running browser
MCP AI reference
MCP tools should be discovered, not guessed.
Use this catalog to understand the capability surface, then let the connected MCP client query the running Social Browser build for the exact current tool names, schemas, executor truth and policy state.
Capability truth
Current capability contract snapshot
The exact installed catalog should always be discovered from the running browser. The website documents the contract model and major capability groups, while the client uses MCP discovery for exact tool names and schemas.
machine-readable names and schemas from the active MCP connection
check executor availability instead of trusting a stale count
effective availability also depends on the current browser policy
Tool catalog
Search the capability groups
This is a human-readable map. For machine-readable truth, use the MCP tools/list and discovery interfaces exposed by the installed browser.
Profiles & targets
Create, inspect, open and control persistent Profiles, tabs and windows while respecting stable resource identity.
Page interaction
Navigate, click, type, select, scroll, inspect elements and work with page state.
Automation Studio
Create and run workflows, automations, tasks, schedules, retries and verification-oriented flows.
Web intelligence
Search the web, read URLs, snapshot pages, find text and extract structured information.
Screenshots & visual context
Capture managed tabs, desktop sources, monitors or selected application windows.
Proxy operations
Import, edit, organize, assign and test proxy entries with long-running job support.
Files & host operations
Use approved filesystem and host operations when the installed capability contract and local policy allow them.
Downloads & uploads
Work with browser downloads, file inputs and file transfer workflows.
Diagnostics & capability truth
Inspect schemas, executor availability, readiness and current policy instead of assuming a registered name can execute.
Discovery
Let compatible agents search the tool catalog and inspect input schemas instead of hard-coding every tool name.
System & permissions
Apply operation-level Allow / Ask / Block policies and temporary or persistent grants.
Bulk & orchestration
Operate across selected Profiles/resources with explicit concurrency, timeouts and recovery rules.
Contract rules
Two rules prevent stale automation
The MCP contract exposes more than names. Agents should evaluate executor truth and resource identity before acting.
Executor Truth
A schema being discoverable is not enough. Check whether the installed build has an executable implementation and whether policy currently allows it.
Stable Resource Identity
Do not persist runtime targetId, webContentsId or runtime client IDs across restart/reconnect. Resolve the Profile/tab/window again from stable identity.
Runtime discovery
Connect and discover
Use the local MCP endpoint, reconnect after updates, then let the client discover the installed tools.
HTTP http://127.0.0.1:60080/mcp HTTPS https://127.0.0.1:60081/mcp MCP method: tools/list