Arch Mcp

Created By
nihalxkumar7 months ago
Arch MCP provides three main capabilities: - 🔍 Resources - URI-based access to Arch Wiki, AUR packages, official repos, and installed packages - 🛠️ Tools - Search, analyze, and securely install packages with built-in safety checks - 📋 Prompts - Guided workflows for troubleshooting, security audits, and dependency analysis
Overview

What is Arch MCP?

Arch MCP is a Model Context Protocol (MCP) server that connects AI assistants with the Arch Linux ecosystem, providing intelligent access to Arch Wiki, AUR packages, and official repositories for enhanced Arch Linux usage.

How to use Arch MCP?

To use Arch MCP, install it using the command uvx arch-ops-server, and configure it with your MCP client to start accessing Arch resources and tools.

Key features of Arch MCP?

  • URI-based access to Arch Wiki, AUR, and official repositories.
  • Tools for searching, analyzing, and securely installing packages with safety checks.
  • Guided workflows for troubleshooting, security audits, and dependency analysis.

Use cases of Arch MCP?

  1. Quickly access Arch Wiki documentation for troubleshooting.
  2. Securely install packages with built-in safety checks.
  3. Conduct security audits on AUR packages before installation.

FAQ from Arch MCP?

  • Is Arch MCP affiliated with Arch Linux?

No, Arch MCP is an unofficial community project.

  • What are the prerequisites for installation?

You need Python 3.11+ and the uv package.

  • Can I contribute to Arch MCP?

Yes! Contributions are welcome, and you can submit pull requests or open issues.

Server Config

{
  "mcpServers": {
    "arch-ops": {
      "command": "uvx",
      "args": [
        "arch-ops-server"
      ]
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
nihalxkumar
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago