InProcessTransport
Direct, in-process access to a ToolRegistry — no JSON-RPC, no network. Intended for on-device LLMs that call tools straight from the same process. Mirrors the surface an MCP client gets over HttpTransport (tools, resources, prompts) without the protocol envelope.
Constructors
Functions
Invoke a tool; honours runtime gating and runs on Dispatchers.IO (see ToolRegistry.executeTool).
Like callTool, delivering the tool's reportProgress updates to onProgress.
Prompts whose McpPrompt.requiredTools are all enabled, like prompts/list.
Resources of every provider whose required tools are enabled, like resources/list (unpaginated). Providers run in parallel; one that fails or times out contributes nothing.
URI templates of every provider whose required tools are enabled, like resources/templates/list.
The enabled tools serialised to a JSON array, each entry carrying name, description, a parameters JSON Schema (type: object with properties and a required list), plus title, outputSchema and annotations when set. For LLM runtimes that want the tool catalogue as a string. Gated-off tools are excluded, matching tools/list over HTTP.
The contents at uri, or null when no visible provider handles it, it can't be read, or the host's confirmer (configured for the provider's required tools) declined.