Dokly runs an MCP server at https://mcp.dokly.co/mcp. Connect your AI agent to it and the agent can write and update your docs, post changelog entries, make your docs site match your website, and check every page for problems. New pages land as drafts and edits to live pages wait for your approval, so nothing reaches readers until you say so.
What you can ask for#
- "Here's our website: https://acme.com. Make our Dokly docs look like it."
- "Write a getting-started guide for the new CLI and save it as a draft."
- "Read the changes in this PR and update the authentication page to match."
- "Add a changelog entry for version 2.4 from the release notes."
- "Check the docs site for broken links and fix them."
- "Show me the changes waiting for review, and approve the one for the pricing page."
What each plan includes#
| Free | Team and higher | |
|---|---|---|
| Read pages, including drafts | Yes | Yes |
| Write drafts and propose edits to live pages | Yes | Yes |
| Post changelog entries (as drafts) | Yes | Yes |
| Publish directly, without your review | No | Yes |
| Rearrange the sidebar, switch the layout | No | Yes |
| Change the theme and branding | No | Yes |
Connect your agent#
The quickest way is to sign in with your Dokly account in the browser the first time you connect. No API key needed.
Run this in your terminal, then start Claude Code and run /mcp to sign in:
claude mcp add --transport http dokly https://mcp.dokly.co/mcpWhen you sign in, the agent can read and write drafts. Tick Allow publishing directly on the sign-in screen to also let it publish and change site settings. You can change this later under Agent access → Connected apps in your project settings.
Use an API key instead#
For CI jobs, shared machines, or when you want exact control over what an agent may do, create a key under Settings → Agent access in your project. Pick which sites it reaches (all of them, or one) and what it may do:
| Permission | Lets the agent |
|---|---|
| Read | Read every page, including unpublished drafts. |
| Write drafts | Create and edit drafts. Edits to live pages wait for your review. |
| Publish | Put drafts on the live site without asking you first. |
| Site settings | Rearrange pages, switch the layout, and change the theme and branding. These go live straight away. |
The key is shown once, together with the ready-made command:
claude mcp add --transport http dokly https://mcp.dokly.co/mcp --header "Authorization: Bearer YOUR_KEY"What your agent can do#
| Tool | What it does | Needs |
|---|---|---|
list_sites | Lists the docs sites the connection reaches | Read |
search_docs, list_pages, get_page | Search and read published pages | Read |
list_drafts, get_any_page | Read drafts and the raw MDX of any page | Read |
get_site | The site's settings, branding and full sidebar | Read |
list_components | Every MDX component a page can use, with props and examples | Read |
check_site | Finds broken pages and links (see below) | Read |
create_page | Creates a page, as a draft unless it may publish | Write drafts |
update_page | Edits a draft, or proposes an edit to a live page | Write drafts |
add_changelog_entry | Adds an entry to your changelog | Write drafts |
list_pending_changes | Lists edits waiting for your review | Read |
approve_change / reject_change | Puts a pending edit live, or discards it | Publish / Write drafts |
create_site | Creates a new docs site in your account | Write drafts |
move_page, set_layout | Rearranges the sidebar, switches docs / help center layout | Site settings |
set_theme, set_branding | Changes the theme, colours, fonts and logo | Site settings |
Every write returns a summary of what changed (+12 −3 per page, with a short diff) and a link to review it in the dashboard. Before saving, Dokly checks the MDX and refuses anything that would break the page, telling the agent the line to fix.
Make your docs match your website#
Give your agent your website's address and ask it to match the look:
Here's our website: https://acme.com. Make our Dokly docs look like it, then write a getting-started page.
The agent reads your website
It looks at your site's CSS: background, text and border colours in light and dark mode, the fonts used for headings, body text and code, how rounded the corners are, and your logo and favicon. Dokly doesn't run any AI for this: your agent does the reading.
It picks the closest theme
set_theme sets the overall design. A dark website gets a dark theme.
It applies your brand
set_branding lays your accent colour, page colours, fonts, corner radius, logo and favicon over the theme. If your website has a dark mode, ask the agent to match its dark colours too: colours it doesn't set keep the theme's own. The change is live straight away, and the agent's reply lists the old values, so undoing it is one more request.
It writes the pages
New pages, changelog entries and updates now render in your brand.
Fonts come from Google Fonts
Dokly loads brand fonts from Google Fonts and checks each one before saving. If your website uses a commercial or self-hosted typeface, the agent picks the closest Google Fonts family.
Branding needs the Site settings permission, which comes with the Team plan and higher. Custom CSS and removing the "Powered by Dokly" badge stay in your project settings.
Reviewing changes#
When the agent edits a live page, the edit is saved as a proposal and the published page doesn't change. You can review it two ways:
- In the dashboard. Open the page in the editor to see the proposed change and approve or reject it.
- In the conversation. Ask the agent to show pending changes. It shows you the diff, and approves only after you say so.
Checking your site#
Ask your agent to run check_site after it writes or reorganises pages. It checks every page, drafts included, and reports:
- MDX that won't render, with the line number
- Links to pages that don't exist
- Live pages that link to drafts (readers would get a 404)
- Empty pages and very short ones
- Pages that share a title
The agent can then fix what it finds and run the check again.
Disconnecting#
Open Agent access → Connected apps in your project settings and choose Disconnect next to the agent. Its access ends straight away, and it has to sign in again to reach your docs. To stop an API key, revoke it in the same section.
Privacy#
Dokly only receives the requests your agent sends to these tools, such as a search term or a page's content. It never sees your conversation. Section 9 of the privacy policy has the details.
Common issues#
The agent says it can't publish or change site settings
Publishing and site settings need the Team plan or higher, and the agent needs permission: tick Allow publishing directly when signing in, or use an API key with Publish or Site settings. You don't need to reconnect after upgrading.
My agent doesn't see a new tool
Agents load the list of tools when they connect. Reconnect Dokly (in Claude Code, run /mcp and reconnect) to pick up new tools.
I signed in with the wrong account
Disconnect the agent under Connected apps, sign out of dokly.co, then connect again and sign in with the right account.
My edit didn't show up on the live site
Edits to live pages wait for review unless the agent may publish directly. Approve the change in the editor or ask the agent to approve it. Approved changes can take up to a minute to appear.
The agent says my font isn't on Google Fonts
Font names are case-sensitive ("IBM Plex Sans", not "ibm plex sans"). If the font really isn't on Google Fonts, ask the agent for the closest family that is.