bdy integration exec

View as Markdown
$bdy integration exec [options] [command]

Use the integration's MCP server: list its tools, show one, call it, and manage executions

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
-h, --help
display help for command
AVAILABLE COMMANDS
Call a tool of the integration's MCP server Required scopes: INTEGRATION_USE
Cancel a running execution Required scopes: INTEGRATION_USE
List integration executions Required scopes: INTEGRATION_READ
Show execution logs Required scopes: INTEGRATION_READ
Show the status of an execution Required scopes: INTEGRATION_READ
Show a tool with its arguments (input schema) Required scopes: INTEGRATION_USE
List the tools of the integration's MCP server Required scopes: INTEGRATION_USE

Documentation for bdy v1.25.34

Last modified on Nov 3, 2026

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$
Show a tool and the arguments it takes
bdy int exec tool integration-identifier search_issues$
Get the full tool definition with its input schema
bdy int exec tool integration-identifier search_issues --format json$
Call a tool
bdy int exec call integration-identifier search_issues --args '{"query":"is:open","limit":10}'$
Call a tool with arguments from a file
bdy int exec call integration-identifier create_task --args @task.json$
Call a tool marked as destructive without confirmation
bdy int exec call integration-identifier delete_task --args '{"id":"123"}' -f$
Return the execution with the parsed result as JSON
bdy integration exec call integration-identifier search_issues --args '{"query":"bug"}' --format json$