Skip to content
Edda
Sign up
Menu

Docs agents can navigate

Agents now read more docs than people do, so every merge publishes HTML for people and indexed Markdown for agents from the same commit.

Connect GitHub to publishRead the docsMoving from Mintlify?

Live example: MDX in, HTML and Markdown out

HTML out: acme.blode.md/quickstart

Quickstart

Install the CLI, then publish your first page.

Run edda login once per machine.

Publish

  1. Run edda new docs
  2. Run edda push docs

Read the CLI guide.

Markdown out: acme.blode.md/quickstart.md

> ## Documentation Index
> [HTML page](https://acme.blode.md/quickstart)
> [Documentation index](https://acme.blode.md/llms.txt)
> Use the index to discover all available pages before exploring further.

# Quickstart

Install the CLI, then publish your first page.

> [!NOTE]
> Run `edda login` once per machine.

## Publish

1. Run `edda new docs`
2. Run `edda push docs`

Read the [CLI guide](/docs/cli/overview).

Turn on JavaScript to edit the example.

Your majority reader is an agent

agent requests vs 131M human page loads, across Mintlify-hosted docs in August 2026
257M
of agent traffic came through .md pages, llms.txt or agent skills
83%
failed requests per task when Markdown links to an index, vs 2.23 for HTML
0.11

Source: Mintlify, 2026 State of Knowledge Report.

Edda ships all three routes on every deploy, and every Markdown page links to the index before its first heading.

Agents draft. People merge.

Most teams now have agents drafting docs changes, and most still want a person to approve them. In Edda that approval is the pull request you already review, and merging it is the publish. No second editor, no sync job, no docs that lag the release.

The merge is the deploy

  1. Indexed Markdown on every page

    Each page has a .md twin that opens with a link to llms.txt, so an agent that lands on one page can find the rest instead of guessing URLs.

    acme.blode.md/quickstart.md
    > ## Documentation Index
> [HTML page](https://acme.blode.md/quickstart)
> [Documentation index](https://acme.blode.md/llms.txt)
> Use the index to discover all available pages before exploring further.

# Quickstart

  2. Tools for browser agents

    Every page registers five WebMCP tools (search_docs, read_page, get_site_overview, read_skill, navigate_page), so an agent driving a browser tab reads your docs through typed calls.

    document.modelContext.getTools()
    search_docs
read_page
get_site_overview
read_skill
navigate_page

  3. Review in the pull request

    Whether a person or an agent wrote it, a docs change is a diff your team approves beside the code it describes.

    docs/quickstart.mdx
    ## PublishRemoved: Run `edda push`.Added: Run `edda push docs`.

  4. Publish on merge

    The GitHub App deploys on every push to main, so the docs change ships the day the product does.

    With the GitHub App
    git switch main
git merge update-quickstart
git push
# deployed to acme.blode.md

Hosted or self-hosted

No visual editor, plugin marketplace, SOC 2, SSO or SLA. Support is the founder.

$0 hosted

No second editor

Unlimited projects, pages and seats. Custom domains, search, MDX and API references included.

Connect GitHub to publish

MIT

Your Postgres

Self-host the same CLI and renderer on your Postgres. No licence keys or telemetry.

View the source on GitHub

FAQ

Last updated

What is Edda?

Edda is a docs platform for teams that keep MDX in git. Every merge publishes an HTML site for people and, for agents, llms.txt, a Markdown copy of every page and WebMCP tools. Hosting is $0 and the source is MIT.

How is Edda different from Mintlify?

Edda is the git path without the web editor or marketplace: the same MDX files, a smaller docs.json and one command to publish. Hosted Edda is $0, and you can self-host the MIT source. Moving over takes a docs.json rewrite, not a content rewrite.

What do agents get from an Edda site?

llms.txt and llms-full.txt, a .md twin of every page (also served for Accept: text/markdown), discovery headers on every HTML page, a generated agent skill, and five WebMCP tools for browser agents. All of it is rebuilt from the commit you merged.

Can an AI agent write my docs?

An agent can draft the change as a pull request like any other code change. Edda publishes what you merge, so a person stays the approver. Edda doesn't include a writing agent of its own.

Can I see how much agent traffic my docs get?

Not in Edda yet. Agents fetch server-side and run no JavaScript, so PostHog counts people only. To count agents today, put a proxy you can log in front of the docs and count .md, llms.txt and AI user-agent requests.

What does Edda cost?

Hosted Edda is $0 with unlimited projects, pages and seats, including custom domains, search, MDX and API references. You do not get a visual editor, a plugin marketplace, SOC 2, SSO or an SLA, and support is the founder. The CLI and renderer are MIT if you self-host.

Your next reader is an agent.

Give it docs it can navigate, from the commit you merged.

Connect GitHub to publish
CLI

npm i -g edda-docs
edda login
edda new docs
edda push docs