paftacular
A Python library for parsing and serializing mzPAF (Peak Annotation Format), a standardized format for annotating mass spectrometry fragment ions in peptide/proteomics analysis. mzPAF is a specification from the Proteomics Standards Initiative (PSI) that provides a compact, human-readable notation for describing fragment ion types, chemical modifications, charge states, mass errors, and confidence scores.
Features
- mzPAF parsing: Handles parsing / serializing of mzPAF strings
- Properties: Supports calculating mass and composition of annotated ions
- Type annotations: Includes a
py.typedmarker for static type checking - Caching: repeated modifier and selected ion components share bounded instance caches
- Peptacular: Optionally integrated with peptacular to enable parsing of included sequences and generation of mzPAF annotations
Installation
pip install paftacular
pip install paftacular[peptacular] # with peptacular integration
pip install paftacular[smiles] # with SMILES support
pip install paftacular[all] # with all optional dependencies
Quick Start
AI clients through MCP
Install with pip install 'paftacular[mcp]', then configure your MCP
client to launch paftacular-mcp. The server provides nine tools for parsing,
construction, sequence resolution, calculations, fragment generation, and m/z
matching, plus scientific reference resources and analysis prompts.
The mcp extra includes peptide support. Use paftacular[mcp,smiles] for SMILES as well.
The base library needs no MCP dependencies. The all extra now includes MCP.
See the MCP guide for configuration and examples.
Python API
There are 3 parsing methods available:
parse: Parses a single or multiple comma-separated mzPAF annotations. Returns a singlePafAnnotationor a list of them.parse_multi: Parses multiple comma-separated mzPAF annotations. Always returns a list ofPafAnnotation.parse_single: Parses a single mzPAF annotation. Returns a singlePafAnnotation. Raises ValueError if multiple annotations are provided.
import paftacular as pft
# Parse a simple peptide ion
ann = pft.parse("y5")
print(ann.ion_type.series) # y
print(ann.ion_type.position) # 5
# Calculate masses
print(ann.mass()) # Ion offset only, because y5 has no sequence context
print(ann.serialize()) # Round-trip back to string
# Parse multiple ions
anns = pft.parse("y5-H2O^2/1.2ppm*0.95,b3^2")
for ann in anns:
print(ann.charge)
print(ann.mass_error.value if ann.mass_error else None)
print(ann.confidence)
Resolve peptide context
With paftacular[peptacular] installed, resolve a fragment against a full ProForma analyte before calculating its complete mass:
import paftacular as pft
ann = pft.parse_single("y2").resolve("PEPTIDE")
print(ann.sequence) # DE
print(ann.mz())
Without an embedded or resolved sequence, peptide and precursor calculations return only the ion offset and modifiers. Resolved context is preserved by to_dict(), while mzPAF serialization preserves the original annotation text structure.
Batch parsing and interchange
import json
import paftacular as pft
for result in pft.iter_parse(["y2,b3", "invalid", "p^2"]):
if result.ok:
print(result.index, len(result.annotations))
else:
print(result.index, result.error.position, result.error.reason)
ann = pft.parse_single("y2/0.000001ppm")
restored = pft.PafAnnotation.from_dict(json.loads(json.dumps(ann.to_dict())))
assert restored == ann
to_dict() produces versioned component data. The existing as_dict() remains a compact display representation.
Documentation
Full documentation is available at Read the Docs.
Citation
If you use paftacular in research, cite the archived software release. Machine-readable citation metadata is available in CITATION.cff; GitHub's Cite this repository menu can render it as APA or BibTeX. The stable DOI for all versions is 10.5281/zenodo.19076277; individual releases also receive version-specific DOIs from Zenodo.
mzPAF Format
The mzPAF format uses compact notation:
[&][analyte@]ion_type[modifications][^charge][/mass_error][*confidence]
Examples: y5, b2{PEP}, y5-H2O^2, y5/1.2ppm*0.95
See the PSI mzPAF specification for full details.
License
paftacular is distributed under the MIT License. The bundled mzPAF specification remains under its own PSI copyright and distribution terms; see third-party notices.
Contributing
See CONTRIBUTING.md for development setup, issue reporting, support, and pull-request guidance. Project governance is described in GOVERNANCE.md, and security reports are handled according to SECURITY.md.
Author: Patrick Garrett (pgarrett@scripps.edu)
Release files for paftacular 1.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| paftacular-1.3.1.tar.gz | 772.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| paftacular-1.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 819.1 kB
Release files / paftacular-1.3.1.tar.gz
| Download URL | paftacular-1.3.1.tar.gz |
|---|---|
| Size | 772.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2cc043087baf050487074f5d5863dcc14ca75cd9169dc271d0d9eb0f763f17d4
|
|
BLAKE2b-256 checksum How to use checksums |
c79995d01fd99c6dc423800c6777c0b48758c05cb8be8edd8cfa2cf0fa7a305e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 23, 2026.
Transparency logRelease files / paftacular-1.3.1-py3-none-any.whl
| Download URL | paftacular-1.3.1-py3-none-any.whl |
|---|---|
| Size | 46.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f768a2654843528f914fe069603304e93930e3aad27013aef177c8c3ac730bd2
|
|
BLAKE2b-256 checksum How to use checksums |
7a71a98c32c193c328b42113043fff1c87705b3f61ea2888445ee67e3baa1bc6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 23, 2026.
Transparency log