mcpbeat Sign in

pdfs.build MCP Server

answering

pdfs.build is answering right now. Last checked 12 min ago.

Design, publish and render PDF templates with Typst. Full template lifecycle over MCP.

Uptime history 50 days of history · worst day 98%
50 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
246 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check pdfs.build every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add pdfs-build --transport http https://backend.pdfs.build/mcp
Settings → Connectors → Add custom connector, then paste this address
https://backend.pdfs.build/mcp
~/.codex/config.toml
[mcp_servers.pdfs-build]
url = "https://backend.pdfs.build/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "pdfs-build": {
      "url": "https://backend.pdfs.build/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "pdfs-build": {
      "type": "http",
      "url": "https://backend.pdfs.build/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://backend.pdfs.build/mcp streamable-http sign-in 246 ms 12 min ago

Alternatives to pdfs.build

same job, measured the same way
boxpdf
by earonesty

Resource-only MCP server with docs and templates for the boxpdf TypeScript PDF layout library.

245 installs/wk local only
BrewMyPDF
by brewmypdf

Render PDFs from templates you design once: list templates, check the data shape, preview, render.

answering
boxpdf-html
by earonesty

Render HTML to PDF (html_to_pdf) plus boxpdf library docs and templates, for AI agents.

189 installs/wk local only
Formfeed
by formfeed-dev

Render PDFs and images from templates, validate data and convert Office files to PDF.

620 installs/wk answering
Layerre
by layerre

Turn Canva designs into templates and render image/PDF variants via the Layerre API.

119 installs/wk answering
Crow Nest
by crow-nest

Publish the apps you build with AI and share them like a Google Doc, with data, files and AI.

answering
docx4j Word documents
by plutext

Read, convert and fill Word (.docx) documents: templates, Markdown/HTML in and out, PDF with math.

local only
Bulkrender
by ayo-nci

Generate DOCX and PDF documents from AI assistants using BulkRender templates.

59 installs/wk local only

pdfs.build — questions

Answers built from our own checks of this server.

Why is there no tool list for pdfs.build?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is pdfs.build working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 246 ms. The bar chart above shows every period we have measured.
How do I connect pdfs.build?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to pdfs.build?
No API key is involved. pdfs.build answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is pdfs.build?
It answers our handshake in 246 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.