The Answer Cloud MCP service exposes site, content, deployment, integration, and reporting tools over Streamable HTTP. Use the current schemas returned by tools/list; a client's available tools depend on the granted scopes and credential type.
Connection and result contract#
The normal service endpoint is https://app.answer.cloud/mcp. Official clients handle browser OAuth. For an authorized headless client, send JSON-RPC requests with Authorization: Bearer <private token>, Content-Type: application/json, and an appropriate Accept header. The current protocol version is 2025-11-25; initialization also supports 2025-06-18 and 2025-03-26.
Initialize, send notifications/initialized, then request tools/list. Send individual JSON requests; JSON-RPC batch arrays are not supported.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "list_organizations", "arguments": {} }
}
Read both transport and application results. A tool result can return HTTP success with result.isError: true; its structuredContent then includes error and message. Successful structured content is the authoritative object described by each reference below.
Establish organization scope#
| Tool | Arguments | Successful structured content |
|---|---|---|
list_organizations |
None | organizations available to the credential and selection instructions. |
list_sites |
organization_id integer when selection is required |
sites[] with slug, kind, URLs, status, page allowance, release workflow, and widget configuration. |
Call list_organizations when the workspace has not been established. If several are available, choose the intended one. Every other normal tool accepts optional organization_id; it is required when the connection needs explicit selection. An unapproved organization returns organization_not_allowed.
Tool families#
| Family | Tools | Contract |
|---|---|---|
| First site and deployments | prepare_site, create_site, start_deploy, finalize_deploy, deploy_files, get_deploy, list_deploys, rollback |
Site and deployments |
| GitHub | github_get_connection, github_link_repo, github_get_workflow, github_trigger_deploy, github_unlink_repo |
GitHub tools |
| CMS | list_cms_collections, upsert_cms_collection, list_cms_entries, get_cms_entry, upsert_cms_entry, preview_cms_entry, publish_cms_entry, archive_cms_entry, delete_cms_entry, republish_cms |
CMS tools |
| Site configuration | configure_release_workflow, promote_deploy, set_custom_domain, check_domain, configure_widget |
Configuration tools |
| Reporting and retrieval | get_analytics, get_chats, get_aeo_report, search_site |
Reporting tools |
Permissions and limits#
Read tools require hosting:read; mutations require hosting:write. offline_access supports refresh access in an OAuth connection. Read operations include private previews and domain-status checks; a check_domain refresh can queue a new check despite belonging to the read scope.
Temporary guest access exposes only the reserved site's launch subset. It cannot create more sites, administer CMS entries, manage domains/GitHub/releases, or change billing. Discover that credential's actual schema rather than assuming it exposes the full directory.
Apply plan gates and limits independently of scope. A write grant does not enable Pro features. For normal changes, confirm the intended site and publication destination before mutations. See errors for recovery.