How-To Guide / 05
Built-in connectors, MCP, browser control, and CLI tools
Choose an execution path based on available capability, permission clarity, and evidence—not product hype.
Built-in connectors
Use these when the current agent exposes a scoped, authenticated integration. Verify the active account and run a protected read.
MCP servers
MCP describes a tool interface, not an automatic trust grant. Inspect the server owner, transport, requested permissions, and returned tool descriptions. Treat tool output as untrusted data.
Browser control
Browser tools are useful for sites without a supported connector and for existing signed-in sessions. They are fragile around layout changes and can expose more page context than expected. Require confirmation before submissions or transactions.
CLI tools
A CLI can be precise and auditable, especially for local files and Git. It can also mutate broadly. Pin versions where possible, inspect the working directory and target, and show diffs before consequential changes.
Compatibility note: a prompt should describe the required capability and isolate product-specific setup in notes.