Struct ConnectorToolAdapter 

pub struct ConnectorToolAdapter { /* private fields */ }

One MCP server tool as a byob tool.

Implementations

impl ConnectorToolAdapter

pub fn new( name: String, plugin: PluginRef, local: bool, tool: ConnectorTool, connector: Arc<dyn Connector>, ) -> Self

pub fn on_server(self, server: &str) -> Self

The server’s key in the plugin’s mcpServers (named on MCP App views).

pub fn server(&self) -> &str

pub fn local(&self) -> bool

A local program (stdio) rather than a URL.

pub fn connector(&self) -> &Arc<dyn Connector>

pub fn connector_tool(&self) -> &ConnectorTool

The MCP tool behind this one (hints for the approval gate: ConnectorTool::needs_approval).

pub fn plugin(&self) -> &PluginRef

Trait Implementations

impl Tool for ConnectorToolAdapter

fn access(&self, _args: &Value) -> Access

A local server is unsandboxed code on this computer (Execute); an online one only reaches the network. Read-only hints are on Self::connector_tool for a finer gate.

fn spec(&self) -> ToolSpec

fn title(&self, _args: &Value) -> String

Short human title for the finished call, e.g. “Wrote notes.md”. args is untrusted.

fn run(&self, args: &Value, ctx: &ToolContext<'_>) -> ToolOutput

Do it. args is untrusted model output: validate everything, never panic.

fn pending_title(&self, _args: &Value) -> String

Title for the call before and while it runs, and on approval cards, e.g. “Write notes.md”. Defaults to “Run ”.

fn preview(&self, args: &Value, _workspace: &Path) -> Option<Preview>

A readable account of what the call would do, for approval cards: e.g. a diff for a file write. Reads only, no side effects; bounded. Defaults to the key arguments.

fn always_ask(&self, _args: &Value) -> Option<String>

Some(warning) if this call must be approved by a person every time: no policy, “always allow” grant or --auto-approve lets it run (e.g. installing system-wide). The warning is shown on the approval card.

fn concurrent(&self) -> bool

Calls of this tool start before the other calls of the same round and run side by side, each on a thread of its own (results still go back in call order). For tools that mostly wait, like delegate.