greentic-mcp-exec

Greentic's executor for Wasm tools that implement the wasix:mcp interface. The crate handles lookup, verification, and execution of MCP-compatible components while exposing host capabilities such as secrets, telemetry, and HTTP fetch. Supports MCP router-world components (wasix:mcp/router@25.06.18) as well as legacy exec shims.

Features

• Local and remote (HTTP) tool stores with SHA-256 integrity checks.
• Signature policy stubs ready for digest/signature enforcement.
• Wasmtime component runtime with the runner-host-v1 imports from greentic-interfaces wired in.
• Describe helpers that prefer the greentic:component/component@1.0.0 world and fall back to legacy actions.

Usage

use greentic_types::{EnvId, TenantCtx, TenantId};
use greentic_mcp_exec::{ExecConfig, ExecRequest, RuntimePolicy, ToolStore, VerifyPolicy};
use serde_json::json;

let tenant = TenantCtx {
    env: EnvId("dev".into()),
    tenant: TenantId("acme".into()),
    tenant_id: TenantId("acme".into()),
    team: None,
    team_id: None,
    user: None,
    user_id: None,
    trace_id: None,
    correlation_id: None,
    deadline: None,
    attempt: 0,
    idempotency_key: None,
    impersonation: None,
};

let cfg = ExecConfig {
    store: ToolStore::HttpSingleFile {
        name: "weather_api".into(),
        url: "https://example.invalid/weather_api.wasm".into(),
        cache_dir: std::env::temp_dir(),
    },
    security: VerifyPolicy::default(),
    runtime: RuntimePolicy::default(),
    http_enabled: true,
    secrets_store: None,
};

let output = greentic_mcp_exec::exec(
    ExecRequest {
        component: "weather_api".into(),
        action: "forecast_weather".into(),
        args: json!({"location": "AMS"}),
        tenant: Some(tenant),
    },
    &cfg,
)?;

Development

cargo fmt
cargo clippy --all-targets -- -D warnings
cargo test

Set RUN_ONLINE_TESTS=1 to exercise the live weather integration test that retrieves the published Wasm component over HTTPS.

MCP node schemas live with the component crate itself. When a tool exports describe-json, greentic-mcp-exec forwards that blob upstream so flows can validate against the component-owned schema/defaults instead of mirroring JSON locally.