Stackie asset tools and MCP

​

Goal

​

Prerequisites

• A PAT carrying only the asset scopes the client needs
• An MCP client that supports stateless Streamable HTTP

​

Workflow

​

Tool and scope matrix

• search_assets, get_asset, and get_asset_operation: assets:read.
• organize_assets: assets:write.
• transform_asset, moderate_asset, and transcribe_asset: assets:process.
• generate_asset: assets:generate; generated images start private and remain gated through storage, replication, scan, moderation, provenance, and spend reconciliation.
• The MCP endpoint accepts any PAT with a concrete Assets scope, but every individual tool call rechecks its own required scope. assets:* is not treated as a wildcard; the platform-wide * scope is.

​

MCP transport and browser-origin rules

• Transport is stateless Streamable HTTP using the official Go MCP SDK. Requests inherit HTTP cancellation and platform rate limits.
• A non-browser client may omit Origin. If supplied, Origin must exactly match the configured StackShift frontend origin or the request origin; userinfo, paths, and unsupported schemes are rejected.
• Inputs, outputs, status, tool name, transport, account principal, and timing are audited after redaction. Prompt bodies and credentials are not exposed by the automation overview.

{
  "mcpServers": {
    "stackshift-assets": {
      "type": "http",
      "url": "https://api.stackshift.cloud/api/v1/assets/mcp",
      "headers": { "Authorization": "Bearer ${STACKSHIFT_ASSETS_PAT}" }
    }
  }
}

​

Governed Stackie node boundary

• Defaults are at most eight tool calls, one specialist handoff, a two-minute deadline, and no secret access.
• The node cannot add tools beyond its declared allowlist or change execution identity, approval policy, or budgets from prompt content.
• Production, costly, and external nested actions use the workflow version grant only when its fixed constraints cover the resolved call; otherwise the node pauses for a new approval.
• Output must validate against the configured JSON schema before downstream conditions or actions can consume it.

​

Expected result

​

Related guides