Skip to content

Avogadro libraries (avogadrolibs)

OpenChemistry libraries behind Avogadro, providing molecular data handling, rendering and extensible chemistry functionality.

Catalog updated ·

Overview

avogadrolibs supplies the main library and plugin functionality used by the Avogadro molecular editor. The separate avogadroapp repository provides its desktop GUI shell. This entry covers the libraries and their role in the application.

Official documentation separates core, IO, rendering and Qt-related modules. Library integration requires a compatible build and dependencies; installing a desktop binary is a different route from embedding the libraries. The BSD-3-Clause license covers this repository, while external dependencies require their own checks.

Key Features

  • Molecular structures and chemical file IO modules
  • Rendering and Qt GUI/plugin modules
  • Shared library architecture used by Avogadro

Use Cases

  • Embed molecular data handling in chemistry software
  • Develop visualization extensions for Avogadro

How to Use

Read the project structure and C++ API documentation, then select the relevant core, IO or rendering module. For source integration, follow the official build guide and satisfy the dependencies for the selected release. For interactive molecule editing, use the application distribution. No build or binary installation was performed.

Sources and verification

This entry describes capabilities documented by the linked project sources. Catalog edits are not evidence of a successful run, compatibility test or scientific performance evaluation.

Read the editorial and verification policy

Related resources

AQME

Open Source

AQME builds quantum-mechanical working environments end to end: conformer generation, input preparation, output checking and descriptor calculation across its CSEARCH, CMIN, QPREP, QCORR and QDESCP modules.

Open sourcePython

Cheminformatics · Computational Chemistry · Quantum Chemistry

Browser-based molecular docking platform using AutoDock Vina and Meeko for rigid-receptor docking, batch virtual screening, pose quality checks, interaction analysis, and downloadable PDF/ZIP results.

Cheminformatics · Computational Chemistry · Drug Discovery

OpenFF Toolkit

Open Source

The Open Force Field Toolkit is a Python toolkit for SMIRNOFF force fields and direct chemical environment perception, with documented export paths to OpenMM and other simulation engines.

Open sourcePython

Cheminformatics · Computational Chemistry · Drug Discovery

AiiDA

Open Source

AiiDA is a computational-science workflow manager that records calculation inputs, outputs and metadata in a provenance graph.

Open sourcePython

Computational Chemistry · Scientific Data

alchemiscale

Open Source

alchemiscale is a high-throughput execution system for alchemical free energy calculations that distributes work across HPC, cloud, bare-metal and volunteer compute resources.

Open sourcePython

Computational Chemistry · Drug Discovery · Scientific Data

alchemlyb

Open Source

alchemlyb extracts alchemical free energy data from molecular dynamics output and estimates free energies with MBAR, BAR and thermodynamic integration on the PyData stack.

Open sourcePython

Computational Chemistry · Drug Discovery · Scientific Data

Related guides

Overview

MCP vs Skills vs Agents vs APIs: What's the Difference?

Understand how APIs, MCP servers, Skills, and agents divide interface, procedural guidance, execution, and planning responsibilities in chemistry workflows—and how to choose or combine them without confusing access with scientific validity.

Skills

AI Skills for Chemistry: What They Are and How They Work

Understand chemistry AI Skills as reusable procedure modules: what SKILL.md contains, how hosts load instructions, how Skills differ from MCP and agents, and how to select, combine, and evaluate them without confusing guidance with scientific validation.

Overview

How to Build a Chemistry AI Agent Stack

Design a chemistry AI agent stack by separating language models, orchestration, Skills, MCP interfaces, APIs, libraries and data. Follow proposed molecular and materials workflows, define input/output contracts, and plan permissions, evaluation and reproducible deployment.