Skip to main content

Apache AIops

A dedicated, governed MCP server, CLI and skill for Apache HTTP Server with 17 MCP tools. It uses Apache's own apachectl diagnostics, optional operator-configured HTTP health and mod_status URLs, and bounded reads of an operator-configured error log plus a privacy-preserving access-log status summary. Every call is audited and budgeted by the vendored governance harness.

What it checks

  • Apache version, config syntax, parsed virtual hosts and loaded modules.
  • Build options and parsed runtime configuration.
  • Parsed config include tree, compiled modules and directives from static modules.
  • Optional machine-readable mod_status metrics, bounded error-log tail and privacy-preserving access-status summary.
  • Optional HTTP health status without downloading the response body.
  • apache_diagnose correlates the checks and preserves failures as errors with data: null.

Setup from source

Requires Python 3.11+, uv, and apachectl on the operator host. Run uv sync --dev, uv run apache-aiops init, then uv run apache-aiops doctor. Manual ~/.apache-aiops/config.yaml:

targets:
  - name: local
    apachectl_bin: apachectl
    probe_url: http://127.0.0.1/health
    status_url: http://127.0.0.1/server-status?auto
    error_log: /var/log/apache2/error.log
    access_log: /var/log/apache2/access.log
    timeout: 10
    verify_ssl: true

Run uv run apache-aiops diagnose. The MCP entry point is uv run apache-aiops-mcp. The optional HTTP probe is configured by the operator, not chosen by a tool caller. TLS verification is enabled by default, and ca_file accepts a custom CA PEM.

Scope and verification

graceful-reload first runs configtest, supports dry-run and two CLI confirmations, and reports an unknown final outcome even if the command returned: existing workers may still serve the old config. It has no safe inverse when the prior config file is not snapshotted. Vhost editing, TLS certificate management and module changes remain outside this release. See verification. Missing operations and live-environment feedback are welcome as issues or PRs.

Metadata

Release files for apache-aiops 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for apache-aiops 0.2.0
File Size Uploaded Provenance Actions
apache_aiops-0.2.0.tar.gz 69.0 kB With provenance Details for apache_aiops-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for apache-aiops 0.2.0
File Interpreter ABI Platform Actions
apache_aiops-0.2.0-py3-none-any.whl Python 3 none any Details for apache_aiops-0.2.0-py3-none-any.whl

Total release size: 123.8 kB

Release files / apache_aiops-0.2.0.tar.gz

Download URL apache_aiops-0.2.0.tar.gz
Size 69.0 kB
Tags Source
SHA-256 checksum
How to use checksums
bd647375439f34462c23a2a857042d21efdb8ba200ad2782ced0088bfad92e1e
BLAKE2b-256 checksum
How to use checksums
7de44b370019f692f6dfe4e762ca30b13898d3631c3b9d00cf6531033cc90c1b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 5, 2026.

Transparency log

Release files / apache_aiops-0.2.0-py3-none-any.whl

Download URL apache_aiops-0.2.0-py3-none-any.whl
Size 54.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d780361ab5c173ba751503dbc1199ead234bcfd6f6c5c1ed13539b7305b94641
BLAKE2b-256 checksum
How to use checksums
b12bc3484fc47a237d44f4d357ec0554e63e7faa6e3fb8594fe840b649cafa44
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 5, 2026.

Transparency log

Security for apache-aiops 0.2.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for apache_aiops-0.2.0.tar.gz

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 Nov 5, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page