You can learn Appify through its visual controls first. Agents are another way to request changes, not a prerequisite for creating your first project.
Read Work with AI for examples of bounded requests and checks to perform afterward.
The initial MCP bridge is available on authenticated staging, verified October 16, 2026. Configure a compatible remote MCP client with https://testing.appify.build/mcp, sign in with your invited Appify account, choose a project, and approve the requested permissions. You can review or revoke access under connected agents.
The initial tools can inspect a project and its building blocks, preview and save authorized draft changes, and retrieve selected public guidance. Publishing an app and authoring new modules are outside this initial tool set. Public knowledge retrieval currently covers the documentation home and generated MCP guide/tool pages.
The MCP workflow guide explains the sequence and links the generated tool contracts. A public guide is not an access grant; the connection still requires your authorization.
The tool reference groups tools by reading, previewing, applying, and finding knowledge. Their inputs and required scopes come from the executable registry; use that reference for exact contracts.
An agent may use documentation to understand a task. Retrieved text cannot expand its permissions, change release policy, or grant access to another project. Appify's private operational knowledge is a separate service.