DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find public full text for a DOI paper with Papergraph MCP

Discover public PDF candidates for a DOI and import the root paper when one eligible copy exists.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA reader who has a DOI from a citation list and needs a readable public copy of the paper.

The problemA DOI resolves to a landing page, not a readable paper, and finding a legal public full-text copy takes manual searching.

The outcomeA list of public full-text candidates for the DOI, and an imported root paper when exactly one eligible public PDF exists.

What you need first

  • uv installed (see the uv getting-started guide linked in the README)
  • An arXiv ID, a local LaTeX project with its main .tex file, or a born-digital PDF of a math paper
  • A workspace database location outside the repository

Steps

  1. Run uvx --from papergraph-mcp==1.2.3 papergraph-mcp discover-doi DOI to list candidates without downloading anything. (inferred, check the README)
  2. Review the candidates and choose one if several are returned, since multiple candidates require your selection.
  3. Run uvx --from papergraph-mcp==1.2.3 papergraph-mcp add-doi-paper WORKSPACE DOI to import the root paper when exactly one eligible public PDF exists. (inferred, check the README)
  4. Run uvx --from papergraph-mcp==1.2.3 papergraph-mcp get-paper-map --workspace WORKSPACE --paper-id PAPER_ID on the imported paper.

Prompt for your agent

Use the papergraph-mcp repo to discover public full-text candidates for DOI <doi>. Return the candidates with their sources and do not import anything until the user chooses one. Verify that no file was downloaded during discovery.

Caveat. Metadata is not full text, and PaperGraph does not bypass paywalls, so some DOI papers will have no importable copy.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page