6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
The official MCP demo server for rendering a PDF in the chat as an interactive MCP Apps widget.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The PDF Viewer MCP server renders a PDF inside a conversation with Claude as an interactive viewer rather than a wall of extracted text. It is the Model Context Protocol project's own reference implementation of MCP Apps, published in the modelcontextprotocol/ext-apps examples directory. Four tools cover listing, reading, displaying and saving documents. It is a demo, not a product.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
List available PDFs that can be displayed
Read a range of bytes from a PDF (max 512KB per request). The model should NOT call this tool directly.
Show and render a PDF in a read-only viewer. Use this tool when the user wants to view or read a PDF. The renderer displays the document for viewing. The widget exposes app-registered tools for page navigation, text extraction, searching, and zoom control. Accepts local files (use list_pdfs), client MCP root directories, or any HTTPS URL.
Save annotated PDF bytes back to a local file. The model should NOT call this tool directly — use interact with action: save_as instead.
Read from the server on 2026-08-18, including each tool's own safety annotations.
readOnlyHint have nothing to read.claude-desktop extension is a different deployment with nine listed tools; do not read its capabilities onto this endpoint.claude as the sole client under works-with.read_pdf_bytes caps at 512 KB per call, per the schema maximum of 524288 on byteCount. Larger documents need paging via offset and hasMore.list_pdfs and save_pdf operate on directories supplied at startup, and a public deployment supplies none.taskSupport is forbidden on all four tools, so none of them can run as a long-lived task.interact is documented in the repository but requires a flag not set here, so the hosted connector displays PDFs and cannot annotate, search or fill forms through a tool call.It is a demo. The server is published by the Model Context Protocol project itself as a reference implementation of MCP Apps, and it lives in the examples directory of the modelcontextprotocol/ext-apps repository on a host literally named example-server. Anthropic lists it at partner tier, but no vendor stands behind it commercially. Treat it as something to learn from and experiment with, not to build a workflow on.
Four, verified on the wire on 2026-08-18. Anthropic's directory listing names only one of them, display_pdf, so the listing is an incomplete subset rather than a stale snapshot. The three the directory omits are list_pdfs, read_pdf_bytes and save_pdf. Two of those three are marked in the server's own metadata as intended for the widget rather than the model.
Any HTTPS URL, plus local files the server was explicitly granted at startup. The README lists academic domains such as arxiv.org and zenodo.org under Allowed Sources, but we searched the server source on 2026-08-18 and found no host check at all. Validation tests the protocol only and rejects anything that is not HTTPS. Arxiv appears in the code solely to rewrite abstract links into PDF links.
No. All four tools ship with no annotations block at all, verified live on 2026-08-18. There is no readOnlyHint on the reading tools and no destructiveHint on save_pdf, which takes a URL and base64 bytes and writes a file. Absent annotations mean unknown, not safe, so a client cannot infer from the wire data which of these four calls writes to disk.
To local paths the server was explicitly given, and nowhere else. A file is writable only if it was named on the command line, or sits strictly under a granted directory. A path the MCP client sent as a file root is always read-only, and a directory named uploads stays read-only unless a flag is passed, because that is where Claude Desktop mounts attachments. With no roots and no arguments, nothing is writable.
Resources yes, prompts no. The initialize response declares a resources capability and resources/list returns exactly one entry: the MCP Apps widget at ui://pdf-viewer/mcp-app.html with MIME type text/html;profile=mcp-app. The server never declares a prompts capability, so prompts/list answers with JSON-RPC error -32601, method not found. That is capability absent, not a declared-but-empty listing.
You can connect it anywhere, but only Claude is listed as a supported client and only MCP Apps clients render the viewer. Anthropic's directory entry records claude alone under works with. In a client without the MCP Apps extension the display_pdf call still returns structured output, but no interactive viewer appears and the page navigation and search controls are unreachable.
server.ts and main.ts, https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/pdf-server (read 2026-08-18) · retrieved 2026-08-18interact, and the deployment notes on why interact is not registered in stateless HTTP mode · retrieved 2026-08-18tools/list, initialize, resources/list and prompts/list handshake against https://example-server.modelcontextprotocol.io/pdf/mcp — 2026-08-18 · retrieved 2026-08-18Connect PDF Viewer once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.