Update ui settings
update_ui_settingsWRITE$0.02 / callShow or hide one interface element of the docs site — the header search button, sidebar search, the copy-page menu and its entries, previous/next links, breadcrumbs, scroll-to-top, page feedback, the 'was this helpful' bar, edit-on-GitHub, the Ask AI buttons (header, outline, on selection), copy-as-markdown, and where the language and theme switchers sit. Also the HOME-PAGE LANDING switches (home_hide_sidebar, home_hide_outline, home_wide_content), which strip the sidebar, the outline and the column width off the site's FRONT PAGE ONLY so it can read as a landing page — use them for 'make the home page a landing page', 'full-width main page', «сделай главную посадочной», «убери сайдбары на главной». And the SITE FOOTER (whether it exists, its layout, its copyright text, its call-to-action button, and whether it shows the social icons and a theme picker) — 'add a footer', 'put a copyright line at the bottom', «добавь футер». Pass only the toggles the user mentioned; the rest are untouched. Use it for 'hide the search button', 'remove breadcrumbs', «убери кнопку поиска». NOT header links or folder tabs — and NOT the footer's LINK COLUMNS, which are update_navigation's footer_columns. NOT colours or fonts (update_branding). All toggles available on FREE plan. BEFORE CHANGING THIS, call docsbook_expert with what you are trying to achieve: it names the reading that should decide the value, so the setting is a conclusion rather than a guess. One call, changes nothing.
Numeric workspace id — OR the project as the user names it: 'owner/repo', the repo name alone, the site's display name, its docs URL or custom domain. Text is resolved server-side; an ambiguous name returns the candidates instead of guessing, so pass what the user said rather than calling list_workspaces first.
The search button in the site header.
The search box at the top of the left sidebar.
—
Show "Copy Skills.md URL" in the Copy page dropdown
Show "View as Markdown" in the Copy page dropdown
Show "Open in ChatGPT" in the Copy page dropdown
Show "Open in Claude" in the Copy page dropdown
Show "Open in Cursor" in the Copy page dropdown
Show "Open in Windsurf" in the Copy page dropdown
Show "Connect to VSCode" in the Copy page dropdown
—
—
HOME PAGE ONLY: hide the left navigation rail on the site's front page (its top-level README/index), on desktop — the mobile drawer stays. Every other page keeps its sidebar.
HOME PAGE ONLY: hide the right-hand "On this page" outline on the site's front page.
HOME PAGE ONLY: let the front page's content run the full window width instead of the fixed reading column.
—
—
—
—
Show AI chat button (AI must be enabled separately)
—
—
Show floating Ask AI button when user selects text in the docs (AI must be enabled separately)
Floating "Ask Docs" pill pinned to the page's bottom-right corner
—
—
—
—
Base URL for Edit on GitHub links
Show the site footer — the band under every docs page. Off by default. It renders only once it has content: a link column (update_navigation footer_columns), footer_text, a CTA, the logo or the social icons.
How the footer's blocks sit: 'columns' (brand block left, link columns right), 'centered' (everything stacked down the middle) or 'minimal' (one row — text left, links and socials right). Placement only; it never turns a block off. One of: columns, centered, minimal.
Free text under the footer's logo — copyright line, legal entity, postal address. Plain text: line breaks are kept, markup is not. Max 600 chars. Pass an empty string to clear it.
Show the site logo in the footer's brand block.
Show the social icons in the footer. WHICH accounts is not a footer setting — it is the workspace's social_links (update_navigation); this only decides whether the footer draws them.
Show a three-way light / dark / system picker in the footer.
Label for an optional call-to-action button in the footer's brand block (e.g. 'Get started'). Without a label no button is drawn. Pass an empty string to remove it.
Where the footer's call-to-action button goes. Leave unset to reuse the workspace's own cta_url (see get_workspace) rather than repeating it.
Call it#
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "update_ui_settings",
"arguments": {
"workspace_id": "<workspace_id>",
"footer_layout": "columns"
}
}
}curl -X POST 'https://docsbook.io/api/mcp/server' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"update_ui_settings","arguments":{"workspace_id":"<workspace_id>","footer_layout":"columns"}}}'Try it over REST#
The same tool is callable as a plain HTTP request, no MCP client required. It runs on the same server, at the same price.
Your workspace is resolved from the API key, so workspace_id is decided server-side here and anything you send for it is ignored.
/api/v1/tools/update_ui_settingsYour API key, sent as Authorization: Bearer dbk_YOUR_API_KEY.Sent as the Authorization header. Your key is used only by your browser for this request — it is never sent to Docsbook or stored.
The arguments above, as one JSON object.
curl -X POST 'https://docsbook.io/api/v1/tools/update_ui_settings' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"args":{"workspace_id":"<workspace_id>","footer_layout":"columns"}}'