Docs/Reference

REFERENCE / GUIDE 10

MCP tool reference

The fifteen available Studio tools.

The hosted endpoint at https://www.wayweaver.app/api/mcp registers 15 tools. Start with studio_get_context and studio_get_schema; the live schema is authoritative for argument fields and node configuration. Every campaign-specific call is restricted to the connection's workspace and campaign grant.

Discovery and reads

studio_get_context

Returns API and document schema versions, workspace ID, granted permissions and campaigns, and authoring limits. No campaign permission is needed beyond an active connection.

studio_get_schema

Returns JSON Schemas and examples for authoring operations and resources. Optionally pass nodeType to get one mission node's configuration schema.

studio_list_campaigns

Lists campaigns visible to this connection, newest activity first. Requires draft:read; campaigns outside a selected-campaign grant are omitted.

studio_get_campaign

Returns campaign metadata, mission summaries, route, resource registry IDs, and the draft editVersion. Requires draft:read for that campaign.

studio_get_mission

Returns one mission's nodes, edges, layout, and relevant resources. Requires draft:read. Expected answers are withheld unless the connection also has answers:read; redactedPaths identifies withheld fields.

studio_get_resource

Reads one location, content, ending, or media reference by ID. Requires draft:read; answer-bearing data remains subject to answer permission.

studio_preview_node

Returns the player-safe projection of a single node. Requires draft:read. It does not create or advance a player run and does not reveal future or server-only information.

studio_validate_campaign

Returns findings for the saved campaign draft, including unreachable nodes, missing transitions, and broken references. Requires draft:read.

studio_list_changes

Returns draft version history in newest-first order, with source (studio or MCP), summary, and affected IDs. Supports pagination. Requires draft:read.

Writes

studio_create_campaign

Creates a schema-valid starter campaign with a draft and initial IDs. Requires campaign:create and an entire-workspace grant. Send a fresh requestId for this logical write.

studio_derive_draft

Creates a mutable draft from an immutable published revision. It refuses to replace an existing draft. Requires draft:write and a requestId.

studio_apply_changes

Applies 1–100 typed authoring operations to one campaign. Requires draft:write, expectedEditVersion, and requestId. mode is preview or commit; validation is draft or ready. A commit is atomic and may remove entities, so review changesets before applying them. See Authoring operations.

studio_create_playtest

Freezes an exact validated draft version into an author-only playtest and returns its admin URL. Requires playtest:create, expectedEditVersion, and requestId. It does not create a production invite.

Media upload

studio_prepare_media_upload

Creates a short-lived signed PUT URL for one JPEG, PNG, or WebP file. Requires draft:write. Upload the raw bytes using the returned headers. Preparing a URL does not register a campaign asset.

studio_complete_media_upload

Verifies the uploaded file and registers its assetId in the campaign media registry. Requires draft:write, the expected draft version, and a request ID. Use the resulting ID in supported image content blocks.

Tool boundaries

The MCP surface authors drafts and creates playtests. It does not publish revisions, issue production invites, operate player runs, execute arbitrary SQL or HTTP, or inspect uploaded screenshot contents. Those responsibilities use the relevant Studio workflows or remain outside the current product.