iatlas-browser

Adapter catalog for the local runtime plus the hosted subset

Browse every callable site interface, then choose local runtime or hosted API correctly.

This page exposes the full adapter catalog used by iatlas-browser site. You can search by platform, inspect arguments, see whether a command is hosted or local-only, copy the exact CLI command, copy an MCP request payload, and call the hosted subset directly through the API. The key rule is simple: if an adapter depends on your real browser session, use the local runtime. If it is public and remote-safe, use the hosted subset.

One adapter catalog Local runtime is primary Hosted subset is curated and smaller
Catalog API Open API docs Local runtime homepage View lao-s

Execution boundary

Not every adapter belongs on the server

Adapter type Best path Why
Public read-only source Hosted API Server-safe, repeatable, and no personal session required
Authenticated personal workflow Local runtime Needs your own cookies, tabs, login state, or live page context
Browser-native interaction flow Local runtime Depends on real user session continuity and interactive state
Catalog discovery and planning Either Use this page or the catalog API to decide the correct execution boundary

Hosted execution

These adapters run directly on the remote server. They are public, read-only, and do not depend on a personal logged-in browser session. 

curl -s https://miaoda.vip/v1/sites/run \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"github/repo","args":{"repo":"miounet11/lao"}}'

Local runtime / MCP

Adapters that depend on your own login, browser state, tabs, or site-side stores remain local by design. Use the same adapter name through CLI or the MCP site_run tool. 

{
  "tool": "site_run",
  "arguments": {
    "name": "twitter/search",
    "args": {
      "query": "claude code"
    }
  }
}

Adapter list

Every command in one page