Web page
Interactive launch brief
Rendered in a sandboxed preview, not trapped as a file attachment.
Build anywhere. Dock to MiraDock.
You used an AI coding tool to make something useful. MiraDock is where you put it: publish visual HTML Web pages and Markdown Bucket Docs, share them with people, and let agents read or write through MCP.
No GitHub repo, Vercel project, Supabase setup, or object storage bucket required for the artifact you just made.
Bucket workspace
Preview
Rendered HTML
Docs
Markdown
Sharing
Public/private
Web page
Rendered in a sandboxed preview, not trapped as a file attachment.
Markdown file
Readable by people and retrievable by agents as native context.
Micro DB
Part of the Bucket model, but not presented here as a live publishing action.
The Bucket
A Bucket is the core object: one shareable place for pages, docs, and context. It is meant to be opened visually by people and reached programmatically by agents.
MiraDock hosts Web pages as rendered HTML and Markdown files as Markdown, with images available for published work.
Buckets support public and private visibility, reusable share links, and public profile routes for discoverable work.
The public Discover route lists public Buckets, featured demo Buckets, topic filters, creators, and HTML badges when a Bucket includes HTML pages.
Visual first
MiraDock is not a code repository wearing a new label. HTML pages are meant to be inspected as pages. Markdown files are meant to be readable, linked, and reused as context.
Browse HTML BucketsHTML
Markdown
MCP
The wedge
Use an AI coding tool to make a useful page, note, report, guide, or small interactive artifact.
Connect through MCP with a write token, then create a Bucket and push HTML or Markdown without setting up hosting infrastructure.
Open it in MiraDock, make it public or private, invite collaborators, or send a share link when the Bucket should stay controlled.
Collaboration
MiraDock ships collaboration around public Buckets through roles, forks, pull-request proposals, and audit-backed settings.
Public Buckets can invite collaborators as editors, reviewers, or readers.
Public Buckets can allow forks, show attribution, and list public forks.
When enabled, signed-in users can propose changes to public Markdown files.
Public Bucket settings include audit history for important collaboration and visibility changes.
Agent-native
Humans get a clean visual surface. Agents get MCP tools and AI-readable endpoints, using public access or tokens depending on the Bucket's visibility.
Agents can create Buckets, push Markdown, push HTML, add images, and update metadata with the permissions you grant.
Agents can read public Buckets and token-protected private Buckets as reusable context.
Public Buckets expose Markdown, /llm.txt, and /context.json surfaces for tools that fetch URLs.
People and agents can read public Buckets.
Private Buckets stay controlled and require permission or tokens.
Create reusable links for controlled access without making a Bucket public.
A Bucket is a shareable workspace for the useful things an AI tool makes. Today that means rendered HTML Web pages, Markdown files, images, sharing, discovery, and MCP access.
No. Micro DB is part of the broader Bucket concept for structured data, but this homepage does not present it as a live feature.
No. MiraDock is for the moment after an AI tool made something useful and you need a durable place to put it.
Use the MCP setup guide to generate tokens and connect an MCP-aware tool. The homepage avoids hardcoding the endpoint because deployment URLs can change.
Save the useful thing your AI made in a durable workspace with sharing and agent access.
Start publishingStart with a Web page, a Markdown file, or a public Bucket worth sharing.