Skip to content
Documentation
Browse docs
overview

Official plugins overview

Install the official Answer Cloud plugin from its repository marketplace, understand what it bundles, and choose a verified Claude Code or Codex connection path.

Reviewed

The official Answer Cloud plugin bundles launch guidance, the website-building skill, and an MCP connection for authenticated site management. It is a convenience for recurring work; the public first-launch prompt can work without installing it.

Choose your client#

Client Setup guide Distribution
Claude Code Connect Claude Code Repository marketplace answer-cloud/answer.cloud-Plugins
Codex Connect Codex The same repository's Codex marketplace catalog
Another MCP-capable assistant Other clients Manual Streamable HTTP MCP connection where supported

The repository packages declare version 1.1.0 at this review. Read the installed package and repository release information when updating rather than assuming a published listing has the same version.

Repository marketplace availability is separate from a vendor's public plugin directory. Installing from Answer Cloud's repository does not establish that the plugin is listed or approved in another directory.

What installation and connection each do#

Installation gives the assistant instructions and the server configuration. Browser OAuth grants the account connection. On first authenticated use, sign in and select the intended Answer Cloud organization in your browser.

The MCP server URL is:

https://app.answer.cloud/mcp

Use OAuth with no custom Authorization header. A static bearer header can interfere with OAuth discovery and should not be added to a normal personal connection.

Once connected, make a read-only request to list organizations and sites. Confirm the public address and slug of the site you intend to manage before publishing changes.

Updating or reconnecting#

If a newly installed skill or server is unavailable, start a new session when your client requires it. Preserve the website brief, source project, and existing site identity across that restart.

If the connection is present but account tools fail, reconnect through the client's MCP settings and complete browser sign-in. Reinstalling the plugin does not recover site ownership or substitute for account setup.

A plugin also cannot add missing terminal, build, or upload capabilities to every client. An assistant may be able to read analytics and edit CMS entries yet be unable to compile and publish an Astro website. Use a capable coding environment for those tasks and hand it the existing source project.

The plugin repository contains the current distribution instructions. For concrete requests after setup, see common agent workflows.

Have a question about this guide?

Send feedback

Type to find a guide.