The engine, in the tools where you already work.
Two open-source sideload surfaces. Load them unpacked from the source repos, point them at your own engine (local or hosted), and get NovoMCP capability inside the tools you use every day. No store account required.
Browser
Chrome Extension
Molecule intelligence on any PubChem, ChEMBL, or DrugBank page. Hover any SMILES for instant properties, ADMET, and compliance.
- Profile cards on hover — properties, drug-likeness, structural alerts
- Side panel: ADMET + FAVES compliance + similarity search
- "Continue in AI" — pick up the session in any MCP-connected assistant
- Configurable engine URL — points at your local instance by default
Install
Chrome → Extensions → Developer mode → Load unpacked → point at the built /dist directory. Full steps in the repo README.
Documents
Word Add-in
ADMET tables inside your manuscripts. Paste a SMILES, get properties inline. Made for grant writers and med-chem publications.
- SMILES → property + ADMET table, inserted at the cursor
- Compliance flags (PAINS, DEA, EU REACH) rendered as citations
- "Refresh from engine" pulls the latest values when the ruleset moves
- Configurable engine URL — points at your local instance by default
Install
Serve the built /dist over HTTPS, then sideload the manifest via Word → Insert → Add-ins → Upload My Add-in. Full steps in the repo README.
Why sideload
A store-published extension defaults to a hosted backend that someone has to run. Sideload versions default to your engine — the same one you install from the OSS repo. Nothing about your data, your queries, or your compute has to leave your environment. Store-published convenience builds may ship later; the sideload versions are the reference.
Sideload the engine into your workflow.
Both repos ship with dev-mode install docs. If something's rough, open an issue.