pdfs.build MCP server

pdfs.build is the official remote MCP server from pdfs.build. It answers at https://backend.pdfs.build/mcp over streamable HTTP and asks you to sign in with your pdfs.build account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 6 November 2026, got the sign-in challenge, so it is up.

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

Description as the publisher wrote it.

What pdfs.build needs before it works

A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your pdfs.build account, and the tools appear once you have approved it.

Add pdfs.build to your AI client

Every block below points at https://backend.pdfs.build/mcp. Pick your client and copy.

claude mcp add --transport http pdfs-build https://backend.pdfs.build/mcp

{
  "mcpServers": {
    "pdfs-build": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://backend.pdfs.build/mcp"]
    }
  }
}

{
  "mcpServers": {
    "pdfs-build": {
      "url": "https://backend.pdfs.build/mcp"
    }
  }
}

{
  "servers": {
    "pdfs-build": {
      "type": "http",
      "url": "https://backend.pdfs.build/mcp"
    }
  }
}

{
  "context_servers": {
    "pdfs-build": {
      "url": "https://backend.pdfs.build/mcp"
    }
  }
}

{
  "mcpServers": {
    "pdfs-build": {
      "serverUrl": "https://backend.pdfs.build/mcp"
    }
  }
}

{
  "mcpServers": {
    "pdfs-build": {
      "url": "https://backend.pdfs.build/mcp"
    }
  }
}

name: pdfs.build
version: 0.0.1
schema: v1
mcpServers:
  - name: pdfs.build
    type: streamable-http
    url: https://backend.pdfs.build/mcp

{
  "mcpServers": {
    "pdfs-build": {
      "httpUrl": "https://backend.pdfs.build/mcp"
    }
  }
}

{
  "mcpServers": {
    "pdfs-build": {
      "type": "http",
      "url": "https://backend.pdfs.build/mcp"
    }
  }
}

{
  "mcpServers": {
    "pdfs-build": {
      "url": "https://backend.pdfs.build/mcp"
    }
  }
}

goose://extension?url=https%3A%2F%2Fbackend.pdfs.build%2Fmcp&type=streamable_http&id=pdfs-build&name=pdfs.build

Is pdfs.build up right now?

It answered our last check on 6 November 2026 in 106 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to pdfs.build

Questions about pdfs.build

Is there an official pdfs.build MCP server?

Yes. It is published by pdfs.build and served from backend.pdfs.build, the vendor's own domain: https://backend.pdfs.build/mcp.

How do I sign in to pdfs.build?

Add the server with a setup above. The first time your client connects it opens the sign-in page for pdfs.build; approve it and the tools load.

Is pdfs.build down?

It answered our last check on 6 November 2026 in 106 ms. Over 4 checks since 23 September 2026 it answered 4.

How do I add pdfs.build to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://backend.pdfs.build/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does pdfs.build need an API key?

It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.

Where this comes from

Publisher: build.pdfs. Endpoint host: backend.pdfs.build. ARD identifier: urn:air:build.pdfs:mcp:pdfs-build. First indexed 18 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.