Science tools, ready to run
Package a capability once. Enable it wherever you need it.
A Levin plugin packages one or more Skills, MCP services, and, when needed, a managed Runtime in one installable extension. Teams can keep repeatable research and engineering methods together, review them as a unit, and enable or disable the package without changing Lévin™ Harness itself.
What a Lévin™ Harness plugin can contain
-
Skill
Reusable instructions for a specific method or task. Available in the Skill catalog when the plugin is enabled.
-
MCP service
External tools, data sources, or hosted services. Managed under Plugin MCP Services after enabling.
-
Runtime
A managed execution environment for the plugin. Deploy it to this Mac or a remote GPU machine.
Disabling a plugin removes its runnable components from new Agent work while keeping the installed package ready to enable again.
Current official bundled plugins
| Plugin category | Typical use | Current plugins |
|---|---|---|
| Basic Tools | Structure validation, scoring, relaxation, and pKa analysis. | MolProbity, PyRosetta, PROPKA 3.0 |
| Antibody Design | Antibody and TCR numbering, sequence design, humanization, and structure design. | AbLang2, ANARCII, AntiBMPNN, HuDiff, RFantibody, IgGM |
| Fixed BB Design | Fixed-backbone sequence design, side-chain packing, and mutation or stability scoring. | ProteinMPNN, FAMPNN, LigandMPNN, ThermoMPNN |
| Structure Prediction | Protein and biomolecular-complex structure prediction. | OpenDDE Preview, AlphaFold3, Protenix v2 |
| Bio Language Model | Codon optimization and codon-sequence evaluation. | CodonTransformer |
| Protein Generation | De novo protein, binder, ligand, and backbone generation. | Pallatom Ligand, Protein Hunter, PXDesign, Genie3, Complexa, BoltzGen |
| Ensemble Prediction | Conformational ensemble sampling and prediction. | BioEmu |
The bundled catalog currently contains 24 plugins across these categories; the list can grow as new plugins are validated.
Choose the right plugin
A plugin is a package boundary. Treat everything it contains as one change to the Agent environment, even when it combines several small capabilities.
-
01Choose a plugin by category
Browse category descriptions to find the capability you need, then open the detail view to review its components.
-
02Open the plugin detail view
Read the plugin capabilities and confirm its scope matches the current task before installing or enabling it.
-
03Choose local or remote GPU deployment
Select this Mac or a Remote GPU machine based on the task's compute and data needs before starting the run.
The package is immutable after installation. Updates replace the managed copy, so keep custom changes in the source plugin or a separate project Skill.
Manage installed plugins
The installed list shows version, source, enabled state, component counts, and available updates. Use it to filter packages, inspect contents, update, disable, or uninstall.
| Action | Result |
|---|---|
| Disable | Keeps the package installed but removes its components from the Agent runtime. |
| Update | Installs the available catalog version after its package has been verified. |
| Uninstall | Removes the installed entry. Built-in packages can be installed again from the catalog. |
| Sync to remote | Copies supported local plugin configuration into the active remote workspace when explicitly requested. |
Enable, disable, and update operations refresh affected capabilities so the next Agent run sees one consistent plugin state.
Understand where a plugin runs
Some packages are local-only; others include a managed runtime or MCP server that can run on a configured Remote SSH or GPU device. The plugin detail and deployment controls identify the target before work starts.
| Target | What is deployed | What to check |
|---|---|---|
| Local Mac | Plugin package, local commands, hooks, and local MCP process. | Executable availability, permissions, and local paths. |
| Remote SSH / GPU | Supported runtime and remote MCP or background job. | Device health, deployment status, and returned artifact path. |
Uninstalling a plugin also closes its MCP sessions and cleans up runtime, job, and deployment state. Save required outputs before removing it.
Use a plugin in Chat or a Workflow
Once enabled, a plugin has two entry points: call it directly in Chat for the current task, or combine its Skills and MCP tools in a Workflow for a repeatable process.
-
01Activate a plugin in Chat
Type
@in the Chat composer and choose an enabled plugin Skill or MCP service for the current task. -
02Compose a plugin into a Workflow
Use a plugin Skill or MCP tool as a workflow step, connect it with the surrounding steps, then build and test the workflow.
Build your own Levin plugin
A plugin turns an open-source scientific tool into a package of Skill, MCP, and Runtime capabilities that Levin can use. Whenever possible, use goal mode: describe the outcome you need first, then let the Agent plan, build, test, and deploy the plugin toward that goal.
Build it with the Agent
- Start a chat with the Agent. Mention
@levin_plugin_creatorand attach the GitHub repository link for the open-source scientific tool. - Discuss the goal. Explain what you need and work through the requirements and implementation details with the Agent.
- Let the Agent build and verify the plugin. The Agent follows Levin's plugin workflow and acceptance checks as it develops the plugin.
- Deploy and iterate. The Agent tests the plugin locally or on a remote machine, then improves it until the complete flow works and the plugin is ready to use.
When the plugin needs an update, continue the conversation with the Agent, describe the change, and let it run the checks and deployment again.
Share and add a personal plugin
- Share the package. Ask
@levin_plugin_creatorto package the finished plugin. It produces one.levin-plugin.tgzfile that you can send to another Levin user. - Add it under Personal. Open Capabilities → Plugins → Personal, choose Add plugin, and select the package or a plugin source folder. If it includes a Runtime, choose this Mac or a Remote GPU machine on the detail page, complete deployment, and then enable it.