Science1 publisher2 min readPublished
Paper2Agent converts a published paper's code into an MCP server a chat agent can query
The framework analyses a paper and its codebase and exposes the workflows as tools a chat client can call, with case studies on AlphaGenome, Scanpy and TISSUE that the authors say reproduce the original results.
The Scientist · Science desk
What happened
- A Nature paper introduces Paper2Agent, an automated framework that turns a paper's manuscript, supplementary materials, datasets, code and workflows into an AI agent the authors describe as a virtual corresponding author.
- The case studies produced an agent that uses AlphaGenome to interpret genomic variants and agents built on Scanpy and TISSUE for single-cell and spatial transcriptomics analyses.
- In a further case study, several Paper2Agent agents worked together to prioritize a causal gene for psoriasis.
Compiled by The ScientistSomething wrong?How this is made
Why it matters
- capability A biologist who does not want to handle API keys, client objects and output modality selection can still put a question to an AlphaGenome-derived agent, so the entry price for a published method falls to knowing what to ask.
- constraint Validation generated by the same pipeline that built the wrapper bounds what a user can trust: it covers execution and reproduction of published outputs, and fit to the data the user brings sits outside that.
- precedent If authors start shipping an MCP server as part of a paper, someone has to keep it running after publication. That upkeep lands on authors, publishers or hosts, not on the reader who used to do the installing.
Paper2Agent writes its own tests. The pipeline analyses the paper and its codebase with multiple agents, builds the model context protocol server, then generates and runs tests to refine that server and increase its robustness [2]. A test written by the same pipeline that wrote the wrapper can show that a tool executes and returns what the paper returned. That is a narrower check than whether the tool suits a dataset the paper never saw.
The authors locate the failure of reuse in setup. A reader has to find the code repository, install dependencies, configure environments and work out the correct inputs and outputs [6]. "Even with well-maintained repositories, this process is often non-trivial," they wrote [7]. For AlphaGenome the friction is itemised: install the environment, create client objects with API keys, construct inputs such as variant objects, select the output modalities, and understand the API hierarchy and parameter semantics along the way [8]. An agent removes that setup. Which output modality answers the biologist's question is still a judgement call.
One case study goes past reuse. Several Paper2Agent agents worked together to prioritize a causal gene for psoriasis [9]. The answer a user gets depends on the model doing the calling as much as on the code being called: the route to that output runs through a chat agent, because the paper MCPs are connected to a client such as Claude Code, which invokes the paper's tools in response to natural language [3].
Three tools appear in the case studies [11], against a claim pitched at the whole literature: the authors write that any research paper can be converted into an agent that embodies the knowledge and methods described in the publication [14]. The validation reported in the abstract is that the agents reproduce the results of the original papers and carry out novel user queries [5]. The abstract does not state how many papers the pipeline was run on, or how often a conversion failed [12]. Those two numbers would say whether the framework also works on a paper whose code has not been run since acceptance.
What to watch
- Whether an independent group picks its own codebases, runs the pipeline on them, and reports what happened.
- Whether journals or repositories begin hosting paper MCP servers alongside PDFs and supplementary files.
- Independent confirmation of the psoriasis gene that the collaborating agents prioritized.