# Shyne full agent handoff

Shyne is a collaborative design workspace for canvases, presentations, visual documents, social posts, video, and publishing. People and AI agents edit the same live projects, and everything an agent makes stays editable for the humans in the project.

Canonical human docs: https://shyne.ai/docs
MCP guide (connect an agent): https://shyne.ai/docs/mcp
Canonical agent guide: https://shyne.ai/docs/agent.md
MCP: https://mcp.shyne.ai/mcp
Transport: Streamable HTTP
Authentication: OAuth
Live REST schema: https://api.shyne.ai/openapi.json
Security and local MCP trust model: https://shyne.ai/security

The live authoring contract comes from the `get_guide` tool after connecting, and MCP `tools/list` is the live source of tool names and parameter schemas. This handoff deliberately does not duplicate either.

## Required orientation

1. Call `projects.list` and match an exact project name or id. Ask if more than one is plausible.
2. Call `get_guide` once at the start of the working session and follow it over anything cached.
3. Pass `projectId` explicitly on every project-scoped call.
4. Call `get_basic_info` before making or placing work.

## Working rules

- Work one frame at a time.
- Call `read_html` immediately before editing an existing frame, and keep everything the request did not ask you to change.
- Use `add_frame` to create and `write_html` to edit. Heed any warnings the tools return.
- Call `screenshot_frame` for every changed frame and inspect the returned image before reporting completion.
- Use `projects.open` when the finished work should appear on the user's screen.

## Media and video

Prefer `search_stock` when real-world media fits. Keep attribution and verify licenses. Use `generate_media` when stock cannot satisfy the request, and `list_files` for project assets.

A video is one frame that owns the whole timeline. Use `get_timeline` to inspect, the clip tools to edit, and `screenshot_frame` with a `time` value to check exact moments. Hosted `export_video` starts a render: it returns a completed download URL when ready or a processing job id that you pass back to `export_video` to poll.

## Hosted MCP tool lanes

The tool surface is served live: call `tools/list` on the MCP endpoint — the registry is the single source and this document no longer mirrors it.

## Boundaries

An authenticated agent works only in projects owned by that Shyne user. Whole-project deletion, credential management, provider tokens, and normal final publishing are not exposed. Scheduling tools create owner-confirmable proposals. `get_presence` returns an empty peer list on hosted MCP.

## Bootstrap prompt

You have access to Shyne through the MCP server named "shyne".

Before changing anything, call `projects.list`, select an exact project, call `get_guide` (its rules are authoritative), and call `get_basic_info`. Pass `projectId` explicitly on every project-scoped call.

Work one frame at a time. For an existing frame, call `read_html` immediately before editing and keep everything the request did not ask you to change. Use `add_frame` to create and `write_html` to edit. Prefer stock for real-world media and generated media when stock cannot satisfy the request.

Before finishing, call `screenshot_frame` for every changed frame, correct visible problems, and use `projects.open` when the user should see the result.

Task: [DESCRIBE THE OUTCOME, AUDIENCE, FORMAT, CONTENT, AND BRAND CONSTRAINTS].