Apache HTTP Server AIops

io.github.AIops-toolsPublished by GitHub account AIops-toolsv0.2.0Updated Nov 5, 2026

Governed Apache HTTP Server operations — 17 MCP tools with audit.

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that lets an assistant inspect and diagnose an Apache HTTP Server through apachectl, health probes and logs, with every call audited.

What you can do
  • Check version, config syntax, parsed virtual hosts, loaded and compiled modules, build options and the config include tree
  • Read runtime configuration and directives from static modules
  • Pull optional mod_status metrics, a bounded error-log tail and a privacy-preserving access-log status summary
  • Probe an operator-configured HTTP health URL without downloading the response body
  • Correlate all checks into one diagnosis that keeps failures as errors
  • Run a graceful reload that first tests the config and supports dry-run
When to use it
Useful when an assistant should help operate or troubleshoot an Apache HTTP Server on the same machine: checking configuration, modules, virtual hosts, status metrics and logs, or performing a guarded reload after a config change.
Requirements
Runs as a local stdio process on the user's machine (desktop only). Needs Python 3.11+, uv and apachectl on the host, plus a config file listing targets with apachectl path, optional probe and mod_status URLs, error and access log paths, timeout and TLS settings. No accounts, API keys or environment variables are declared.
Before you install
The graceful reload changes live server state: it runs configtest first and supports dry-run and two CLI confirmations, but the final outcome can be unknown and there is no safe inverse without a snapshot of the prior config. It reads local error and access logs, so log paths should be chosen carefully. Vhost editing, TLS certificate management and module changes are out of scope.

Installation

In SourceWeft

  1. Open Apache HTTP Server AIops in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

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.

Source: README.md at commit a0092fa

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

1
  1. v0.2.0LatestNov 5, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts