BrewMyPDF
com.brewmypdfPublished by brewmypdf.comOfficial publisherv1.0.0Updated Oct 24, 2026
Render PDFs from templates you design once: list templates, check the data shape, preview, render.
Overview
Lets an assistant list, inspect, preview and render PDFs from templates you design in BrewMyPDF, using a hosted remote endpoint.
- What you can do
- BrewMyPDF is a hosted PDF generation service exposed over a remote MCP endpoint. According to the description, an assistant can list your templates, check the data shape a template expects, preview output, and render a PDF from a template. Templates are designed once in the service, and the assistant then drives rendering against them.
- When to use it
- Useful when you repeatedly produce PDFs from a fixed layout, such as invoices, reports or certificates, and want an assistant to fill in data and render them without building your own PDF pipeline.
- Requirements
- A remote MCP connection to the BrewMyPDF endpoint over streamable HTTP. A bearer API key is required in the Authorization header; the key is issued in the BrewMyPDF console on the Lite plan or above and is the same key used by the REST API. Network access is needed.
Installation
In SourceWeft
- Open BrewMyPDF in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.brewmypdf%2Fpdf/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"brewmypdf": {
"type": "http",
"url": "https://brewmypdf.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.0LatestSep 17, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.