arch

This MCP server exposes Arch Linux data and tooling to AI assistants, enabling safe and structured access to the Arch Wiki, AUR, and official repositories. It provides a suite of URI schemes for direct information retrieval, plus executable tools for package search, installation, verification, and maintenance. You can query Arch Wiki pages, fetch official package details, view AUR metadata, inspect pacman-related data, and perform system monitoring and log retrieval through the exposed functions. The server is designed so AI agents can generate digestible, actionable responses with follow-up prompts that guide users through installations, updates, and system checks on Arch Linux systems (and non-Arch hosts via remote access).

Usage focuses on the available executable tools and the URI-based access patterns: you can use the archwiki, archrepo, aur, pacman, system, archnews, and config URI schemes to fetch targeted information; and you can call tools like search_archwiki, search_aur, get_official_package_info, check_updates_dry_run, install_package_secure, remove_packages, manage_orphans, verify_package_integrity, manage_install_reason, query_file_ownership, list_package_groups, and list_group_packages to perform common maintenance and retrieval tasks. The server bridges these capabilities to the AI environment so responses can include structured data ready for follow-up actions (e.g., installing a package, updating mirrors, or inspecting a package’s PKGBUILD).

Prerequisites:\n- Python 3.8+ and pip installed on the host system.\n- Access to the internet to fetch the Python package.\n\nStep-by-step installation:\n1) Create and activate a virtual environment (optional but recommended):\n python -m venv venv\n source venv/bin/activate # On Windows use: venv\Scripts\activate.bat\n\n2) Install the Arch MCP server package from PyPI:\n pip install arch-ops-server\n\n3) Run the MCP server (as a module):\n python -m arch_ops_server\n\n4) Verify the server starts and is reachable. By default it should listen on the configured port (check console output). If you need to customize configuration, provide environment variables or config files as per the package documentation.\n\nOptional: If you manage multiple environments, consider running in a container or using a process manager to keep the MCP server alive (e.g., systemd, PM2, or Docker).

Notes and tips:\n- This MCP server relies on the arch-ops-server package to expose Arch Linux data via MCP-compatible endpoints. Ensure you have network access to fetch Arch Wiki data, AUR metadata, and pacman-related information.\n- If you run behind a proxy, configure Python's proxy settings or your environment to allow outbound HTTP(S) requests.\n- For safety and stability, use the provided tools (e.g., check_updates_dry_run before applying updates, verify_package_integrity before package changes) to minimize unintended system changes.\n- Review URI schemes in the README (archwiki://, archrepo://, aur://, pacman://, system://, archnews://, config://) to leverage direct data access in your AI workflows.\n- When deploying in production or on non-Arch hosts, consider restricting the exposed endpoints and enabling authentication as appropriate for your MCP setup.