Files
openidea/wit/mcp.wit
T
l0ng-ai 74e66a5dae feat(plugins): environment and debugger for plugin run configurations (API 1.9) (#3476)
Plugin run configurations could not set environment variables, and Debug
only worked when a source file in the arguments let the IDE infer a
debugger, so a plugin could run `func start` for an Azure Functions app but
not debug the worker it starts.

API 1.9 adds the optional `launch-configurations` export, preferred over
`run-configurations` when a component has both. Each configuration can add
environment variables (only names the IDE's environment doesn't already
have, like `process` commands) and name a debugger: launch the program
under a language's debugger, or run it and attach to the first process of
an Attach to Process kind that the run starts. Only the run's own
descendants are candidates; the IDE waits up to a minute while the run
lasts and otherwise leaves it running without the debugger. Remote projects
resolve the process on the server.

The SDK gets `LaunchConfigurations` / `launch_configurations`, the README
and docs describe the export, and the bundled components and fixtures are
rebuilt for 1.9.
2026-11-15 11:01:12 +08:00

17 lines
725 B
Plaintext

package openidea:plugin@1.9.0;
/// Discovery of the IDE's built-in MCP server; never exposes its URL or token.
interface mcp {
/// Stdio bridge argv for the invoking project; none without a window/project or while off.
stdio-command: func() -> option<list<string>>;
}
/// Optional tools declared by contributes.mcpTools, under the plugin's grants and command budget.
interface mcp-provider {
use types.{error};
use invocation.{invocation};
/// Calls the declared local tool name with JSON arguments and the project's window context.
/// Returns text; tools may encode structured data as JSON text.
call: func(tool: string, arguments: string, ctx: borrow<invocation>) -> result<string, error>;
}