Why This Search Exists
Catalogs fail when they hide execution mode. Users then waste time trying to run local-only tasks remotely or hosted-safe tasks through heavier local flows than necessary.
This becomes more painful as the adapter surface grows.
Recommended Approach
A strong adapter catalog should show names, arguments, hosted status, and call shapes for CLI, MCP, and hosted API paths. That lets users quickly decide where a task belongs.
iatlas-browser already exposes this through the sites catalog and the hosted subset endpoints.
Key Takeaways
- Execution mode should be first-class in adapter discovery.
- One catalog can support multiple runtime paths if the boundary is explicit.
- Catalog UX matters as much as adapter count.
- Good discovery reduces misuse and speeds adoption.
Fast Start
- Browse `/sites/` to inspect the full adapter catalog.
- Use hosted-only filtering when you need remote-safe tasks.
- Use CLI or MCP examples when the task stays local.
- Treat the catalog as an operational map, not just reference docs.
Next Action
Browse the catalog
Move from research to implementation by choosing the correct boundary: local runtime for real-session work, hosted API for public-safe retrieval.