Provides 17 tools to monitor, diagnose, and manage Apache HTTP Server operations through diagnostics, log analysis, and health probes.
Also known as AIops-tools/Apache-AIops, apache-aiops
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- 332
- Latest version
- 0.2.2
- Last commit
- Nov 14, 2026
- License
- MIT
What is Apache HTTP Server AIops MCP?
Apache HTTP Server AIops provides 17 tools to monitor, diagnose, and manage Apache HTTP Server operations through diagnostics, log analysis, and health probes.
Summary generated from the project's README
About Apache HTTP Server AIops MCP server
Managing and diagnosing Apache HTTP Server operations becomes more structured through this MCP server which provides 17 specialized tools for system administrators and DevOps engineers. It integrates directly with the local apachectl utility to inspect configuration syntax, loaded modules, and virtual hosts. Users can also configure the server to monitor machine-readable mod_status metrics, perform bounded error log tailing, and review privacy-preserving access log summaries.
Setup requires Python 3.11+, uv, and the apachectl binary on the host machine. Operators configure specific targets in a YAML file, defining paths for error logs, access logs, and optional HTTP health or status URLs. The system includes a governance harness that audits and budgets every call to ensure controlled interaction with the server. While it supports graceful-reload via configtest, it does not currently handle vhost editing, TLS certificate management, or module changes.
What you can do with it
- 1Verify Apache configuration integrityAsk the AI to check the current Apache version, configuration syntax, and loaded modules to ensure the server is running correctly.
- 2Perform automated server diagnosticsRequest a comprehensive diagnostic report that correlates various checks and identifies unhealthy HTTP probes.
- 3Analyze server logs for errorsHave the AI examine a bounded portion of the error log to identify recent issues.
Written from the project's README. Every use case is checked against a quote from it.
How to install Apache HTTP Server AIops MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Apache HTTP Server AIops MCP in Claude Code
$ claude mcp add apache-aiops -- uvx apache-aiopsInstall Apache HTTP Server AIops MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"apache-aiops": {
"command": "uvx",
"args": [
"apache-aiops"
]
}
}
}Install Apache HTTP Server AIops MCP in VS Code
.vscode/mcp.json
{
"servers": {
"apache-aiops": {
"type": "stdio",
"command": "uvx",
"args": [
"apache-aiops"
]
}
}
}Install Apache HTTP Server AIops MCP in VS Code CLI
$ code --add-mcp '{"name":"apache-aiops","type":"stdio","command":"uvx","args":["apache-aiops"]}'Install Apache HTTP Server AIops MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"apache-aiops": {
"command": "uvx",
"args": [
"apache-aiops"
]
}
}
}Install Apache HTTP Server AIops MCP in Codex
$ codex mcp add apache-aiops -- uvx apache-aiopsInstall Apache HTTP Server AIops MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.apache-aiops] command = "uvx" args = ["apache-aiops"]
Install Apache HTTP Server AIops MCP in Gemini CLI
$ gemini mcp add -s user apache-aiops uvx -- apache-aiopsInstall Apache HTTP Server AIops MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"apache-aiops": {
"command": "uvx",
"args": [
"apache-aiops"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableaiops-tools/apache-aiops is public and reachablegithub.com/aiops-tools/apache-aiops ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Sigstore attestation for apache-aiopspypi.org/project/apache-aiops/ ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/aiops-tools/apache-aiops ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from apache-aiopsPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubApache 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_statusmetrics, bounded error-log tail and privacy-preserving access-status summary. - Optional HTTP health status without downloading the response body.
apache_diagnosecorrelates checks, preserves failed probes as errors withdata: null, and reports completed but unhealthy HTTP probes separately inunhealthyProbes. Itshealthyverdict istrue,falseornullwhen health was not established;completeonly means configured probes ran without errors.
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.
Apache HTTP Server AIops MCP questions
How do I add Apache HTTP Server AIops MCP to Claude Code?
Run claude mcp add apache-aiops -- uvx apache-aiops in your terminal. Add --scope user to make it available in every project.
How do I add Apache HTTP Server AIops MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can the server check regarding Apache configuration?
It can check the Apache version, configuration syntax, parsed virtual hosts, loaded modules, build options, and runtime configuration.
What are the system requirements for setup?
You need Python 3.11+, uv, and the apachectl binary installed on the host machine.