Skip to content

BrewMyPDF MCP server

Which MCP servers are BrewMyPDF's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to BrewMyPDF

Whose server it is
  • Registry namecom.brewmypdf/pdfverified in the MCP registry

The registry name sits under brewmypdf.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Staterequires sign-inchecked 2026-10-24
  • Server calls itselfbrewmypdf
  • Server version1
  • Protocol version2025-06-18

On 2026-10-24 the server answered and asked for a sign-in with a BrewMyPDF account (OAuth). It shows its tool list only to signed-in users, so we list none here.

Should an agent connect itNot proven either way yet
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • Asks for a sign-in.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer327 ms

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "pdf": {
      "type": "http",
      "url": "https://brewmypdf.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http brewmypdf https://brewmypdf.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://brewmypdf.com/mcp as a custom connector in the settings.

The first time it connects, the client opens a BrewMyPDF sign-in.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.