← Playbook index

Step 1 — Publish apertureapi-mcp to PyPI

Discovery plumbing (secondary). This page makes the service findable by someone already searching; it does not replace pipeline work (page 00). Do it once; no paid tier, listing or upgrade (hard rule 6).

Why first: the official MCP Registry entry (Step 2) points at a PyPI package; it is only submittable once that package actually exists.

What you are publishing: the already-built package at integrations/mcp/ in the ApertureAPI repository (version 0.1.0, hatchling build, console command apertureapi-mcp). You are not writing code — only building and uploading what exists.

Do this

  1. Create/confirm the PyPI account (operator supplies the company email). Enable 2FA (required by PyPI). Artifact: you can log in at pypi.org.
  2. Create an API token: pypi.org → Account settings → API tokens → "Add API token", scope "Entire account" for the first upload (narrow it to the project after it exists). Copy it once; it is shown once.
  3. On the build machine, from the repository root:
  4. cd integrations/mcp
  5. ../../.venv/bin/pip install -q build twine
  6. ../../.venv/bin/python -m build → produces dist/apertureapi_mcp-0.1.0.tar.gz and a .whl.
  7. ../../.venv/bin/python -m twine upload dist/* — username __token__, password = the API token.
  8. Verify: open https://pypi.org/project/apertureapi-mcp/ — page exists, version 0.1.0, README renders.
  9. Prove installability on any machine: pipx install apertureapi-mcp then apertureapi-mcp --help (or confirm the binary exists).

Artifact

Date Account Artifact URL Confirmed by

Buyer pages to pair with this page: workflow fit · methods supplement. Pipeline stages and KPIs: page 00.