apolo-mcp 26.8.0__tar.gz

apolo_mcp-26.8.0/.github/dependabot.yml

@@ -0,0 +1,15 @@
+version: 2
+updates:
+  - package-ecosystem: uv
+    directory: /
+    schedule:
+      interval: daily
+      time: "03:00"
+    open-pull-requests-limit: 10
+    insecure-external-code-execution: allow
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: daily
+      time: "03:00"
+    open-pull-requests-limit: 10

apolo_mcp-26.8.0/.github/pull_request_template.md

@@ -0,0 +1,15 @@
+## Summary
+
+## Safety and context impact
+
+- [ ] No credential/private data is included.
+- [ ] Tool outputs are bounded and serializable.
+- [ ] Write annotations/policy/approval behavior is covered by tests, or not applicable.
+- [ ] Explicit context does not persist a context switch.
+
+## Validation
+
+- [ ] `make lint`
+- [ ] `make test`
+- [ ] `make build`
+- [ ] `CHANGELOG.md` and compatibility docs updated when applicable.

apolo_mcp-26.8.0/.github/workflows/ci.yaml

@@ -0,0 +1,81 @@
+name: CI
+
+on:
+  push:
+    branches: [master]
+    tags: ["v*"]
+  pull_request:
+    branches: [master]
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    name: All checks are passed
+    uses: ./.github/workflows/test.yaml
+    secrets: inherit
+
+  approve:
+    name: Approve Dependabot PR
+    runs-on: ubuntu-latest
+    if: github.event_name == 'pull_request' && github.actor == 'dependabot[bot]'
+    needs: test
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+      - name: Fetch Dependabot metadata
+        uses: dependabot/fetch-metadata@v3
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+      - name: Enable auto-merge for Dependabot PR
+        run: gh pr merge --auto --squash --delete-branch "$PR_URL"
+        env:
+          PR_URL: ${{ github.event.pull_request.html_url }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+  release-package:
+    name: Release apolo-mcp package
+    runs-on: ubuntu-latest
+    needs: test
+    environment: pypi
+    if: github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v')
+    permissions:
+      contents: write
+      id-token: write
+    steps:
+      - name: Checkout commit
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+      - name: Install uv
+        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        with:
+          version: "0.11.31"
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+      - name: Install project Python
+        run: uv python install
+      - name: Install dependencies
+        run: make setup
+      - name: Verify tag and changelog
+        shell: bash
+        run: |
+          [[ "${GITHUB_REF_NAME}" =~ ^v[0-9]{2}\.([1-9]|1[0-2])\.[0-9]+$ ]]
+          test "${GITHUB_REF_NAME}" = "v$(uv run python -c 'from apolo_mcp import __version__; print(__version__)')"
+          grep -F "## ${GITHUB_REF_NAME#v}" CHANGELOG.md
+          test -z "$(find CHANGELOG.D -type f ! -name .gitignore -print -quit)"
+      - name: Build apolo-mcp package
+        run: make build
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+      - name: Sign the distributions with Sigstore
+        uses: sigstore/gh-action-sigstore-python@v3.5.0
+        with:
+          inputs: >-
+            ./dist/*.tar.gz
+            ./dist/*.whl

apolo_mcp-26.8.0/.github/workflows/test.yaml

@@ -0,0 +1,97 @@
+name: Tests
+
+on:
+  workflow_call: {}
+
+jobs:
+  lint:
+    name: Linter
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+      - name: Install uv
+        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        with:
+          version: "0.11.31"
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+      - name: Install project Python
+        run: uv python install
+      - name: Cache pre-commit hooks
+        uses: actions/cache@v6
+        with:
+          path: ~/.cache/pre-commit
+          key: pre-commit|${{ runner.os }}|${{ hashFiles('.python-version', '.pre-commit-config.yaml') }}
+      - name: Install dependencies
+        run: make setup
+      - name: Run linters
+        run: make lint
+        env:
+          CI_LINT_RUN: 1
+
+  unit:
+    name: Unit tests (${{ matrix.os }}, Python ${{ matrix.python-version }})
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13", "3.14"]
+        os: [ubuntu, macos]
+    runs-on: ${{ matrix.os }}-latest
+    timeout-minutes: 15
+    steps:
+      - name: Checkout commit
+        uses: actions/checkout@v7
+      - name: Install uv and set Python version
+        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        with:
+          version: "0.11.31"
+          python-version: ${{ matrix.python-version }}
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+      - name: Install dependencies
+        run: make setup
+      - name: Run unit tests
+        run: make test PYTEST_ARGS="-vvv"
+        env:
+          COLOR: yes
+
+  build:
+    name: Build distributions
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - name: Checkout commit
+        uses: actions/checkout@v7
+      - name: Install uv
+        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
+        with:
+          version: "0.11.31"
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+      - name: Install project Python
+        run: uv python install
+      - name: Install dependencies
+        run: make setup
+      - name: Build package
+        run: make build
+
+  check:
+    # This job does nothing and is only used for branch protection.
+    name: Check
+    needs: [lint, unit, build]
+    if: ${{ always() }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check
+        if: ${{ needs.lint.result != 'success' || needs.unit.result != 'success' || needs.build.result != 'success' }}
+        run: |
+          echo "lint result: ${{ needs.lint.result }}"
+          echo "unit result: ${{ needs.unit.result }}"
+          echo "build result: ${{ needs.build.result }}"
+          exit 1
+      - name: Success
+        run: echo "All checks have passed"

apolo_mcp-26.8.0/.gitignore

@@ -0,0 +1,15 @@
+src/apolo_mcp/_version.py
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+*.whl
+*.tar.gz
+.mypy_cache/
+.pytest_cache/
+.venv/
+venv/
+*.egg
+.coverage
+coverage.xml

apolo_mcp-26.8.0/.pre-commit-config.yaml

@@ -0,0 +1,34 @@
+# Adapted from neuro-inc/app-types at 44d287f4216b87e0aacd3913aa1a611845875412.
+ci:
+  # pre-commit.ci does not install the project's uv environment. The GitHub Actions
+  # lint job runs this hook after `make setup` and remains the docs-drift gate.
+  skip: [generate-mcp-docs]
+
+exclude: ^uv\.lock$
+repos:
+  - repo: local
+    hooks:
+      - id: generate-mcp-docs
+        name: Generate MCP docs
+        language: system
+        entry: make docs
+        pass_filenames: false
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: check-added-large-files
+      - id: check-merge-conflict
+      - id: check-toml
+      - id: check-yaml
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.9.9
+    hooks:
+      - id: ruff
+        args: [--fix, --exit-non-zero-on-fix]
+      - id: ruff-format
+  - repo: https://github.com/twisted/towncrier
+    rev: 25.8.0
+    hooks:
+      - id: towncrier-check

apolo_mcp-26.8.0/.python-version

@@ -0,0 +1 @@
+3.12

apolo_mcp-26.8.0/AGENTS.md

@@ -0,0 +1,133 @@
+# AGENTS.md
+
+## Overview
+
+**`apolo-mcp`** is an MCP (Model Context Protocol) server that gives AI agents the ability to work with the [Apolo platform](https://apolo.us) — running training jobs, deploying long-lived applications, and managing artifacts in storage.
+
+It is a thin adapter layer over `apolo-sdk`. It does **not** shell out to the `apolo` CLI.
+
+## Architecture Decisions
+
+- **Separate package** from `apolo-cli`/`apolo-sdk` to avoid MCP deps polluting the SDK.
+- **Uses `apolo-sdk` directly** (not the CLI subprocess) for structured errors and typed responses.
+- **Auth via Apolo configuration** — local use normally reads `~/.apolo/` after
+  `apolo login`; isolated jobs may use `APOLO_PASSED_CONFIG`. No tool accepts a token.
+- **`apolo_sdk.get()`** is the entry point: an async context manager yielding `Client`.
+- **`MCPServer`** from the `mcp` package for tool registration and server lifecycle.
+
+## Workload boundary
+
+- Use **jobs** for bounded R&D, experiments, builds, migrations, batch work, and tests.
+- Use **Apps** for long-running deployments and managed services, including databases,
+  APIs, and web UIs. Do not emulate a deployment by keeping a job alive.
+- A remote image builder may run as a job because the build is bounded; deploy the
+  resulting image through an App template such as Service Deployment.
+
+## Tool Surface
+
+`src/apolo_mcp/catalog.py` is the canonical ordered catalog for capability groups,
+runtime registration, documentation descriptions, and owning skills. Registered
+MCPServer metadata remains canonical for individual tool schemas and operation types. It
+generates the complete [tool reference](docs/capabilities/tools/README.md); do not
+maintain a duplicate tool table here.
+
+## Package Structure
+
+```
+src/apolo_mcp/
+  cli.py         — server and packaged-skill command-line interface
+  catalog.py     — declarative capability and skill ownership catalog
+  server.py      — MCPServer app and stdio server lifecycle
+  skill_installer.py — packaged skill installation implementation
+  _client.py     — apolo_sdk.get() context manager helper
+  workspace.py   — server-controlled local filesystem confinement
+  tools/         — registered capability modules; see catalog.py
+```
+
+## Tooling
+
+- **uv** for all dependency management, building, and publishing — no pip/setuptools/twine.
+- `pyproject.toml` is the single config source (no `setup.cfg` / `setup.py`).
+- `uv.lock` is committed for reproducible installs.
+- Build backend: **hatchling**.
+
+## Documentation Contract
+
+- Maintain exactly one authoritative source for each fact, interface, or workflow.
+  Prefer generating documentation from executable code and structured metadata. When
+  generation is impractical, designate one maintained canonical Markdown page. Every
+  other README, guide, skill reference, or example must link to that source instead of
+  copying its tables, commands, configuration blocks, or normative prose.
+- The current source-ownership map is:
+
+  | Subject | Authoritative source | Published documentation |
+  |---|---|---|
+  | Capability order, descriptions, runtime registration, and skill ownership | `src/apolo_mcp/catalog.py` | generated tool navigation, skills catalog, and safety sections |
+  | MCP tool names, schemas, annotations, and operation types | registered MCPServer metadata in `src/apolo_mcp/tools/` | generated `docs/capabilities/tools/` and generated sections of the safety model |
+  | Policy modes and lifecycle journal behavior | `src/apolo_mcp/policy.py`, `src/apolo_mcp/ledger.py`, and `build-tools/docs-templates/safety.md` | generated `docs/getting-started/safety.md` |
+  | Canonical skill names and summaries | `src/apolo_mcp/catalog.py`, skill frontmatter, and `agents/openai.yaml` | generated `docs/capabilities/skills.md` |
+  | Complete skill instructions and supporting references | `skills/*/SKILL.md` and `skills/*/references/` | generated `docs/capabilities/skills/*/` |
+  | Installation, client registration, policy forwarding, startup-directory confinement, and skill installation | `build-tools/docs-templates/installation.md` | generated `docs/getting-started/installation.md` |
+  | Full-mode dedicated-service-account workflow | `build-tools/docs-templates/full-mode-service-account.md` | generated `docs/guides/full-mode-service-account.md` |
+  | Self-contained R&D runtime and isolated-job configuration | `build-tools/docs-templates/rnd-runtime.md` | embedded unchanged in the generated full-mode guide and packaged R&D skill reference |
+  | Supported, unsupported, and CLI-fallback capabilities | `docs/capabilities/README.md` | the same canonical maintained page |
+
+- Treat MCP code, registered tool metadata, policy constants, and canonical skill
+  metadata as documentation inputs. Any change to a tool name, description, schema,
+  annotation, safety behavior, policy, skill, supported capability, or CLI fallback
+  must include the corresponding documentation update in the same change.
+- Edit maintained prose under `docs/` and generator templates under
+  `build-tools/docs-templates/`. Never edit generated files under
+  `docs/capabilities/tools/`, `docs/capabilities/skills.md`,
+  `docs/capabilities/skills/`, or
+  `docs/getting-started/installation.md`, `docs/getting-started/safety.md`,
+  `docs/guides/full-mode-service-account.md`, or the packaged R&D skill's generated
+  `references/installation.md` directly.
+- Run `make docs` after relevant code or skill changes, commit the generated Markdown,
+  then run `make docs-check` and pre-commit. Generation must not modify GitBook-owned
+  navigation such as `docs/SUMMARY.md`.
+- Do not create a second installation or client-configuration guide. The canonical
+  `build-tools/docs-templates/installation.md` owns all install commands and
+  configuration snippets. Generated and maintained pages should link to the published
+  `docs/getting-started/installation.md`.
+- Keep `docs/capabilities/README.md` current and use complete executable CLI commands,
+  including the `apolo` or `apolo-flow` entry point. Do not use internal shorthand such
+  as `job/root`.
+
+## Development Commands
+
+```bash
+make setup       # uv sync --all-groups + pre-commit install
+make format      # pre-commit run --all-files
+make lint        # format + mypy
+make test        # pytest unit tests
+make build       # uv build (sdist + wheel into dist/)
+make docs        # regenerate code-derived documentation
+make docs-check  # verify committed generated documentation is current
+make publish     # uv publish (set UV_PUBLISH_TOKEN)
+```
+
+## Running the Server
+
+```bash
+# stdio (default for Claude Desktop / Claude Code MCP config)
+python -m apolo_mcp
+
+# or via installed entry point
+apolo-mcp
+```
+
+## Client configuration
+
+Do not duplicate Codex or Claude Code setup here. Use the
+[installation and client configuration](docs/getting-started/installation.md).
+
+## Key Conventions
+
+- Storage paths: accept `apolo://...` URIs or bare paths like `/my/dir` (resolved against the current cluster/org/project from config).
+- Centralize all local path confinement in `src/apolo_mcp/workspace.py`; document its
+  behavior only in `build-tools/docs-templates/safety.md`.
+- All tools return plain dicts or strings — no SDK objects cross the boundary.
+- Async tools throughout; MCPServer handles the event loop.
+- Python ≥ 3.11 (matches `apolo-sdk` minimum).
+- Ruff owns formatting and import sorting; `apolo_mcp` is the configured first-party package.

apolo_mcp-26.8.0/CHANGELOG.D/.gitignore

@@ -0,0 +1 @@
+!.gitignore

apolo_mcp-26.8.0/CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+
+All notable changes are documented here. Releases use `YY.MM.NN`, where `YY` is the
+two-digit year, `MM` is the month without a leading zero, and `NN` is the zero-based
+release sequence within that month.
+
+[comment]: # (towncrier release notes start)
+
+## 26.8.0 (2026-08-03)
+
+### Features
+
+- Establish the standalone MCP server with typed Apolo tools, explicit context, released
+  Flow integration, protected credential sinks, operational skills, code-derived docs,
+  packaged Codex and Claude Code skill installation, a declarative capability catalog,
+  and calendar-based release tooling. ([#1](https://github.com/neuro-inc/apolo-mcp/issues/1))

apolo_mcp-26.8.0/CONTRIBUTING.md

@@ -0,0 +1,21 @@
+# Contributing
+
+Use Python 3.11+ and `uv`. Create a focused branch, add tests for every tool/schema or
+policy change, and run:
+
+```console
+make setup
+make lint
+make test
+make build
+```
+
+Never put credentials or private platform data in fixtures, recordings, logs, or pull
+requests. Tool results must be serializable and bounded. Write tools need accurate MCP
+annotations, explicit resolved context, unit tests, and server-policy enforcement where
+high risk. Interactive or high-bandwidth behavior belongs in a documented CLI workflow,
+not an unbounded MCP response.
+
+Add a `CHANGELOG.D/<issue>.feature`, `.bugfix`, `.doc`, `.removal`, or `.misc`
+fragment for each user-visible change. Maintainers assemble fragments with
+`make changelog VERSION=<version>` through the protected release workflow.

apolo_mcp-26.8.0/LICENSE

@@ -0,0 +1,17 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        https://www.apache.org/licenses/
+
+   Copyright 2026 Apolo
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       https://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

apolo_mcp-26.8.0/Makefile

@@ -0,0 +1,60 @@
+SHELL := /bin/bash
+
+PYTEST_ARGS=
+
+.PHONY: help
+.SILENT: help
+help:
+	@grep -hE '^[a-zA-Z_-]+:[^#]*?### .*$$' $(MAKEFILE_LIST) | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}'
+
+.PHONY: setup
+setup: ### Install dev dependencies and pre-commit hooks
+	uv sync --locked --all-groups
+	uv run pre-commit install
+
+.PHONY: format fmt
+format fmt: ### Reformat source files
+ifdef CI_LINT_RUN
+	uv run pre-commit run --all-files --show-diff-on-failure
+else
+	uv run pre-commit run --all-files || uv run pre-commit run --all-files
+endif
+
+.PHONY: lint
+lint: format ### Reformat, lint, and type-check
+	uv run mypy src/ --show-error-codes
+
+.PHONY: test
+test: ### Run unit tests
+	uv run pytest $(PYTEST_ARGS) tests/
+
+.PHONY: build
+build: ### Build sdist and wheel
+	uv build
+
+.PHONY: docs
+docs: ### Regenerate code-derived documentation
+	uv run python build-tools/generate-docs.py
+
+.PHONY: docs-check
+docs-check: ### Verify code-derived documentation is current
+	uv run python build-tools/generate-docs.py --check
+
+.PHONY: changelog
+changelog: ### Build the changelog for calendar VERSION (for example, VERSION=26.7.0)
+	test -n "$(VERSION)"
+	uv run towncrier build --yes --version "$(VERSION)"
+
+.PHONY: publish
+publish: ### Publish to PyPI (set UV_PUBLISH_TOKEN env var)
+	uv publish
+
+.PHONY: run
+run: ### Run the MCP server (stdio transport)
+	uv run python -m apolo_mcp
+
+.PHONY: clean
+clean: ### Remove build artifacts
+	find . -name '*.egg-info' -exec rm -rf {} +
+	find . -name '__pycache__' -exec rm -rf {} +
+	rm -rf .mypy_cache dist build

apolo_mcp-26.8.0/PKG-INFO

@@ -0,0 +1,108 @@
+Metadata-Version: 2.4
+Name: apolo-mcp
+Version: 26.8.0
+Summary: MCP server for the Apolo platform
+Project-URL: Homepage, https://github.com/neuro-inc/apolo-mcp
+Project-URL: Documentation, https://github.com/neuro-inc/apolo-mcp/tree/master/docs
+Project-URL: Repository, https://github.com/neuro-inc/apolo-mcp
+Project-URL: Issues, https://github.com/neuro-inc/apolo-mcp/issues
+Author-email: Apolo Team <dev@apolo.us>
+License:                                  Apache License
+                                   Version 2.0, January 2004
+                                https://www.apache.org/licenses/
+        
+           Copyright 2026 Apolo
+        
+           Licensed under the Apache License, Version 2.0 (the "License");
+           you may not use this file except in compliance with the License.
+           You may obtain a copy of the License at
+        
+               https://www.apache.org/licenses/LICENSE-2.0
+        
+           Unless required by applicable law or agreed to in writing, software
+           distributed under the License is distributed on an "AS IS" BASIS,
+           WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+           See the License for the specific language governing permissions and
+           limitations under the License.
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.11
+Requires-Dist: apolo-flow>=26.7.2
+Requires-Dist: apolo-sdk>=26.7.2
+Requires-Dist: async-timeout>=5
+Requires-Dist: jsonschema<5,>=4.23
+Requires-Dist: mcp<3,>=2.0.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: tomlkit<1,>=0.13
+Description-Content-Type: text/markdown
+
+# apolo-mcp
+
+`apolo-mcp` is a local stdio Model Context Protocol server for typed Apolo platform
+operations. It is a thin adapter over `apolo-sdk`: it never shells out to the CLI and
+uses the configured Apolo identity, permissions, and defaults. Local sessions normally
+come from `apolo login`; isolated jobs may use `APOLO_PASSED_CONFIG`.
+
+The server exposes bounded context discovery and typed platform operations. Every
+operational tool accepts explicit `cluster`, `org`, and `project` inputs where the
+SDK supports them; explicit inputs never modify the user's saved context. Secret
+values and one-time credentials are intentionally outside the model-visible interface.
+
+## Installation
+
+Follow the
+[installation and client configuration guide](docs/getting-started/installation.md)
+for prerequisites, server and skill installation, Codex and Claude Code registration,
+per-session policy selection, and verification. Local stdio is the only supported
+transport; shared-credential remote service operation is unsupported.
+
+See the [Apolo MCP documentation](docs/README.md) for prerequisites, safety controls,
+the capability matrix, generated tools and skills catalogs, and task-oriented guides.
+
+## Development
+
+```console
+make setup
+make lint
+make test
+make build
+```
+
+Dependencies are locked with `uv.lock`. Tests use an `ApoloClientProvider` fake and do
+not require credentials. Integration tests, when added, must be opt-in and target an
+isolated non-production project.
+
+Wheel and source-distribution files are generated release artifacts and must not be
+committed. Tagged releases build them in CI and publish the exact outputs to PyPI via
+Trusted Publishing; local `dist/` contents are disposable. Maintainers should follow
+[RELEASE.md](RELEASE.md) for changelog, validation, signing, and publication.
+
+Release versions use `YY.MM.NN`: the two-digit year, the month without a leading zero,
+and a zero-based release sequence within that month. For example, `v26.7.0` is the
+first July 2026 release, and its Python package version is `26.7.0`.
+
+## Safety configuration
+
+The server defaults to `APOLO_MCP_POLICY_MODE=read-only`. Use `managed` to create
+resources and manage only their exact journaled lifecycles, or `full` to permit
+mutations of any exact-context resource. Policy never grants Apolo permissions or
+replaces Apolo RBAC, and it is not a security boundary against an agent with direct
+CLI or SDK access. **Never run `full` with a personal administrator, owner, or other
+broadly privileged Apolo account.** Use a dedicated least-privileged service account
+and follow the [full-mode service-account guide](docs/guides/full-mode-service-account.md).
+Select policy per launch rather than permanently storing `managed` or `full`; the
+installation guide contains the client-specific configuration. Read the generated
+[safety model](docs/getting-started/safety.md) before enabling writes, and consult the
+[capability matrix](docs/capabilities/) for the complete current contract.
+
+Licensed under Apache-2.0. See [SECURITY.md](SECURITY.md) for private reporting.