Skip to main content

1. Prepare your workspace

Sign in to Studio. Use an existing Storyworld or create one in Studio. A Storyworld holds the creative work your account is permitted to access.

2. Add the remote server

In your agent’s MCP settings, choose remote HTTP and enter:
Name it SIA Studio. If you already have a SIA entry, update that entry rather than adding a duplicate. Existing internal names such as sia-studio-production can stay unchanged. Follow the guide for your client. Keep optional headers empty unless the client’s current official instructions require otherwise. Never copy an OAuth token from another client or browser.

3. Sign in and review permissions

Complete the native SIA sign-in flow. Initial discovery requests account and saved-work read access. Creating drafts, editing assets and generating media require additional scopes. Only approve capabilities you want this connection to use. Some clients request renewable access. Stay connected for up to 30 days is optional and unchecked by default. It permits renewal within that limit; it does not authorize a new creative task or spending.

4. Check the connected account

Ask:
Which SIA account am I connected to, and which Storyworlds can I access?
The client can use account_get and storyworld_list. This first check does not create media or spend generation credits. A Connected badge or completed browser callback alone is not proof of a successful tool call.

5. Find something saved

Find the characters I saved for this story and show their reference images.
Choose the correct Storyworld when needed. Reuse the returned Studio links if your host cannot display the media. Continue with creative workflows when the saved-work check succeeds.

If access changes

Refresh the client’s tool list or start a new conversation after a server update. Use native reconnect/sign-in when the client needs additional permissions. Follow authentication and recovery before retrying an interrupted write.