app invoke to test an exact SDK, REST, or Unified App version with your execution token. Call MCP apps through an MCP client; the CLI manages their deployment, inspection, and tokens.
Call something
app invoke never picks a version for you, which is the property that makes it useful in CI.
--params. Any JSON option also accepts @file, or - for stdin, which keeps large payloads and anything sensitive out of your shell history.
If the selected bucket is still missing a required static credential, app invoke stops before contacting the provider and prints the exact fused-cli connect command for that service, bucket, authentication type, and scheme. Store the value securely, then repeat the same invocation.
In a pipeline
Keep the token out of the environment where you can, and gate on the structured output rather than the exit code alone.--json prints the endpoint, physical results, status, and timing, so a job can assert on what actually ran. A stable --idempotency-key keeps a retried job from counting as a second logical request.
Flags
The token comes from
FUSED_APP_TOKEN unless you redirect it. Management credentials and provider credentials are never substituted for it.
Limits worth knowing
This is a debug surface, not a production transport. It accepts one buffered JSON provider document up to 1 MiB. Generated SDKs keep their broader gRPC transports, so a payload that fails here may be perfectly fine from your application. It produces one logical Fused execution and does not retry locally or follow redirects itself — Fused owns retries, pagination, and continuation.Read the receipts
app activity shows what every execution did, whichever route made it.