
Bulkrender
- 1 repo stars
- Updated May 30, 2026
- ayo-nci/bulkrender-mcp
BulkRender is a MCP server that generates DOCX and PDF documents from AI assistant output using BulkRender templates.
About
BulkRender MCP connects your coding agent to the BulkRender document API so drafts become client-ready DOCX and PDF files from templates you already trust. developers who sell services, ship proposals, or hand off spec packs use it in Build when the agent has nailed the content but Word layout and PDF export would eat an afternoon. The server is published as bulkrender-mcp on npm (1.1.1) with stdio transport; by default it talks to https://api.bulkrender.com, and you only set BULKRENDER_API_URL when developing against a local BulkRender stack. It is a narrow integration—not a full CMS—meaning you keep templates and branding in BulkRender while Claude Code or Cursor fills variables and triggers renders. Register the MCP entry, add your BulkRender credentials or API access per BulkRender’s docs, and close the loop from chat to downloadable documents for stakeholders who still want files, not markdown in a repo.
- Generate DOCX and PDF from AI assistant content through BulkRender templates
- npm package bulkrender-mcp with stdio MCP transport
- Optional BULKRENDER_API_URL override for local API development
- Registry version 1.1.1 from GitHub ayo-nci/bulkrender-mcp
- Pairs agent drafting with production document formatting
Bulkrender by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env BULKRENDER_API_URL=YOUR_BULKRENDER_API_URL bulkrender-mcp -- npx -y bulkrender-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | bulkrender-mcp |
| Transport | STDIO |
| Auth | None |
| Last updated | May 30, 2026 |
| Repository | ayo-nci/bulkrender-mcp ↗ |
What it does
Turn agent-written specs, reports, and proposals into polished DOCX and PDF files using BulkRender templates without manual copy-paste in Word.
Who is it for?
Best when you already use BulkRender templates and want Claude or Cursor to produce finished document files automatically.
Skip if: Skip if you only need markdown in-repo or and do not use BulkRender for document templates and API access.
What you get
After you wire BulkRender MCP, the agent can render templated DOCX and PDF deliverables through the BulkRender API in one workflow.
- Templated DOCX files generated via BulkRender from agent content
- Templated PDF exports for stakeholders
- Repeatable agent-to-document pipeline over MCP
By the numbers
- npm package bulkrender-mcp version 1.1.1
- Default API base https://api.bulkrender.com
- stdio MCP transport
README.md
bulkrender-mcp
BulkRender MCP server. Generate DOCX and PDF documents from Claude, Cursor, Windsurf, Cline, and any other MCP-compatible AI assistant.
Quickstart
- Sign up at bulkrender.com
- Go to Settings, Integrations, AI Assistants (MCP)
- Click Generate MCP URL — copy it immediately, shown once
- Paste into your AI assistant (see below)
Connect your AI assistant
Claude.ai
Settings, Integrations, Add custom integration, paste your MCP URL.
Claude Desktop / Cursor / Windsurf / Cline
Add to your MCP config file:
{
"mcpServers": {
"bulkrender": {
"url": "YOUR_MCP_URL"
}
}
}
Claude Code (CLI)
claude mcp add bulkrender --scope user -- npx mcp-remote YOUR_MCP_URL
Verify:
claude mcp list
# bulkrender ✓ Connected
Tools
Authenticated tools (requires MCP URL)
| Tool | Description | Credits |
|---|---|---|
list_templates |
List all templates | 0 |
get_template |
Get template details and variable schema | 0 |
search_templates |
Search templates by name or tag | 0 |
generate_document |
Generate a single document (DOCX or PDF) | 1–2 |
generate_batch |
Generate documents for multiple records (up to 500) | 1–2 each |
get_batch_status |
Poll batch job status and get download URLs | 0 |
check_credits |
Check remaining credits | 0 |
refresh_document_url |
Get a fresh signed URL for an existing document | 0 |
estimate_cost |
Estimate credit cost before generating | 0 |
create_template_from_docx |
Create a reusable template from a DOCX URL | 0 |
submit_feedback |
Submit feedback or a bug report | 0 |
Credit costs: DOCX = 1 credit, PDF = 2 credits.
Walk-in tools (no account required)
For agents acting on behalf of end users who have no BulkRender account. Pay per session via Stripe.
| Tool | Description | Cost |
|---|---|---|
acp_list_public_templates |
List built-in templates (invoice, quote, contract, report, proposal) | Free |
acp_create_session |
Create a checkout session and get a Stripe payment URL | — |
acp_pay_session |
Charge a Stripe payment method directly (developer path) | Min $1.00 |
acp_get_session |
Poll session status, get download URLs when complete | Free |
Walk-in minimum charge: $1.00 (covers up to 10 DOCX or 5 PDF docs).
Public MCP URL (no account, walk-in tools only): https://mcp.bulkrender.com/mcp/acp
Usage examples
List templates:
"List my BulkRender templates"
Generate a document:
"Generate an invoice using the Invoice Template for Acme Corp, invoice #1234, dated 2025-01-15, amount $5,000"
Batch generation:
"Generate invoices for these 3 clients: Acme Corp ($5,000), Beta Inc ($3,200), Gamma LLC ($7,800)"
Troubleshooting
| Problem | Solution |
|---|---|
| Server not connecting | Regenerate your MCP URL from Settings, Integrations |
Template not found |
Use list_templates to get the correct UUID |
| Timeout on large batch | Batches over 10 records process async — poll get_batch_status |
429 Too Many Requests |
Rate limit hit — retry after a short pause |
Rate limits
| Endpoint | Limit |
|---|---|
| Document generation | 30 requests / minute per organisation |
| Template reads, credits | 30 requests / minute per organisation |
generate_batch counts as one request regardless of record count.
Links
Migrating from the npm package
The standalone npm package (npx bulkrender-mcp with BULKRENDER_API_KEY) is no longer supported. Use the hosted MCP URL instead — no install, no env vars, just paste the URL from your dashboard.
If you have the old config:
{
"mcpServers": {
"bulkrender": {
"command": "npx",
"args": ["-y", "bulkrender-mcp"],
"env": { "BULKRENDER_API_KEY": "br_live_..." }
}
}
}
Replace it with:
{
"mcpServers": {
"bulkrender": {
"url": "YOUR_MCP_URL"
}
}
}
Get your MCP URL from Settings, Integrations, AI Assistants (MCP) in your BulkRender dashboard.
Recommended MCP Servers
How it compares
Template-driven document render MCP, not a markdown-to-PDF CLI skill.
FAQ
Who is BulkRender for?
Developers and small teams that use BulkRender for branded DOCX/PDF templates and want their AI agent to trigger renders instead of exporting manually.
When should I use BulkRender?
Use it during Build when you have finalized agent-drafted content—proposals, reports, or spec packs—and need production DOCX or PDF output from your templates.
How do I add BulkRender to my agent?
Install bulkrender-mcp from npm, add io.github.ayo-nci/bulkrender to your MCP config with stdio transport, set BULKRENDER_API_URL only if not using the default api.bulkrender.com, and include your BulkRender API credentials as required by BulkRender.