MCP tools

Site settings

Read and change a project's site settings from a connected AI agent through the Doxa MCP server

Overview

Two MCP tools let a connected agent read and change the site settings of a project: the same settings you edit in the dashboard under the site settings pages. Use them when you want an agent to update the theme, navigation, SEO, features, or other site configuration for you.

ToolWhat it doesScope needed
get_site_settingsReads the current site settings of a project.docs:read
update_site_settingsChanges site settings on a branch.site:write

Both tools are part of the 34 tools that the Doxa MCP server exposes. Scopes are granted on the consent page when you connect an agent. See MCP Scopes and Approval Requests for how scopes limit what a tool can do.

Before you start

  • Connect your agent to the Doxa MCP server. Follow Connect an AI Agent with MCP.

  • Grant the agent docs:read to read settings, and site:write to change them. An agent without site:write cannot update settings.

  • Make sure the project you pick on the consent page is the one you want the agent to change.

Reading site settings

Ask your agent to read the settings for a project, for example:

text
Get the site settings for my "acme-docs" project.

The agent calls get_site_settings and returns the current configuration, so you can check values before you ask for a change.

Changing site settings

update_site_settings changes settings on a branch, not directly on the published site. This matches the rest of the MCP workflow: writes to main are rejected through MCP, so the change goes through a named branch first.

A typical sequence is:

  1. Ask the agent to create a branch with create_branch, or use an existing branch.

  2. Ask the agent to update the settings on that branch with update_site_settings.

  3. Ask the agent to build a preview with build_preview and check the result.

  4. Publish the branch with publish_branch. Publishing requires the publish scope.

text
On a new branch called "theme-refresh", change the site accent color
and turn on search. Build a preview when you are done.

Until the branch is published, the live site keeps its current settings. For the branch workflow, see Branches, Previews, Publishing, and Restore.

Settings you can review in the dashboard

The same settings are available in the dashboard. Use these pages to understand what each field controls:

  • Appearance: theme, colors, logo, and visual options.

  • Navigation: sections, groups, and page order in the sidebar and header.

  • SEO and sharing: search metadata and social sharing.

  • Features: toggles for search and API reference pages.

  • Advanced JSON: the full site configuration as JSON.

  • Custom Domains: domain setup. Domain changes use the domains:write scope and the domain tools.

Troubleshooting

SymptomLikely causeWhat to do
The agent cannot read or change settings.The agent lacks docs:read or site:write.Review the grant under Settings, Connected agents, and reconnect with the scopes you need.
The agent reports the project is not found.The project was not selected on the consent page, or your role on a team project is viewer.Reconnect and select the project, or ask a team owner or admin for edit access.
Changes do not appear on the live site.The branch has not been published.Build a preview, then publish the branch.

Next steps