Use Claude Code when you want an assistant that can work in your source project, build a static site, and manage Answer Cloud through MCP. For a brand-new starter website, you can begin with the launch prompt before installing the plugin.
Install the official plugin#
In a current Claude Code session, run:
/plugin install answercloud --marketplace answer-cloud/answer.cloud-Plugins
The single-command form requires Claude Code v2.1.275 or later according to the Answer Cloud repository instructions. For an older client that supports repository marketplaces, use:
/plugin marketplace add answer-cloud/answer.cloud-Plugins
/plugin install answercloud@answercloud
The package includes the Answer Cloud skills and an HTTP MCP server named answercloud. Start a new session if your client needs one to load the installation.
Complete browser sign-in#
On the first authenticated tool request, let Claude Code open the browser authorization flow. Sign in to Answer Cloud and select the organization you intend to manage. Never paste your password, email verification code, or account claim link into the conversation.
If sign-in does not start, open Claude Code's MCP connection controls, locate answercloud, and reconnect it. Keep the configured URL as https://app.answer.cloud/mcp and remove any manually added static authorization header from a personal OAuth connection.
If you are continuing a guest launch, finish account setup first. The guest build token cannot be used as a permanent account connection.
Manual connection without the plugin#
If you only need MCP tools, Claude Code supports a manual HTTP server connection:
claude mcp add --transport http answercloud https://app.answer.cloud/mcp
Complete the client's browser OAuth flow for that server. Prefer one working connection over several duplicate server entries with unclear access. Claude Code's MCP documentation describes its current remote-server and authentication controls.
Verify before changing anything#
Ask:
Use the Answer Cloud connection to list organizations. Let me choose if there is more than one. Then list sites for that organization and confirm the public URL and site slug. Do not deploy or publish content.
A successful browser callback alone is not the final check. The agent should make an authenticated tool call and find the intended site. If it sees another organization or cannot find the site, reconnect with the correct account rather than creating a replacement.
Once verified, open the editable Astro project and follow the hosted update workflow or existing website companion workflow.