Doc81 🚀
Doc81 is a developer document template platform that helps you create, manage, and use document templates proven by many experts. It provides both a local mode for working with templates on your filesystem and a server mode for accessing templates out there.
Features
- Your Document -> Scalable Document Template in 2s
- Find appropriate document templates on demand
- MCP (Model Control Protocol) integration for AI assistant compatibility
- API server for general usage
Installation
Prerequisites
- Python 3.10+
- pip or pipenv
Quick Start
MCP (recommended)
Cursor (default)
- setup MCP
> uvx --with doc81 doc81-mcp-cli setup
This command add .cursor/rules/doc81.mdc. This prompt will guide cursor how to ask and do the work for you.
- add MCP
// mcp.json`
{
"mcpServers": {
"doc81": {
"command": "uvx",
"args": [
"--from",
"doc81",
"doc81-mcp"
],
"env": {
"DOC81_PROMPT_DIR": "<your local prompt directory>"
}
},
}
}
See Configuration for details.
- Use the cursorrule to generate document based on the template.
// cursor ask/agent
> Help me write a runbook in @your-new-doc.md
cursor: List template (function call)
cursor: Get template (function call)
Let me copy the runbook template to your-new-doc.md. ...
Usage
Creating Templates
Templates are markdown files with frontmatter metadata. Create a template file with the following structure:
---
name: Template Name
description: Template description
tags: [tag1, tag2]
---
# Your Template Content
Content goes here...
MCP API
Doc81 integrates with MCP for AI assistant compatibility:
list_templates- Lists all available templatesget_template(path_or_ref)- Gets a specific template by path or reference
Configuration
Doc81 can be configured using environment variables:
DOC81_ENV- Environment (dev/prod, default: dev)DOC81_MODE- Mode (local/server, default: local)DOC81_PROMPT_DIR- Directory containing templates (default: project's prompts directory)
Development
Testing
uv run python -m pytest tests/
License
Metadata
Release files for doc81 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| doc81-0.1.6.tar.gz | 438.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| doc81-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 458.9 kB
Release files / doc81-0.1.6.tar.gz
| Download URL | doc81-0.1.6.tar.gz |
|---|---|
| Size | 438.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc5c7b93b58510db64a17ef5474fa841b6d0f67b4d8433082b67da5353c9c9ec
|
|
BLAKE2b-256 checksum How to use checksums |
ff78a55f2ae353c029ae87b5bc535db37423732e0b764c9b4b2599c345e196ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Release files / doc81-0.1.6-py3-none-any.whl
| Download URL | doc81-0.1.6-py3-none-any.whl |
|---|---|
| Size | 19.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dddad88c5d62b10c65b6f4a1c0e4806eb655ca071ec3c3fa56ec6d4fe48cdd36
|
|
BLAKE2b-256 checksum How to use checksums |
995a02ef5924edaab5497527aa8ba9d235f1b613b151c49ae4ead0c15be02ca5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Security for doc81 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.