Your docs editor doesn't change.
You don't migrate. You don't pay for a second editor. You don't fight WYSIWYG on top of git. Whatever you write in Cursor today, Miradorly shows tomorrow.
Docs portal · comments · role-aware MCP
Share your repo docs with clients — without giving them your repo.
Miradorly renders your private GitHub or GitLab markdown as a clean portal with role-based access and comments. Your team keeps writing in Cursor. Anyone you invite sees a polished site they can read and comment on — and your AI agents query the same docs respecting every permission.
No credit card · we onboard new teams within 24 hours
$ claude mcp add miradorly <url> # docs stay where you write them
Your repo. Our viewer. Your client's comments.
Sound familiar?
You've moved your docs to git. Now what?
Most agencies and dev teams hit at least two of these.
“I'm sending .md files in Slack and non-coding people can't even open them, let alone comment.”
You set up Cursor and Claude Code for the team — and now your PM can't find the spec you wrote yesterday because it's buried in a private repo.
Your designer keeps DMing you for the latest brand guidelines. Your HR keeps re-explaining the PTO policy. Your sales lead can't find the technical brief.
You looked at GitBook, then at Mintlify. GitBook wants $173/mo for a 10-person team. Mintlify wants you to ditch your editor.
Markdown needs comments, permissions, and history — without forcing the whole team into GitHub. Said better than we ever could ↗
The fix
A read-only viewer + comments + MCP — over your existing repo.
Miradorly connects to your GitHub or GitLab repository and renders your markdown as a fast, navigable portal. Your team keeps writing in Cursor or Claude Code — every commit shows up automatically. Anyone you invite — clients, designers, HR, sales, leadership — gets a clean URL, signs in with email, comments on any section, and can never see what they shouldn't.
Your client doesn't need GitHub.
They get an email invite, sign in, and see only their project — comments threaded by section. You see every comment in one inbox and mark them resolved. No more “I emailed it to John for review” loops.
Your AI agent reads docs without leaking them.
Connect Claude Code, Cursor, Claude Desktop, or any MCP client. The agent searches in real time — but only what their account can see. .docignore keeps internal files out of the index entirely.
The whole system on one screen
One repo. One permission model. Two ways to read.
Push markdown to git like you always do. Miradorly turns it into two synchronized surfaces — a portal for people and an MCP endpoint for AI agents — both governed by the same roles and the same .docignore.
fig. 1 — how Miradorly sits between your repo and your readers
The wedge no one else has
Role-aware MCP on private docs.
GitBook and Mintlify ship MCP for published docs. Notion's MCP shuts guests out. Miradorly's MCP serves your private repo docs — and every query is filtered by the caller's role, so a client's agent physically can't read your internal notes.
- Your team's agents see everything; a client's agent sees only their project.
.docignorefiles are never indexed — not hidden, absent.- Read-only by design: agents can read your docs, never overwrite them.
- One command to connect:
claude mcp add miradorly <url>
fig. 2 — what the client's agent can (and can't) see
Four steps · about 30 seconds to first render
How it works
- 1
Connect your repo
Install the Miradorly GitHub or GitLab app, pick the markdown folders. Takes 30 seconds.
- 2
Set up access
Create projects, invite people as viewer or commenter, optionally publish individual pages or whole projects publicly.
- 3
Keep doing what you do
Write docs in Cursor / Claude Code / any editor. Push to the repo. Miradorly renders the changes live.
- 4
Plug in your AI agent (optional)
claude mcp add miradorly <url>— now your agent answers from your docs with full role-aware access.
Live, right now
Browse a real Miradorly portal.
We run a fully public showcase you can open immediately. Viewing is open; commenting needs a free account — to keep clients safe.
See the live portal →Your docs, your git
Built so you never have to hand over your repo.
Read-only by design
Miradorly reads your repo to render the portal — it never writes, pushes, or modifies anything in your git. Your repo stays the single source of truth.
.docignore means absent, not hidden
Files you exclude are never indexed. They can't be served to the portal, found in search, or read by any MCP client — there is nothing to leak.
Role checks on every read
Every portal page view and every MCP query is filtered by the caller's role and project membership, server-side. A client can't see another client's project — or your internal notes.
No lock-in, ever
Your repo was always the source of truth — Miradorly only serves a rendered view of it. Disconnect the integration and the portal turns off; there's nothing to migrate out.
MCP connections are authorised with OAuth 2.1 + PKCE and inherit the signed-in user's permissions. More detail in Answers — MCP & docs.
No fake logos. No fake numbers.
Built by an agency, for agencies.
We've been writing project documentation in git and sharing it with clients for the past year — and we got tired of the same gaps every other agency hits. So we built the tooling we wanted, and now we're opening it up. Try it free for 30 days. If it works for you, $29/mo. If it doesn't, walk away — no card needed to start.
- We use Miradorly daily on our own client projects — every commit, every comment, every MCP query.
- OAuth 2.1 + PKCE for MCP, role-based access per project,
.docignorefor sensitive files. - Self-hosted option on the roadmap.
The short version
Miradorly vs the tools you've already priced.
| Miradorly | GitBook | Mintlify | DIY: MkDocs + Pages | |
|---|---|---|---|---|
| Keep your editor (Cursor, any IDE) | Yes — reads your repo | Their editor | Their platform | Yes |
| MCP on private docs | Yes — role-aware | Published docs only | Public docs only | No |
| Client comments without GitHub | Yes — email sign-in | Editor accounts | — | giscus needs GitHub login |
| Private, per-client access | Roles per project | Per-seat plans | Public-first | Public by default — auth is on you |
| Entry price | $29/mo flat | $65/site + $12/user | $79 + $15/user | Free + your engineering hours |
Full breakdowns: Miradorly vs GitBook · Miradorly vs Mintlify · Miradorly vs MkDocs · all comparisons →
Flat monthly. No usage gotchas.
Pricing that respects a small team.
Small teams
$29 / month
Teams sharing docs mostly internally, with a handful of client projects
- 10 projects
- Unlimited team seats
- 50 external collaborator seats
- Threaded comments included
- Role-based access — viewer or commenter per project
.docignoreto keep internal files out- Role-aware MCP server included
Agency
$79 / month
Studios running many client-facing projects at once
- Unlimited projects
- Unlimited team seats
- Unlimited external collaborators
- Threaded comments included
- Role-based access — viewer or commenter per project
.docignoreto keep internal files out- Role-aware MCP included · priority support
Start free for 30 days on any plan. No credit card. Cancel any time before the trial ends and you pay nothing.
- No card required to start the trial
- Cancel inside the app any time during the 30 days
- Honest pricing — $29 or $79 flat, no per-seat surprises
Questions, answered straight
FAQ
Who actually uses Miradorly day-to-day?
Two groups. Writers (engineers, tech leads) keep editing docs in Cursor / Claude Code / their IDE — they barely open Miradorly except to verify rendering. Readers — your clients, PMs, designers, HR, sales, leadership — open the portal in a browser and get the answers they need without ever touching a repo. Tech-savvy readers can also point an MCP-capable AI client at the docs, but the portal is the default path.
Does Miradorly replace Cursor / Claude Code / my editor?
No, and that's the point. You keep writing docs wherever you write them today — Miradorly just renders, organises, and shares them. Push a commit, see it on the portal.
Do my clients need a GitHub or GitLab account?
No. They sign in to Miradorly with email or Google. They never see your repo.
Why not just use GitBook or Mintlify?
Both want you to use their editor. GitBook starts at $65/site + $12/user (≈$173/mo for a 10-person team). Mintlify's MCP only works on public docs — useless for private client work. Miradorly is an overlay, not a replacement, and the MCP works on private docs with role-based access.
How is this different from GitHub Wiki or Docusaurus?
GitHub Wiki has no comments your clients can use without GitHub accounts. Docusaurus is a framework you have to build, deploy, and maintain — and Giscus comments require a GitHub login from every commenter. Miradorly is hosted, ready in 30 seconds, and your clients sign in with email.
How does the MCP server work? Is my data safe?
OAuth 2.1 + PKCE. Each MCP connection inherits the user's permissions. If your client's AI agent connects with their commenter account, it can search only the documents they're allowed to see, and .docignore files are never indexed. Read-only by design — agents can read, they can't overwrite your docs.
What stacks do you support?
Anything in a git repo as .md or .mdx files. We render standard Markdown + GFM, code blocks with syntax highlighting, Mermaid diagrams, tables of contents, and cross-page links.
Can I publish some pages publicly?
Yes. Per-page or per-project. Useful for marketing docs, support pages, or open handbooks (à la the GitLab handbook).
What happens when a project ends or we cancel?
Nothing to migrate out — the source of truth was always your repo. Disconnect the integration and the portal simply turns off. You keep everything, because everything already lives in your git.
How does the free trial work?
Click “Start free”, leave your email, and we set up your workspace and send you access within 24 hours. You get 30 days of full access on either plan. No credit card up front. If on day 30 you want to continue, add a card and you're billed $29 or $79 starting day 31. If not, the workspace freezes and you don't pay a cent. Export your data any time.
Go deeper
Guides & answers we keep updated.
30 seconds from connecting your repo
Stop emailing markdown to clients.
Start your free 30 days — we'll set up your workspace and onboard you within 24 hours. Decide on day 30 whether to keep going.
- No credit card
- Cancel any time
- Your docs stay in your git