# Managing Multiple Production Sites with answer.cloud MCP

> Canonical source: [Managing Multiple Production Sites with answer.cloud MCP](https://www.answer.cloud/docs/managing-multiple-production-sites-hosted/)

Select an organization through OAuth, then use explicit organization IDs and site slugs to manage several production sites.

An answer.cloud MCP connection can provide access to multiple organizations. Select the organization first, then select the site inside it. Site slugs identify deployment targets; display names are for people.

## Connect and choose the organization

Use the interactive browser OAuth sign-in flow provided by the official plugin or your MCP client. Run `list_organizations` before site operations when the conversation has not established an organization.

If the connection returns several organizations, ask the user which one to use. Include the selected `organization_id` on subsequent calls when the connection requires it. Do not infer a production organization from the currently open dashboard or a similar name.

## Manage several sites in one organization

1. Run `list_sites` with the selected organization.
2. Review each site’s slug, live URL, current deploy, and release workflow.
3. Use the exact `site_slug` for site-specific tools.
4. State the intended organization and site when requesting a deployment.

For example: “Deploy this reviewed project to the Acme organization’s site with slug acme-docs.” An agent should inspect the target and its current live URL before starting that authorized deployment.

## Keep build modes distinct

A hosted site ships its complete static website and any CMS templates. An existing-site companion ships the companion’s CMS package and leaves the original website in place. Use the [hosted guide](https://www.answer.cloud/docs/mcp-hosted-sites-hosted/) or [existing-site guide](https://www.answer.cloud/docs/mcp-existing-sites-hosted/) for the correct package.

## Verify a release

Build and review the artifact, upload through `start_deploy`, call `finalize_deploy` only after upload succeeds, and poll `get_deploy` until it is live or fails. Read warnings and verify the intended public URL. If independent staging is enabled, uploads go to staging and an explicit promotion is required for the custom-domain production site.

## Credentials and access boundaries

Interactive OAuth and headless hosting keys are different authentication paths. An organization-scoped hosting key can manage the organization’s sites; creating another such key does not itself create a site-level access boundary. Use the organization and access controls appropriate to each customer or team, and never publish credentials in site files.

For current tool arguments, see [Site & Deploy Tools](https://www.answer.cloud/docs/mcp-site-and-deploy-tools-hosted/), [GitHub Tools](https://www.answer.cloud/docs/mcp-github-tools-hosted/), and [CMS Tools](https://www.answer.cloud/docs/mcp-cms-tools-hosted/).