Codex can manage Answer Cloud through an authenticated MCP connection. A coding session also needs source files, build tools, and upload access to publish a complete website. For the first starter site, the public launch guide handles its separate temporary access workflow.
Option 1: install the repository plugin#
Add Answer Cloud's repository marketplace:
codex plugin marketplace add answer-cloud/answer.cloud-Plugins
In a client that exposes repository marketplaces in its plugin browser, select that marketplace and install Answer Cloud. Start a new session if necessary to load the plugin and its skills.
Repository marketplace support varies by Codex surface and version. If the installation control is unavailable, use the manual MCP option below. A repository installation is separate from inclusion in a public directory. OpenAI's plugin packaging documentation describes the marketplace command and supported distribution surfaces.
Option 2: add the MCP server directly#
In a Codex CLI environment, run:
codex mcp add answercloud --url https://app.answer.cloud/mcp
codex mcp login answercloud
codex mcp list
Complete sign-in and organization approval in your browser. Keep OAuth discovery enabled; do not add a static Authorization header for this personal connection.
The equivalent server configuration is:
[mcp_servers.answercloud]
url = "https://app.answer.cloud/mcp"
In an app with MCP connection settings, configure the same URL with OAuth rather than running CLI commands in an unrelated environment. OpenAI's MCP documentation covers current CLI configuration and login behavior.
Verify the actual account connection#
Ask Codex:
List my Answer Cloud organizations. Let me choose if several are available, then list that organization's sites. Confirm the existing site slug and public URL before making changes.
Codex should discover the organization, pass its ID explicitly, and confirm the intended site. A connected icon or browser sign-in message alone does not establish access to that site.
If a launched site is missing, complete its ownership handoff and check the account used for OAuth. If authentication expires, reconnect the existing server through the client or run the login command again.
Resume source work#
Open the preserved Astro project and give Codex a concrete edit. State whether you want a local preview or a publication, and name the environment when relevant. Keep temporary launch credentials out of permanent MCP settings and source archives. See authentication for the access model and common workflows for copyable task examples.