AI assistants can now read files directly

When you connect an AI assistant to Librario, download_file hands it a signed link to the PDF — but for at least one major AI tool, that isn’t enough. Claude.ai’s own safeguard against autonomously fetching links that came out of a tool call means it won’t follow that URL itself, so the file content never reached the model. The assistant could show you the link, but not read the file, summarize it, or answer a question about its contents without you opening it yourself first.

Librario’s MCP server now also exposes publication details and file content as MCP resources — content delivered over the same already-authenticated connection your assistant has, not a link it has to fetch on its own. Ask your assistant to look up a publication or read one of its attached files, and on any AI tool that supports MCP resources, the content comes back directly in the conversation. get_publication and download_file keep working exactly as before for tools that prefer a link.

This is a new permission, not an automatic upgrade to what your assistant could already do: reading file content directly needs its own tick on the consent screen, in addition to the existing permission to download files. Untick just the direct reading and download links keep working exactly as before. Decline file downloads altogether and both go away — the links and the in-conversation reading.

For accounts on an enterprise plan, administrators can also switch off AI file-content access account-wide, independent of what any individual user has consented to. With it disabled, download_file no longer returns a link — it points assistants to the publication’s page for the person to open themselves instead — and the file-content resource is refused outright.