Skip to main content
The core CLI workflow is: search → execute → if auth error → connect → retry.

Search for Tools

Filter by service:
Limit results:

Execute a Tool

By ID:
By slug:
By exact name:
Resolution is exact, never fuzzy. A slug is looked up first; otherwise the name is compared to the search results with case and punctuation ignored (gmail-send-email and Gmail - Send Email are the same key) and must match exactly one tool. Anything else exits 1 with error: not_found and a candidates list of name, id and slug to pick from; nothing is executed. Check what a reference resolves to with --dry-run, which prints tool_id, tool_name and resolved_by (uuid, slug or name).

Data Input (-d flag)

The -d flag accepts multiple formats:

Get Schema

Inspect a tool’s parameter schema before executing:

Dry Run

Validate parameters without executing:

Connect to a Service

If execution fails with an auth error, the CLI tells you what to run:

Batch Execute

Execute up to 10 tools from a JSON file:

Tool Info

Get full details for a specific tool:

Agent Usage

Agents call the CLI via subprocess. When stdout is piped (not a TTY), output defaults to JSON automatically:

Unix Pipe Examples