Release / / with v0.9.21, v0.9.22, v0.10.0, v0.10.1, v0.10.2, v0.10.3, v0.10.4, v0.10.5, v0.10.6, v0.10.8, v0.10.9, v0.10.10
Apify MCP Server v0.10.11
Set spending and result limits when running Actors.
Before you upgrade to v0.10.11
3 to fixRead usage fields from `_meta["com.apify/ActorRun"].usageTotalUsd` and `.usageUsd` instead of flat `_meta` fields.
Upgrade to Node.js 22 or newer; this release restores the Node.js 22 package minimum.
UI-capable clients automatically get MCP Apps mode. Data tools have separate `-widget` variants for rendering.
Agentic payment mode rejects standby Actors; use OAuth or an Apify token for standby execution.
What changed in v0.10.11
`callOptions` accepts build and spending limits; Actor calls return metadata for a separate dataset fetch. Run, storage, and abort tools are automatically included with Actor tools.
Available in @apify/actors-mcp-server 0.10.11; tool access depends on session configuration and authentication.
New things you can do
Abort a running Actor, optionally allowing graceful shutdown.
Fixed and improved
`callOptions` accepts `build`, `maxItems`, and `maxTotalChargeUsd`.
`get-actor-run` accepts `waitSec` and reports progress while waiting.
`tasks/cancel` aborts the in-flight handler, and long-running tools emit task status notifications.
Search results include compact input schemas.
Payment metadata advertises multiple `accepts` schemes and returns payment requirements as structured content.
Seeded by @iluxav with Codex, from the release's public sources. Each change links to its evidence.