Connect the Answer Cloud MCP to your AI assistant, then ask it to update your website in ordinary language. MCP (Model Context Protocol) is the connection that lets AI work with Answer Cloud on your behalf.
Connect and make your first request#
- Sign in to Answer Cloud and open MCP setup.
- Choose your AI tool and follow its installation or connection instructions. Complete browser sign-in and approve the team you want to work with.
- Start a chat with the connection enabled. Give AI your website address and describe the update you want.
For example:
Find my existing Answer Cloud site at [website address]. Update the contact page with these details and show me a preview before publishing.
AI should confirm the team and site, prepare your update, and help you review it. Ask it to publish when you are ready. If you were invited by someone else, follow Start developing after accepting an invite.
Describe the task and publication scope#
Say what should change and whether you want a draft, a preview, or a published update. You can also ask AI to review traffic, improve a CMS article, or check your chat settings. See common requests for examples.
For layout or code changes, AI may ask for the existing source project or repository access. The site owner can share it if needed. AI handles building and packaging in a capable coding environment. The hosted update workflow has the developer details.
Technical connection details#
The normal authenticated service is https://app.answer.cloud/mcp, using Streamable HTTP and OAuth. A connected assistant can inspect sites, work with deployments and configured content collections, configure supported site features, and read available reporting.
Keep three kinds of access distinct#
| Access | Purpose | Scope |
|---|---|---|
| Public first launch | Build and publish a newly reserved starter site through /new |
Temporary access to that reservation only |
| Authenticated MCP | Manage sites your signed-in account may access | Authorized organizations and the explicitly selected site |
| Public website services | Visitor chat, forms, and discovery | Published visitor-facing functionality; not account administration |
The first launch does not require plugin installation or browser sign-in. Returning management uses normal account access after account setup. A public site URL does not establish that an assistant has authenticated permission to manage it.
Start with a read-only inspection#
After connecting a supported client, ask:
List the Answer Cloud organizations I can access. If there are several, let me choose. Then list that organization's sites and show the slug, kind, public URLs, and release configuration. Do not make changes.
The assistant should call list_organizations when the organization has not been established. If more than one is available, select one and keep its organization_id explicit on later calls. Site operations then use the intended site_slug; deployment operations use the returned deployment ID.
Tool access and feature access are separate. A tool can be available in the client while the selected site's plan does not permit the operation. Treat the returned error and site configuration as the authority.
See common workflows, authentication, and the MCP reference for the next step.