Summary
Turns document generation into native AI operations. Exposes PDF creation, screenshot capture, and document rendering as MCP tools that any compatible agent can call directly. Useful when you need your AI assistant to produce formatted outputs beyond plain text, like generating reports, capturing web page screenshots, or creating printable documents on demand. The stdio transport means it runs as a local process, so document generation happens on your machine without external API dependencies. Reach for this when you want Claude or other MCP clients to handle the full pipeline from content creation to formatted delivery.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Tools
Public tool metadata for what this MCP can expose to an agent.
5 tools
docapi_generate_pdfConvert HTML to a PDF using DocAPI's headless Chromium renderer. Full CSS support: Flexbox, Grid, custom fonts, gradients, shadows. Args: - html (string): HTML to render. Inline styles and <style> tags work. Google Fonts URLs supported. - format ('A4' | 'Letter' | 'Legal' | 'T...5 params
Convert HTML to a PDF using DocAPI's headless Chromium renderer. Full CSS support: Flexbox, Grid, custom fonts, gradients, shadows. Args: - html (string): HTML to render. Inline styles and <style> tags work. Google Fonts URLs supported. - format ('A4' | 'Letter' | 'Legal' | 'T...
Parameters* required
htmlstringHTML content to convert to PDF
formatstringPaper format (default: A4)one of
A4 · Letter · Legal · Tabloiddefault: A4landscapebooleanLandscape orientation (default: portrait)default: false
margin_inchesnumberPage margin in inches 0–4 (default: 0.5)default: 0.5
print_backgroundbooleanInclude background colors and images (default: true)default: true
docapi_capture_screenshotScreenshot a URL or render HTML and capture it as an image. Returns the image inline so you can view it immediately. Common uses: Open Graph images (1200×630), social cards, page thumbnails, template previews. Args: - url (string, optional): A live URL to screenshot. Provide u...5 params
Screenshot a URL or render HTML and capture it as an image. Returns the image inline so you can view it immediately. Common uses: Open Graph images (1200×630), social cards, page thumbnails, template previews. Args: - url (string, optional): A live URL to screenshot. Provide u...
Parameters* required
urlstringLive URL to screenshot (e.g. https://example.com). Provide url OR html, not both.
htmlstringHTML to render and screenshot. Provide url OR html, not both.
widthintegerViewport width in pixels (default: 1200)default: 1200
formatstringImage format (default: png)one of
png · jpegdefault: pngheightintegerViewport height in pixels (default: 630)default: 630
docapi_check_creditsCheck remaining API credits and USDC top-up address for agent accounts. Only applicable to agent accounts (registered via docapi_register_agent). Human subscription accounts use monthly plan limits instead. Returns: { credits, usdc_address, rate, suggested_topup_usdc }
Check remaining API credits and USDC top-up address for agent accounts. Only applicable to agent accounts (registered via docapi_register_agent). Human subscription accounts use monthly plan limits instead. Returns: { credits, usdc_address, rate, suggested_topup_usdc }
No parameter schema in public metadata yet.
docapi_register_agentRegister a new DocAPI agent account programmatically. Returns an API key and USDC address — no email, no dashboard, no human step required. Use this when building software that needs PDF or screenshot generation. After registering, embed the api_key in the software and wire up...1 params
Register a new DocAPI agent account programmatically. Returns an API key and USDC address — no email, no dashboard, no human step required. Use this when building software that needs PDF or screenshot generation. After registering, embed the api_key in the software and wire up...
Parameters* required
notify_emailstringOptional operator email for low-balance alerts (one email per 24h when credits fall below 50)
docapi_generate_invoiceGenerate a professionally formatted invoice PDF from structured data. Returns a base64-encoded PDF. Args: - from_name (string): Sender's name or business name - from_email (string, optional): Sender's email - from_address (string, optional): Sender's address (\n for line break...15 params
Generate a professionally formatted invoice PDF from structured data. Returns a base64-encoded PDF. Args: - from_name (string): Sender's name or business name - from_email (string, optional): Sender's email - from_address (string, optional): Sender's address (\n for line break...
Parameters* required
datestringInvoice date (e.g. 'January 1, 2026'). Defaults to today.
notesstringAdditional notes shown at the bottom of the invoice
to_namestringRecipient's name or business name
due_datestringPayment due date
logo_urlstringURL of a logo image to display in the invoice header
to_emailstringRecipient's email address
from_namestringSender's name or business name
from_emailstringSender's email address
from_phonestringSender's phone number
line_itemsarrayLine items: description, quantity, unit_price
to_addressstringRecipient's address (use \n for line breaks)
tax_percentnumberTax percentage to apply to subtotal (e.g. 10 for 10%)
from_addressstringSender's address (use \n for line breaks)
invoice_numberstringInvoice number (e.g. INV-001)
currency_symbolstringCurrency symbol (default: $)default: $
MCP Registry
The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation
Development Status
2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).
Current key maintainers:
- Adam Jones (Anthropic) @domdomegg
- Tadas Antanavicius (PulseMCP) @tadasant
- Toby Padilla (GitHub) @toby
- Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov
Contributing
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
- Discord - Real-time community discussions
- Discussions - Propose and discuss product/technical requirements
- Issues - Track well-scoped technical work
- Pull Requests - Contribute work towards issues
Quick start:
Pre-requisites
- Docker
- Go 1.24.x
- ko - Container image builder for Go (installation instructions)
- golangci-lint v2.4.0
Running the server
# Start full development environment
make dev-compose
This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Alternative: Running a pre-built Docker image
Pre-built Docker images are automatically published to GitHub Container Registry:
# Run latest stable release
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
# Run latest from main branch (continuous deployment)
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
# Run specific release version
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
# Run development build from main branch
docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
Available tags:
- Releases:
latest,v1.0.0,v1.1.0, etc. - Continuous:
main(latest main branch build) - Development:
main-<date>-<sha>(specific commit builds)
Publishing a server
To publish a server, we've built a simple CLI. You can use it with:
# Build the latest CLI
make publisher
# Use it!
./bin/mcp-publisher --help
See the publisher guide for more details.
Other commands
# Run lint, unit tests and integration tests
make check
There are also a few more helpful commands for development. Run make help to learn more, or look in Makefile.
Architecture
Project Structure
├── cmd/ # Application entry points
│ └── publisher/ # Server publishing tool
├── data/ # Seed data
├── deploy/ # Deployment configuration (Pulumi)
├── docs/ # Documentation
├── internal/ # Private application code
│ ├── api/ # HTTP handlers and routing
│ ├── auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)
│ ├── config/ # Configuration management
│ ├── database/ # Data persistence (PostgreSQL)
│ ├── service/ # Business logic
│ ├── telemetry/ # Metrics and monitoring
│ └── validators/ # Input validation
├── pkg/ # Public packages
│ ├── api/ # API types and structures
│ │ └── v0/ # Version 0 API types
│ └── model/ # Data models for server.json
├── scripts/ # Development and testing scripts
├── tests/ # Integration tests
└── tools/ # CLI tools and utilities
└── validate-*.sh # Schema validation tools
Authentication
Publishing supports multiple authentication methods:
- GitHub OAuth - For publishing by logging into GitHub
- GitHub OIDC - For publishing from GitHub Actions
- DNS verification - For proving ownership of a domain and its subdomains
- HTTP verification - For proving ownership of a domain
The registry validates namespace ownership when publishing. E.g. to publish...:
io.github.domdomegg/my-cool-mcpyou must login to GitHub asdomdomegg, or be in a GitHub Action on domdomegg's reposme.adamjones/my-cool-mcpyou must prove ownership ofadamjones.mevia DNS or HTTP challenge
Community Projects
Check out community projects to explore notable registry-related work created by the community.
More documentation
See the documentation for more details if your question has not been answered here!
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →Configuration
DOCAPI_API_KEY*secretYour DocAPI API key from docapi.co
Categories
Registryactive
Package@docapi/mcp
TransportSTDIO
AuthRequired
UpdatedMar 18, 2026
