Who it is for
Developers evaluating MCP app rendering rather than teams with a document workflow.
Demo viewer that renders PDFs from a short allowlist of URLs
Overview
A demonstration connector from the Model Context Protocol community rather than a product. It renders PDFs from a restricted set of allowed sources, arxiv.org among them, with the restriction described as a security measure. The listing records one tool while the endpoint returns four, and two of those, byte-range reading and saving, carry descriptions instructing the model not to call them directly, which indicates they exist to back the viewer component rather than to be invoked as tools. The presence of a save path means this is not purely a reader. The tier is partner despite the demonstration framing.
Developers evaluating MCP app rendering rather than teams with a document workflow.
Four tools came back against the one claimed: list_pdfs and display_pdf for the viewer, plus read_pdf_bytes and save_pdf, whose own descriptions tell the model not to call them. The save path means the surface is not read-only.
Availability
PDF Viewer is listed in the Claude connectors directory only. Model Context Protocol Community has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them.
The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one.
Claude listing
PDF Viewer publishes 1 tool to Claude, a deliberately narrow surface; only 0.7% of the 1,253 Claude-listed connectors expose fewer.
The median Claude-listed connector filed under Productivity publishes 12, so this one sits 11 tools below its bucket's median, 439th of 462.
It falls in the 1-3 tools band, which holds 16.4% of the Claude directory.
A direct call to the endpoint returned 4 tools, 3 more than the 1 the listing publishes. Probed 2026-08-07.
list_pdfsread_pdf_bytesdisplay_pdfsave_pdfPDF Viewer publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally.
Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there.
https://example-server.modelcontextprotocol.io/pdf/mcp PDF Viewer carries partner verification in the Claude directory, which 474 of 1,253 listings do (37.8%). That is a review step past self-publishing, not an Anthropic-built server.
In the publisher's words
Demo interactive PDF viewer that renders PDFs from a limited set of allowed URLs (e.g., arxiv.org) for security reasons.
Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it.
Same company
Render and play generated sheet music from ABC notation
Claude
Demo viewer that renders Three.js scenes in the conversation
Claude
Nearby
PDF compression, conversion, merging and page edits
ChatGPT
PDF page editing, conversion, and sharing
ChatGPT
Edit, convert, and combine PDF documents
ChatGPT
Search indexed repos and pull an org's real code review standards
Claude
Document translation run through an interactive widget
ChatGPT
Global payroll, contracts, and org data from Remote
Claude
This is an independent catalogue entry compiled by Node8 from PDF Viewer's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Model Context Protocol Community, and inclusion here is not an endorsement.
Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot.