{"version":"2.1.287","anchor":"inline-pdf-results-from-mcp-tools-and-only-the-first-pdf-pe","canonical_anchor":"inline-pdf-results-from-mcp-tools-and-only-the-first-pdf-pe","heading":"PDFs returned by MCP tools can be passed to Claude directly","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/inline-pdf-results-from-mcp-tools-and-only-the-first-pdf-pe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### PDFs returned by MCP tools can be passed to Claude directly\n\nA PDF returned by an MCP tool can now be handed to Claude as a document, and only the first PDF in a result is kept\n\n**Unclear.** The size limit's value is not known, and if it is zero, PDFs would never be passed directly.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When such a tool returns an embedded PDF that is within a size limit, Claude Code now passes it to Claude as a document. A PDF over the limit is handled the old way.\n\nIf one result contains two or more documents, Claude Code keeps the first and replaces the rest with the note \"[Another PDF in this result was left out: only the first is shown.]\"\n\n**Why**\n\nClaude can read PDFs from MCP servers natively instead of receiving them in a more generic form.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}