Skip to content
DocMyRepos
EspañolStart now

The answers you need from your repositories.

Your docs stay in each repository as Markdown. DocMyRepos gathers them from your GitHub organization into one portal with one search. Host it yourself or let us do it.

Start nowTry the demo(opens in a new tab)View on GitHub(opens in a new tab)

Hosted DocMyRepos opens soon.

Leave your email and we will tell you when hosted DocMyRepos opens. We use the address only for that, and send nothing else. See the Privacy Policy.

Search results for the word deployment across several repositories, with highlighted snippets and repository, type and tag filters
Search across every repository of one organization, with highlighted snippets and filters.

Find

Search, Ctrl/Cmd+K and Ask the docs across every repository.

You should not have to know which repository holds the answer. There are three ways to look, and they all use the same index.

  • Search every repository at once

    One full-text search covers every synced repository. Results are ranked by title, headings, description and body, with highlighted snippets and filters for repository, type and tag.

    Search results for the word deployment across several repositories, with highlighted snippets and repository, type and tag filters
    Search across every synced repository, with highlighted snippets and filters.

  • Ctrl/Cmd+K from anywhere

    Press Ctrl/Cmd+K on any page to open the command palette and jump straight to a document.

    The quick search palette open over a page, listing documents that match the typed words
    Ctrl/Cmd+K opens the palette from any page.

  • Ask in plain language

    An optional assistant answers from the synced documents and cites the sections it used. It stays off until an administrator sets it up, with a model the operator provides: Anthropic, or any OpenAI-compatible endpoint, including a local one.

    Ask the docs: a plain-language answer with numbered references to the document sections it used
    Ask the docs answers from your documents and links the sections it used.

  • Browse a repository's space

    Each repository you choose gets its own space, with its main README, its code owners from CODEOWNERS and a tree of its docs folder.

    A repository space with its README, the documentation tree and the code owners panel
    Each repository gets its README, its code owners and a tree of its docs folder.

How it works

A read-only GitHub App, four steps, nothing to migrate.

Your docs stay as Markdown in each repository. There is nothing to migrate, no separate editor and no build step.

  1. Install the DocMyRepos GitHub App on your organization.

    • Read-only permissions, never a personal access token.

  2. Choose which repositories are visible.

    • Only the repositories you pick are synced and shown.

  3. DocMyRepos syncs their docs folders and keeps them up to date.

    • Documents are treated as untrusted: output is sanitized and .mdx never runs.
    • A failed sync keeps the previous content.

  4. Everyone reads and searches in one portal.

    • GitHub is never called while people browse.
    • The portal sits behind a login with admin and user roles.

Read

Markdown, diagrams, API reference, OKF, comments and your own branding.

Reading

  • Markdown that reads well

    GitHub-flavored Markdown with Shiki syntax highlighting and Mermaid diagrams. Documents are treated as untrusted: output is sanitized and .mdx is never executed.

    A document page with its metadata, a Mermaid diagram, an outline and the documentation tree
    Markdown with highlighted code and Mermaid diagrams, beside an outline. Open the full screenshot

  • API reference from your specs

    OpenAPI 3.0/3.1 and Swagger 2.0 files found in a repository are shown on a read-only reference page.

    The API reference page of a repository, rendered from its OpenAPI file with servers, tags and operations
    OpenAPI and Swagger files become a read-only API reference.

  • Open Knowledge Format, when you use it

    Repositories that use OKF can be filtered by concept type, tags and status, with each document's metadata on its page. Repositories without it show no OKF interface.

    An Open Knowledge Format repository filtered by concept type in the documentation panel
    Repositories that use OKF can be filtered by type, tag and status.

  • Comments on every document

    Signed-in users discuss a document on its page, and admins can answer as the organization and moderate. Comments are stored in the portal, never written to GitHub.

Running it

  • Fresh without a pipeline

    GitHub webhooks sync a repository again whenever its default branch changes. A scheduled full sync catches missed deliveries, syncs are incremental, and a failed sync keeps the previous content.

  • Your name, colours and logo

    Admins set the organization name, page title, colours and logo from the portal.

  • Light, dark or system

    Readers choose light, dark or the system setting. Code blocks and diagrams follow it, and the page does not flash on load.

The portal home page: a search field above the list of synced repositories
The portal home. Admins can set their own organization name, colours and logo.

Agents

Your agents read the same docs, and can only read them.

AI agents such as Claude Code and Cursor search and read the portal's documentation through a read-only MCP endpoint, with the same visibility as the website.

Read-only by design

  • Agents can search and read; they can never change documents or repositories.
  • Each user creates a personal token, shown once.
  • Tokens expire after 30 days, 90 days or a year, and can be revoked at any time.
  • A token sees exactly what its user sees, nothing more.
Claude Code
claude mcp add --transport http docmyrepos \
  https://docs.example.com/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"
Cursor and other agents: ~/.cursor/mcp.json
{
  "mcpServers": {
    "docmyrepos": {
      "url": "https://docs.example.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Replace the address with your portal’s and YOUR_TOKEN with your own token. Never commit a token to a repository.

Instead of…

Docusaurus, Confluence, Notion and others, side by side.

Including where DocMyRepos does not lead.

Where the docs live

DocMyRepos
In each repo, as Markdown
Docusaurus
In the site’s repo
Confluence
In Confluence pages
Notion
In Notion pages
Backstage TechDocs
In each repo
GitBook
In GitBook, Git sync optional

Moving docs already in repos

DocMyRepos
None
Docusaurus
Into one site repo
Confluence
Yes, imported
Notion
Yes, imported
Backstage TechDocs
Per-repo config
GitBook
Git Sync per space

One search across many repos

DocMyRepos
Yes
Docusaurus
No: one site
Confluence
Not applicable
Notion
Not applicable
Backstage TechDocs
Yes, via Backstage Search
GitBook
Within one site

Build pipeline to publish

DocMyRepos
None
Docusaurus
Yes
Confluence
No
Notion
No
Backstage TechDocs
Yes, CI recommended
GitBook
No

Editing in the browser

DocMyRepos
No: authors edit in the repo
Docusaurus
Via Git provider
Confluence
Yes
Notion
Yes
Backstage TechDocs
Via Git provider
GitBook
Yes

Open source, self-hostable

DocMyRepos
Yes, MIT
Docusaurus
Yes, MIT
Confluence
No, proprietary
Notion
No, cloud service
Backstage TechDocs
Yes, Apache-2.0
GitBook
Renderer only, GPL-3.0

AI agents over MCP

DocMyRepos
Yes, read-only
Docusaurus
Not built in
Confluence
Yes, official server
Notion
Yes, official server
Backstage TechDocs
Metadata only
GitBook
Yes, official server
Sources and notes

Last reviewed October 27, 2026, from each tool’s public documentation. Product names are trademarks of their owners; DocMyRepos is not affiliated with them.

Start

Free to start hosted, or self-hosted under MIT.

The same product either way.

Questions

Does DocMyRepos change our repositories?

No. It reads them through a GitHub App installed with read-only permissions and never writes to them. Comments people leave in the portal stay in the portal, not in GitHub.

Which docs are synced?

The docs folder of each repository you choose (it looks for docs, doc or documentation), plus the repository’s README and its code owners from CODEOWNERS. OpenAPI and Swagger files found in the repository become its API reference.

Who can see the docs?

Only people signed in to your portal. Administrators create the users and choose which repositories are visible. Search, Ask the docs and agents show exactly what that user can see.

Do we need Open Knowledge Format?

No. Plain Markdown works as it is. Repositories that already use OKF also get filters by type, tag and status and a metadata card on each document; the others show no OKF interface at all.

What can AI agents do with our docs?

They can search and read them through a read-only MCP endpoint. Each user creates a personal token, sees it once and can revoke it. A token sees what its user sees and cannot change anything.

How do hosted and self-hosted differ?

It is the same product. Self-hosted, you run it on your own servers with Docker and Postgres under the MIT license, with no limits. Hosted, we run it for you and it opens soon.

The docs of every repository, one search away.

Start nowTry the demo(opens in a new tab)View on GitHub(opens in a new tab)

Hosted DocMyRepos opens soon.

Leave your email and we will tell you when hosted DocMyRepos opens. We use the address only for that, and send nothing else. See the Privacy Policy.

Made byDash AI

DocMyRepos is one of the small open-source tools Dash AI builds for people who build with AI.

Meet other products(opens in a new tab)Request AI consultation(opens in a new tab)