Ship the feature.Your agent writes the docs.

Tell the agent you already use what changed. It writes your docs and help center pages through Dokly, and nothing goes live until you approve the diff.

Start your free trialOne command to connect · Nothing publishes without you
Works with
  • Claude Code
  • Cursor
  • claude.ai
  • + any MCP client
claude — ~/dokly
Our quickstart doesn't mention agents yet. Add a card for connecting one under "What's next".
dokly - get_any_page (MCP) get-started/quickstart
dokly - update_page (MCP) get-started/quickstart
Proposed · waiting for review · live page unchanged
get-started/quickstart.mdx | +4 −0
</Card>
+ <Card title="Connect your agent" icon="bot"
+ href="/get-started/connect-your-agent">
+ Let your AI agent write and update these docs.
+ </Card>
</CardGroup>
Approve or reject → https://www.dokly.co/dashboard/…/pages/…
Dashboard · Quickstart

An agent proposed changes to this live page. +4 −0

Readers see the current version until you approve.

Docs and help centers already live on Dokly

and 35+ more sites published on Dokly

What you get

Your agent knowswhat changed.

  1. Docs that ship with the release

    Ask in the same session you built the feature in. Your agent has just read the code, so the page is written from what actually changed — not from someone's memory two weeks later.

  2. A help center that keeps up with support

    Paste a support thread or this week's repeat questions. Your agent drafts the articles; you publish the ones worth keeping.

  3. No new editor. No docs day.

    You stay in Claude Code, Cursor or claude.ai. Dokly hosts the site, keeps it searchable, and publishes an llms.txt so other AI tools can read it too.

See it work

One request, start to finish.

Recorded in one take: a request in Claude Code, a quick review, and a help center live on dokly.co.

  1. Ask. “Write a help center for this app” in Claude Code.
  2. Review. The agent shows the diff and asks before it goes live.
  3. Live. A searchable help center on pocketbill.dokly.co.

How it works

Connected in one command.

No SDK, no config file, no repo to set up. Your agent signs in to Dokly once and works on every site you own.

  1. Add Dokly to your agent

    One line in your terminal for Claude Code. In claude.ai, paste the same URL as a custom connector.

    zsh — ~/dokly
    claude mcp add --transport http dokly https://mcp.dokly.co/mcp
    # then sign in to Dokly in the browser that opens

  2. Sign in and set the rules

    Your browser opens on Dokly. You see exactly what the agent may do before you allow it — publishing stays off unless you tick it.

    www.dokly.co/oauth/consent

    Connect Claude Code to Dokly

    Signed in as you@company.com

    Claude Code will be able to:

    • Read all your sites, including unpublished drafts
    • Create and edit drafts
    • Propose edits to live pages — they wait for your review
    • Publish to your live sites without asking you

  3. Ask for what you need

    Plain sentences. Your agent reads the site first, writes in your existing components, and reports back.

    claude — ~/dokly
    We renamed "Projects" to "Workspaces". Fix every page.
    Proposed · waiting for review · live page unchanged
    Turn these five support threads into help articles.
    Draft saved · not published
    Document the new /webhooks endpoint.
    Draft saved · not published

You stay in control

Review it likea pull request.

Agents write drafts. An edit to a live page becomes a proposal with a diff, and readers keep seeing the current page until you approve it — in the dashboard or from your terminal.

  • Drafts by default

    New pages stay unpublished until you publish them.

  • Proposals, not overwrites

    A live page changes only when you approve the diff.

  • Publishing is opt-in, per agent

    Allow it when you connect; take it back any time in Settings → Agent access.

  • Broken pages never save

    MDX that would break a page is refused before anything is written.

www.dokly.co/dashboard/…/pages/…
Dokly docs Quickstart Live
An agent proposed changes to this live page. +4 −0 Readers see the current version until you approve.
<Card title="Import an OpenAPI spec" icon="terminal" href="/api-reference/openapi-import">
Drop in your OpenAPI YAML and get a full API reference auto-generated.
</Card>
<Card title="Connect your agent" icon="bot"
href="/get-started/connect-your-agent">
Let your AI agent write and update these docs.
</Card>
</CardGroup>
claude — ~/dokly
Show me what's waiting, then approve the quickstart change.
dokly - list_pending_changes (MCP)
dokly - approve_change (MCP) get-started/quickstart
Approved · live page updated at https://docs.dokly.co/get-started/quickstart

Docs and help center

Docs for your developers.A help center for everyone else.

docs.dokly.co/components/steps
A page of Dokly's own documentation: sidebar navigation and a numbered Steps guide with a code block

Product docs and API reference

Sidebar navigation, code blocks, an interactive API playground, and llms.txt for AI readers. Dokly's own docs run on it.

Write the migration guide for v2.

visionfly-help-docs.dokly.co
VisionFly's help center on Dokly: a search box above article categories

A help center your customers can search

A search-first home, articles grouped by topic, and “Was this helpful?” on every page so you know what to fix next.

Turn this week's top support questions into articles.

Before you connect

Straight answers.

Who does the writing, Dokly or my agent?
Your agent. Dokly doesn't call a model when your agent writes. It checks, stores, versions and publishes what your agent sends.
Which agents work?
Claude Code and claude.ai connect with a browser sign-in. Cursor and other MCP clients connect with an API key from Settings → Agent access.
Can it publish without asking me?
Only if you tick “Allow publishing directly” for that agent. Without it, the agent can draft and propose; you publish.
Can I still edit pages myself?
Yes. Every page opens in Dokly's editor, and your agent's proposals appear there as a diff you approve or reject.

Ready when your next release is

Whatever ships next,the docs already know.

Connect your agent, ask for one page, approve it. That's the whole setup.

Start your free trialOne command to connect · Nothing publishes without you