ipro-agent
An independent, agent-drivable reimplementation of the published IPRO procedure (Iterative Protein Redesign and Optimization).
Unsupported research code, maintained by the Chowdhury Lab; please use GitHub issues. It implements a method published by the Maranas group (Penn State), cited under Citing. It is not their software and is not endorsed by them. None of their code is in it.
IPRO as published is a suite of programs wired to specific case studies: the molecules, the design positions and the objective live in a per-case Python input deck. This repo keeps the machinery and replaces the wiring with a declarative problem statement, so the same optimizer can be pointed at an arbitrary protein and an arbitrary stated goal, by a person or by an LLM agent.
You give it:
- a goal in plain language, mapped to one of five objectives;
- structures of the interacting partners (protein, peptide, small molecule, transition-state analogue);
- the positions where mutation is allowed, and the amino acids allowed at each.
It writes the rotamer-selection MILP that encodes those constraints, then iterates: perturb → choose optimal rotamers → dock → relax → accept or reject on energy. Out comes a design sequence, the per-iteration energies, and an ensemble of the best designs.
Quick start
One command, if you just want it working:
bash scripts/bootstrap.sh
That creates the environment, reports what resolved, runs the test suite and the shipped example, and prints the exact commands and MCP config with your own paths filled in. Safe to re-run; deletes nothing.
What using it looks like: resolve the positions, prove the constraint reached the solver, run, and read the refusal. Reconstructed rather than recorded, from real output of the shipped example. More worked prompts, with what each one produces.
By hand instead. The install step is not optional: rotamers come only from
PyMOL's mutagenesis wizard, and pymol-open-source is conda-only, so
pip install alone cannot give you a working design pipeline:
conda env create -f environment.yml && conda activate ipro-agent
Then check what resolved. Everything below runs from the repo root; nothing needs installing the package itself:
python3 scripts/doctor.py --require pymol
python3 -m ipro_agent validate examples/ompf_pore/spec_smoke.yaml
python3 -m ipro_agent run examples/ompf_pore/spec_smoke.yaml --run-dir runs/smoke
python3 -m ipro_agent status runs/smoke
What that run produces, so you can tell a working install from a real result:
with the shipped seed it accepts 3 iterations and reports zero mutations. The
native residues win at those four positions because no reference-energy term
offsets the packing bias against large side chains, and the run says so in its
notes. That is a successful smoke test rather than a design. For a run that
does mutate, see examples/ompf_pore/spec_full.yaml (25 positions,
~85 s/iteration) or set goal_options.reference_energies.
For agents
Clone the repo, create the conda environment above, open it with an agent and
ask in plain language: "redesign this thioesterase to prefer C12 over C14, you
may change residues 110, 113 and 117". The skill at
.claude/skills/ipro-agent/SKILL.md loads
itself from its description. Beyond that one environment step there is nothing
for the agent to configure; it should run scripts/doctor.py first and report
the mode it finds.
To read it yourself, it is the operating manual: goal selection, spec format, encoding user constraints into the integer program, the degraded modes, and a validation checklist to work through before reporting a design.
Use it from another agent (MCP)
The section above assumes an agent that has cloned this repo and can read
SKILL.md. For an agent working somewhere else, or one that cannot read a repo
at all, there is an MCP server. It presents the tool as fifteen typed tools
rather than a manual to read:
pip install git+https://github.com/chowdhurylab-studio/ipro-agent
{"mcpServers": {"ipro-agent": {"command": "ipro-agent-mcp",
"cwd": "/path/to/a/clone"}}}
That block goes in your client's MCP config (Claude Desktop's config file,
.mcp.json for Claude Code, Cursor's settings; the shape is shared).
bash scripts/bootstrap.sh prints it with your own paths already filled in,
which is the easier route.
Set cwd to a checkout even when you installed with pip. The documents served
as resources (ipro://skill and the rest) ship with the repository rather than
inside the package, so a server that cannot see a checkout will list them and
then tell the agent where to fetch them instead of serving them. Use the conda
environment's python rather than a bare python3: a local server sees only what
its own interpreter can import, so the wrong one means PyMOL does not resolve
and no design can run.
| Tool | What it does |
|---|---|
ipro_doctor |
what resolved, and whether a design is possible at all |
ipro_setup |
create the environment, when the agent has a shell and the user says so |
ipro_fetch_structure |
download a PDB entry by id, optionally one chain; the only networked tool |
ipro_inspect_structure |
chains, residue span, sequence, and what residue a position number actually is |
ipro_goals |
the five objectives and the paper each comes from |
ipro_validate |
check a spec before spending CPU |
ipro_positions |
propose design positions from the structure |
ipro_score |
measure a structure without designing |
ipro_milp |
emit the integer program, to prove the constraints are in it |
ipro_run |
launch a run detached, returns a run id |
ipro_status |
poll it; carries the mode and the notes |
ipro_result |
the design itself: mutations, sequence, ensemble, and the PDB on request |
ipro_iterations |
the trajectory's tail, with the reason each iteration was rejected |
ipro_runs |
every run this server can see, for a lost id |
ipro_cancel |
stop a running design, keeping what it has written |
ipro_fetch_structure and ipro_inspect_structure are there because a remote
agent has no shell: without them "redesign OmpF, you may change residues 18,
20, 38 and 40" cannot even be started, and a position number that is never
resolved against the structure silently designs a different residue than the
user named. Resolve the positions and say what they are before writing a spec;
docs/EXAMPLE_PROMPTS.md prompt 1 is that path end to end.
A spec can be a file path or inline YAML, since an agent usually has it in
context rather than on disk. ipro_run refuses to launch when PyMOL has not
resolved, rather than starting a job that dies at the first rotamer harvest.
It also serves the documents, so a remote agent is not worse informed than one that cloned the repo. Fifteen tool descriptions cannot carry the operating manual, so the manual is a resource instead:
| Resource | |
|---|---|
ipro://skill |
the full operating manual: goal selection, spec format, degraded modes, validation checklist |
ipro://house-rules |
the non-negotiables, short |
ipro://example-spec |
an annotated spec to copy from |
ipro://design-notes, ipro://milp, ipro://install, ipro://responsible-use, ipro://example-expectations |
provenance, the integer program, dependencies, scope of use, what the example can reproduce |
There are also three prompts, which clients show as slash commands:
ipro-redesign (walks the whole documented order for a new protein),
ipro-check-setup, and ipro-report (turns a finished run into an honest
report).
The server can install its own dependencies. It is pure standard library, so it
starts on a machine with nothing installed, which is the only way it can report
that nothing is installed. ipro_doctor names what is missing and ipro_setup
reports the exact command; with confirm=true it runs the conda install itself.
Measured in an empty virtualenv: the server starts, reports
missing_required: ['numpy', 'Bio', 'yaml'], finds mamba, and hands back the
command without installing anything.
One limit remains. It is a local server, so the environment it installs has to
be the one the server itself runs in: after ipro_setup finishes, point your
MCP config at that environment's python
(.../envs/ipro-agent/bin/python -m ipro_agent.mcp_server), or PyMOL still
will not resolve. ipro_setup says so in its result.
Documentation
| File | Contents |
|---|---|
| .claude/skills/ipro-agent/SKILL.md | how an agent drives this tool (auto-loaded) |
| docs/DESIGN.md | every capability traced to its paper and equation, and every deviation |
| docs/MILP.md | the integer program in full |
| docs/INSTALL.md | dependencies and what each one unlocks |
| examples/ompf_pore/ | worked case, with an EXPECTED.md of what can and cannot be compared |
| docs/EXAMPLE_PROMPTS.md | five prompts to paste at an agent, and what each actually produces |
| docs/HANDOFF.md | passing this to a labmate, a student or your future self |
Dependencies
Required: Python ≥ 3.10, numpy, Biopython, PyYAML, and PyMOL, which has
no fallback. Rotamers come only from its mutagenesis wizard; there is no
built-in rotamer builder, and backends.mutate: builtin is refused by the config.
Without it validate, positions and goals work; milp, score and run
do not, because all three build rotamer tables and rotamers come only from
PyMOL. Measured on a machine with no PyMOL discoverable: validate and goals
exit 0, milp and score refuse with "backend missing: no PyMOL available". conda env create -f environment.yml installs all
five.
Genuinely optional, each resolved at run time with a documented fallback:
| Tool | Used for | Without it |
|---|---|---|
| PyRosetta | backbone relaxation, scoring | loop runs fixed-backbone; energies come from a screening function |
| AutoDock Vina | re-docking partners after mutation | input poses are kept |
| MILP solver (CPLEX, Gurobi, CBC, HiGHS, GLPK) | proving the optimal packing | a heuristic that does not prove optimality |
scripts/doctor.py reports what resolved and what a run will actually use. It
also refuses an interpreter below the floor: on Python 3.9 with every
dependency installed it reports can_run: false and exits 1, because
import ipro_agent fails there whatever else is present.
Platforms: developed and tested on macOS (Apple silicon), and used on Linux.
Windows is untested. The detached-run path has a Windows branch and the
interpreter search looks in Scripts/python.exe and %USERPROFILE%, but
nothing here has ever run on Windows, PyMOL's conda package is the only
supported route to it, and a few paths assume a POSIX shell. On Windows use WSL
2, where the Linux instructions apply unchanged.
Status and honesty
This is research code and an independent reimplementation. It was written from
the published formulations; the released upstream source was read for behaviour
the papers leave ambiguous, and every value taken from it is cited as such in
docs/DESIGN.md §2 and docs/MILP.md. No upstream IPRO code is copied. It
substitutes an open stack for the original's CHARMM, GAMS/CPLEX and in-house
Monte-Carlo docking, so energies are not comparable to the numbers in the IPRO
papers, and identical designs should not be expected.
What it has actually been run on: every end-to-end run in this repo has been on one chain of PDB 2OMF, with 1CRN as a test fixture. No other protein has been tried here, and no design from this code has been synthesised or tested experimentally. The checks listed below are self-consistency checks of the optimizer rather than validation against experiment.
What has been verified here: the MILP reproduces exhaustive enumeration exactly
on a test case (including with a class-cardinality constraint), the integer cuts
provably prevent revisiting a sequence, and the Metropolis temperature
reproduces IPRO's published calibration. The PyRosetta and AutoDock Vina paths
have now been executed. Both were installed deliberately to do so, and between
them that found seven defects, because neither path had ever run
(docs/DESIGN.md §7e). What remains unexercised is listed in
ipro_agent/energy/pyrosetta_backend.UNEXERCISED, which a test keeps honest.
One known defect is open, and it can produce a wrong answer that looks right.
The channel axis is fitted through the centroid of the design positions, so it
only follows the channel when those positions ring the lumen. When they do
not, as with four positions along one wall in the shipped smoke example, the
axis runs inside the protein and the reported "bottleneck" is a gap beside a
wall, which then passes PoreDesigner's published sub-4 Å filter. The run says
so in its notes and reports the axis clearance, but any pore radius from a spec
whose positions do not surround the channel must be treated as meaningless;
give goal_options.pore_axis explicitly instead. docs/DESIGN.md §7h has the
measurements, and why the clearance has to be measured on the input structure
rather than on a candidate.
Objectives of this kind reproduce the rank and sign of a change far better than its magnitude; published hit rates for this family of methods are roughly 24–43%. Every design is a hypothesis for the bench.
Responsible use
This is a research tool that proposes mutations. It does not know what it is being pointed at, and a coding agent driving it knows even less.
- Research use, on targets you are authorised to work on. Every design is a hypothesis for the bench rather than a validated construct; published hit rates for this family of methods are roughly 24–43%.
- Some targets need a human in the loop before anything is run, not after the result arrives: toxins, virulence factors and select agents; anything intended to change host range, transmissibility, immune escape or drug resistance; and any sequence heading for synthesis. If the goal is to make a protein better at harming, that is not a use this repo supports.
- An agent must not relax the user's stated constraints to make a failing run
succeed. The troubleshooting tables offer knobs (widen
allowed, loosen a catalytic-distance restraint, raisemax_self_energy) and every one of them changes the scientific question. Report the change; do not absorb it. - Report the mode and the notes with every design, a house rule in
AGENTS.md. A run in a degraded mode, or one where nothing was accepted, is not a design and must not be presented as one. - Screening energies from the built-in backend are not kcal/mol comparable to the papers, and no design from this code has been tested experimentally.
Citing
For the implementation, cite this repository. CITATION.cff carries the
metadata, and GitHub's "Cite this repository" button renders it.
For the method, cite the original work. docs/DESIGN.md has the full list
with DOIs; the main entries are:
- IPRO: Saraf, Moore, Goodey, Cao, Benkovic, Maranas. Biophys J 90:4167 (2006).
- The IPRO suite: Pantazes, Grisewood, Li, Gifford, Maranas. J Comput Chem 36:251 (2015).
- PoreDesigner: Chowdhury et al. Nat Commun 9:3661 (2018).
- IPRO+/−, insertions and deletions: Chowdhury et al. Structure 28:1344 (2020).
- Specificity redesign: Grisewood et al. ACS Catal 7:3837 (2017).
- OptZyme: Grisewood et al. PLoS ONE 8:e75358 (2013).
Licence
MIT: see LICENSE, with the scope spelled out in NOTICE.md.
That covers this implementation only: the code, tests and documentation written here. Three things in this tree are deliberately not covered, and the licence file says so in its own words:
| The method | Not ours and not licensed by us. Cite the papers above for the method and this repo only for the implementation. |
refs/ |
Publisher PDFs and clones of upstream repositories, kept locally for provenance and git-ignored: they are not in this repository and are not redistributed. |
| Optional dependencies | PyMOL, AutoDock Vina, Open Babel, PyRosetta and any MILP solver are separately licensed and separately installed. PyRosetta requires its own licence; see docs/INSTALL.md. |
No upstream IPRO code is copied here. That is what makes publishing this
defensible: the upstream releases carry no LICENSE file at all, and the
Maranas group's pages describe the suite as freely available to academic users.
This is an independent reimplementation rather than a fork, written from the
papers, with the released source read only for behaviour the papers leave
ambiguous (chiefly a handful of numeric defaults); every such value is cited as
coming from the source in docs/DESIGN.md §2 and docs/MILP.md.
docs/DESIGN.md §6 maps every capability back to the paper and equation it came
from, so the provenance of each piece is checkable.
Metadata
Release files for ipro-agent 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ipro_agent-0.1.0.tar.gz | 319.5 kB | With provenance | Details for ipro_agent-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ipro_agent-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ipro_agent-0.1.0-py3-none-any.whl |
Total release size: 558.9 kB
Release files / ipro_agent-0.1.0.tar.gz
| Download URL | ipro_agent-0.1.0.tar.gz |
|---|---|
| Size | 319.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ecc3192f57d315ef0c43d92cebbf75bd7e647fd40d93313214504fd067f11fa
|
|
BLAKE2b-256 checksum How to use checksums |
92a493bdfc3a88e6a514152990989ee26a87cc286f3fafb385f7aec4f5e3f07d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logRelease files / ipro_agent-0.1.0-py3-none-any.whl
| Download URL | ipro_agent-0.1.0-py3-none-any.whl |
|---|---|
| Size | 239.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
178200782d863250dd1598af7a0fd2beb9c83e1c1395bcafa23512a45e2c5eeb
|
|
BLAKE2b-256 checksum How to use checksums |
15b92da80ab16924dea4ad29811f992fc3b6590fcb167478b3d42a4f29a624b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logSecurity for ipro-agent 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for ipro_agent-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.