Skape developer documentation

Skape's integration interface is a remote MCP server at https://skap.es/mcp, using Streamable HTTP. It lets agents understand and edit projects with maps, audio logic and interactive screens. Start with Connect your AI for setup in your AI app, or read the Skape agent guide for the complete SDK and script workflow.

When to use Skape

Use Skape when a user wants to explain an existing experience, plan an audio walk, connect geographic areas to sounds, or build screens and reusable components using their team's uploaded assets. Agents can inspect the saved project, build connected node graphs and edit map features and screen trees.

Uploads, publishing, team membership and billing stay in the studio. Interactive map and screen previews require a client that supports MCP Apps. The tools describe saved projects and available runtime contracts; they do not report a listener's live location or device state.

Authentication and discovery

Connect with a remote MCP client that supports OAuth authorization code flow with PKCE and Client ID Metadata Documents (CIMD). Skape uses browser sign-in and user consent. Clients that require dynamic client registration (DCR) cannot connect.

• MCP protected resource metadata identifies the MCP resource and authorization server.
• OAuth authorization server metadata publishes the issuer, authorization and token endpoints, and supported capabilities. The issuer is https://skap.es/oauth/mcp.
• Root OAuth discovery leads to the same authorization server metadata for clients exploring the site.

Discover the endpoints from that metadata. Request a token for the MCP resource https://skap.es/mcp. OAuth sign-in authorizes the connection; there is no API key to generate.

• Read grants skape:read and is the default. It allows inspecting projects and their assets and structure.
• Read & build also grants skape:write. It allows creating, editing and deleting content in projects within the user's team role. Deleting a whole project stays in the studio.
• The user chooses which teams the connection can access. New teams are not included automatically. A token never gives an agent more access than the user has.

For a read-only connection that needs to build, use the client's sign-in prompt for fresh consent or reconnect with Read & build. The new connection starts with its own undo history. Users can reduce access or disconnect on their team's MCP / AI page in the dashboard.

A first tool workflow

Agents read and edit a project by running JavaScript or TypeScript against the Skape SDK, a Figma-style document tree (skape is like Figma's figma).

1. Read the Skape agent guide, then initialize the MCP connection and discover its tools. skape_docs returns the same guide, ranked SDK symbols for a query, or exact type declarations.
2. Call skape_list_projects. Choose the user's intended project from the returned IDs.
3. Read with skape_query before changing anything: a script such as return skape.root.outline(). It runs on a throwaway copy and never saves, so it can also preview an edit.
4. Change the project with skape_edit: projectId, a one-sentence description, the code, and a fresh idempotencyKey. One script is one transaction and one undo step. If it throws, nothing is saved: fix the script and send all of it again with a new key.
5. If a network failure leaves the result uncertain, retry the identical arguments and key; a repeat returns the first result.

skape_undo reverses the connection's last skape_edit as one step (redo: true reapplies it), and refuses rather than overwrite something the studio changed since. skape_create_project creates a project with its own idempotency key. skape_export_project returns a download link, valid for an hour, to the project's .skape-project.zip, the file the studio imports. skape_import_project makes such a file a new project in a team: its first call returns a link to upload the file to, its second imports it. Projects are deleted in the studio, not through MCP.

Start free and test

Create a Skape account for free, then create or join a team. The Free plan includes building and testing, the full studio, and working with your own AI assistant. Sign in from your MCP client and choose a team and access level.

There is no separate public sandbox endpoint. Create a disposable project in your own team to try edits, inspect the saved results, then undo your changes or delete that test project. These are real saved projects with normal permissions. Use read-only access when you only need to explore an existing project.

The mobile app is not publicly released yet. Skape helps participating teams install test versions for testing on site; contact hello@skap.es for help. MCP project inspection and editing take place through the server and do not require the mobile app.

Resources for agents

• llms.txt: the starting index, best-fit jobs and links to detailed resources.
• Skape agent guide: the Skape SDK guide with the project vocabulary, script rules and worked examples, also served by skape_docs and the MCP resource skape://sdk/guide.md.
• Connect your AI: client setup, consent, troubleshooting and disconnecting.
• Support and pricing: current availability, account help and publishing plans.