# KEEL Studio

> KEEL helps creators prepare artwork, interactive projects, reusable assets and releases. Agents can discover the tools and documentation publicly. Private workspace access requires a connection approved by the creator.

## Start here

- [Machine-readable connection details](https://studio.onkeel.io/.well-known/keel.json): SDK, MCP, skill, contracts and readiness links.
- [Connect an agent](https://studio.onkeel.io/studio#agents): the creator signs in with their selected wallet and grants the agent permissions. Use the resulting Studio agent key as a bearer token. Never ask for wallet keys or a seed phrase.
- [Remote Studio MCP](https://studio.onkeel.io/api/mcp): Streamable HTTP using JSON POST requests. A GET returns 405; this does not mean the server is absent. Anonymous requests cannot access private drafts.
- [MCP guide](https://studio.onkeel.io/docs/mcp): connection and workflow documentation.

After the creator grants access, initialize the MCP connection, list its tools, and call `keel_whoami` to inspect permissions. Call `keel_project_modules` to find published dependencies, including three.js with its core module, and infer file roles. The server's initialization instructions and current tool schemas are authoritative.

The remote Studio MCP prepares drafts and returns review links. The creator approves publishing, payments and contract changes in their own wallet. Finding this page does not grant private workspace access or authorize an agent to sign.

## SDK and local tools

- [KEEL SDK source and setup](https://github.com/keel-web3/keel-sdk): the `@keel/sdk` toolkit and local MCP server.
- [SDK guide](https://studio.onkeel.io/docs/sdk): APIs and examples.
- [Local MCP setup](https://github.com/keel-web3/keel-sdk/blob/master/packages/mcp/README.md): workspace-based planning and verification tools.
- [Agent skill](https://github.com/keel-web3/keel-sdk/blob/master/skills/fray-keel-agent/SKILL.md): the publication workflow and its referenced instructions.
- [Contracts](https://studio.onkeel.io/docs/contracts): contract families, authority and publication documentation.
- [Network preparation readiness](https://studio.onkeel.io/api/studio/projects/readiness): read-only storage, registered viewer, media module and native-text capability checks.

## Working with a creator

Module configuration and NFT actions are distinct. Use `keel_configurable_modules` for `keel-module-inputs@1` settings supplied to reusable code through `KEEL_INPUTS`. Use `keel_artwork_controls_read` and `keel_artwork_controls_prepare` for `keel-collector-actions@1` bindings to ABI contract functions. The latter only validates and prepares unsigned calldata. The creator attaches the mapping under a project's Artwork controls and each collector approves its execution through their selected wagmi wallet.

- [Artwork controls designer](https://studio.onkeel.io/studio/actions): label inputs, choose owner/public visibility, preview the collector form, and download `keel.actions.json`.
- [Portable actions schema](https://studio.onkeel.io/api/collector-actions/schema): exact argument bindings and manifest rules.
- [Module settings and contract controls](https://studio.onkeel.io/docs/artwork-controls): sources, mutable creator mappings, inline token metadata, EVM support, and undeployed example contracts.

Ask about the work they want to make. Inventory supplied files and preserve originals. Search the selected-chain catalogue before creating or uploading a reusable dependency. Let files determine their initial roles; a model or image should not become a code library just because of its filename. Use explicit role and format overrides when the creator asks.

Payload storage defaults to Compact: native bytes once, compatible beneficial lossless compression, and exact reuse of unchanged published objects. Raw preserves the supplied bytes and intentional formatting. Shell selection is separate: use the registered KEEL verification shell by default; explicit `viewer=none` preserves creator-owned self-contained HTML without a canonical protection claim.

Check the selected network before preparing files. Preview the actual files with their selected modules. Keep draft preparation, local previews, chain receipts and exact public read-back distinct. Read the SDK README and agent skill before publication work; use their current tools and schemas rather than inventing contract actions.