bdy integration exec tools

$bdy integration exec tools [options] <integration>

List the tools of the integration's MCP server Required scopes: INTEGRATION_USE

ARGUMENTS

integration

Integration identifier (required)

OPTIONS

--context <name>

Connection and scope context: default, git, link or a saved name. Overrides the globally active context for this invocation.

--examples

Show only examples; with this flag --format accepts text, json or jsonl

--verbose

Show REST API requests, responses, timing and retries on stderr

-w, --workspace <domain>

Workspace URL handle. Can be set via variable: BUDDY_WORKSPACE

-p, --project <name>

Project name. Can be set via variable: BUDDY_PROJECT

--scope <scope>

Force scope (WORKSPACE, PROJECT, ENVIRONMENT). By default calculated by provided options and environmental variables (--project, --environment, BUDDY_PROJECT, linked project)

--environment <identifier>

Environment identifier to scope the integration to. Resolves a workspace environment; add

--project

to point at a project environment

--format <text|json>

Output format: json, text. JSON CLI errors: {error:{code,message,hint}}, exit 1. Default: text (choices: "text", "json")

-h, --help

display help for command

Documentation for bdy v1.25.34

Last modified on Nov 3, 2026

tool get

Examples

List the tools of an integration's MCP server

bdy int exec tools integration-identifier$

Return the result as JSON

bdy integration exec tools integration-identifier --format json$