Productivity · Remote MCP server
PDFMakerAPI
Turn a description into a shareable, editable PDF - invoices, certificates, reports, resumes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.GerardoBarrera/pdfmakerapi-mcp- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-19
- Updated
- 2026-06-19
- Publisher
- GerardoBarrera (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/GerardoBarrera) · how
- Listed under
- PDF MCP servers
- Website
- pdfmakerapi.com
- Repository
- github.com/GerardoBarrera/pdfmakerapi-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.pdfmakerapi.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- No - could not connect (DNS or connection failure)
- Handshake
- -
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @pdfmakerapi/mcp | 1.0.0 | stdio |
How to connect PDFMakerAPI
PDFMakerAPI is a remote MCP server: there is nothing to install. Its endpoint is https://api.pdfmakerapi.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @pdfmakerapi/mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @pdfmakerapi/mcp@1.0.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pdfmakerapi-mcp": {
"command": "npx",
"args": [
"-y",
"@pdfmakerapi/mcp@1.0.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| PDFCrowd PDF ExportCreate polished, professional PDFs from a single prompt. Documentation, reports, charts, and more. | Local · stdio |
| pdffrLocal, private PDF to Markdown for agents: geometry-first parsing, OCR only where needed. | Local · stdio |
| pdfgate.comMCP server for the PDFGate API. Generate PDFs, manage documents and handle e-signatures. | Remote & Local · HTTP, stdioLive check: sign-in required |
| PdfintactExtract tables, text and formulas from PDFs, including scanned pages and broken text layers. | Remote · HTTPLive check: ✓ handshake |
| pdfmuxPDF-to-Markdown extraction that audits its own output and flags any extractor's silent drops. | Local · stdio |
| pdfnative MCP - PDF/A & PDF/X-4 generation, PAdES signing & introspectionPDF MCP: generate PDF/A & PDF/X-4, sign & verify PAdES (LTV), forms, merge, split, encrypt. 28 tools. | Local · stdio |
| Pdfops MCPDeterministic PDF tools for AI agents: inspect fields, fill forms, merge PDFs, invoices. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| pdfrenderHTML and CSS to PDF MCP server with page headers, footers and page numbers. No headless browser. | Remote · HTTPLive check: ✓ handshake |