docs.page
Instantly serve markdown from any GitHub branch as modern, agent-ready docs, with AI chat, MCP, and llms.txt.
Links
README
From the repo.
Free and open-source
Docs for humans + agents
Instantly serve markdown from any GitHub branch as modern, agent-ready docs, with AI chat, MCP, and llms.txt.
Homepage • Documentation • Quickstart • Contribute • Discussions
Quick start
Prompt your agent:
Read https://use.docs.page/quickstart.md and set up docs.page in this repository.
Or set it up yourself:
npx @docs.page/cli init
Push docs.json and docs/ to a public GitHub repository. Your site is live at:
https://docs.page/{owner}/{repo}
Features
- Agent-ready: MCP server and auto-generated
llms.txton every public site. Add optional agent skills and enable Ask AI (beta) so LLMs and readers can query your docs without a separate mirror. - Git publishing: Deploy updates directly from your public GitHub repository. Eliminate build pipelines, hosting configuration, or infrastructure maintenance.
- Intelligent search: Built-in full-text index (Cmd+K) plus embedded AI chat. Locate information instantly without third-party tracking scripts or external setup.
- Markdown components: Add interactive components to your docs with MDX for richer experiences than standard Markdown.
- Branches & versions: Serve any Git branch, tag, or release as a distinct documentation site. Organise versions and live staging previews on the fly.
- Modern interface: Style your docs site using shadcn/ui design standards. Customize components easily to match your brand identity.
Should I use docs.page?
Bring your docs into the agentic age. Use docs.page when you want markdown from a public GitHub repository served as a modern documentation site for human readers and AI agents, without build pipelines, hosting setup, or a docs SaaS.
Not sure how docs.page compares to Docusaurus, Mintlify, or GitHub Pages? See comparisons.
License
See LICENSE.
Built and maintained by Invertase.
Collected info
- ★ 675 stars
- ⎇ 101 forks
- Language: TypeScript
- Source updated: 9/21/2026
Config for your environment
Replace {MCP_ENDPOINT_URL} with this MCP’s endpoint URL (from its repo or docs above). No API key — you connect directly.
Tool
OS
Config file: ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "{MCP_ENDPOINT_URL}"
}
}
}Paste into mcpServers in the config file. Restart Cursor after saving.
If this MCP is also published on mcpchannel.ai, you can subscribe from Browse and use the gateway config there instead.