Mkdshare.DEV
Publish Markdown specs, runbooks, or client-facing docs from Claude or Cursor and share them with password or link access without spinning up a separate CMS.
Overview
mkdshare is a MCP server for the Build phase that publishes access-controlled Markdown documents from MCP-enabled AI tools via mkdshare.dev.
What is this MCP server?
- Streamable HTTP MCP remote at mkdshare.dev with Bearer token auth from account API & MCP settings
- Publish and revoke access-controlled Markdown shares from any MCP-enabled client
- Version 1.0.0 registry entry with required Authorization header for hosted remote
- Suited for solo builders sharing PRDs, changelogs, or support articles without deploying a blog stack
- Registry version 1.0.0
- Single remote endpoint https://mkdshare.dev/mcp (streamable-http)
- Required secret Authorization Bearer token
What problem does it solve?
Agent-written Markdown sits in chat or local files until you manually copy it into a host that does not match your agent workflow.
Who is it for?
Solo builders who draft docs in Claude or Cursor and need quick, gated links for stakeholders without maintaining a separate doc site.
Skip if: Teams that require Git-versioned docs in-repo, heavy WYSIWYG CMS workflows, or fully offline publishing with no third-party host.
What do I get? / Deliverables
After you register the remote MCP with your Bearer token, agents can publish shareable, permissioned Markdown pages in one step.
- Hosted Markdown pages with configurable access
- Shareable links produced from agent publish actions
- Centralized document sharing without a custom doc pipeline
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the primary job is turning agent-written Markdown into hosted, access-controlled documents you ship alongside the product. Docs subphase fits writers who treat shared Markdown as living documentation, handoffs, or lightweight landing copy rather than in-repo README-only files.
How it compares
Hosted Markdown publish MCP, not an agent skill or local file-write-only workflow.
Common Questions / FAQ
Who is mkdshare for?
Indie developers and small teams using MCP clients who want to share agent-produced Markdown with access control from mkdshare.dev.
When should I use mkdshare?
Use it when a spec, FAQ, or announcement is ready in your agent and you need a live link with permissions instead of exporting files manually.
How do I add mkdshare to my agent?
Sign in at mkdshare.dev, create a Bearer token under API & MCP, and add the streamable HTTP remote https://mkdshare.dev/mcp with Authorization in your MCP config.