Start with a connection and a project you can identify
MCP connects a compatible assistant to Webyaam's editing tools. The remote endpoint is https://app.webyaam.com/mcp. Authorize the workspace you intend to use, then begin with a read-only request that identifies the correct site. A connection error or a missing project should be resolved before the assistant creates a replacement website.
The built-in site agent and an external MCP client are different operating choices. External client availability, models and usage charges belong to that client; the built-in agent uses Webyaam's AI credit system. The detailed Claude walkthrough separates connection, authorization, implementation and review without promising that one prompt produces a finished business website.
Give the assistant decisions it can respect
Describe the audience, primary action, pages, content and constraints. Ask it to inspect existing pages, installed sections, variables and collections before proposing changes. Define what it may change immediately and what needs review, particularly deletion, public URLs, shared components and publication.
A useful first task is a proposed page outline or a single content change. Avoid combining a redesign, a content migration and a hosting change into an unexplained operation. Smaller tasks give you a clearer result to accept, reject or correct.
Make reuse and content structure explicit
A request to change a card might mean local copy, an all-instance design adjustment or a new independent preset. The reuse guide explains those scopes. Ask the assistant to use the existing visual system before introducing custom code, and have it identify whether a selected element belongs to a linked component.
For repeating content, approve a collection schema before generating many entries. Use a small set of clearly illustrative drafts and inspect their values afterward. A field is data; if the design should display or filter by it, verify the actual component behavior rather than assume that adding a key implemented the feature.
Treat tool responses as evidence to review
Ask the assistant to list what changed and what it checked. A saved source revision, a successful build and a screenshot answer different questions. Verify long content, mobile reading order, navigation, forms and the actual released URLs where appropriate. Do not accept invented metrics or a claim that a check passed when it could not be performed.
When another editor has saved a newer revision, reload and reconsider the pending change. Authentication failures, required-field messages, source validation errors and occupied development sessions need different fixes. Repeating an outdated write is not a recovery strategy.
Prepare for the next person and the next session
Record the assistant's authorized workspace, the role it follows and the review rules the team expects. Do not use a personal connection as an undocumented dependency of a client website. Revoke a connection when it is no longer needed, and keep credentials out of prompts, CMS entries and exported source.
The reading path combines the connection tutorial with design reuse, structured content, responsive review and handoff. Those are the skills that turn an AI-assisted draft into a maintainable site. The final publication should remain an intentional release decision based on the checks actually completed.