Skip to main content

Quick Diagnostics

Run these commands to quickly diagnose issues:
Verify all components are installed correctly:
Expected: All version commands return valid versions, server responds with tools list

Verify Installation

After installing and configuring the Arch MCP Server:
1

Check client settings

Go to settings tab and look for MCP tools icon in your client.
Location varies by client:
  • Claude Desktop: Settings → Features → Model Context Protocol
  • Cursor: Settings → MCP Servers
  • VS Code: MCP extension sidebar
2

Find arch-ops server

You should see “arch-ops” listed as a connected MCP server.
Status should be: Connected (green indicator)
If status shows “Disconnected” (red), see troubleshooting below.
3

Test a simple query

Try a basic query to verify the server responds:
Expected: Results from Arch Wiki with titles and links
4

Test a tool

Try a specific tool to verify functionality:
Expected: List of AUR packages with vote counts

Common Installation Issues

  1. Verify uvx is installed: uvx --version
  2. Check Python version: python --version (need 3.11+)
  3. Reinstall: uvx --reinstall arch-ops-server
  4. Restart your MCP client
  1. Check config file has valid JSON (no trailing commas)
  2. Verify file location is correct for your client
  3. Completely quit and restart the client (not just reload)

Server Won’t Start

Error: command not found: uvx or permission errorsDiagnosis:
Solutions:
  1. Install uv/uvx:
  2. Add to PATH:
  3. Verify installation:
The uv installer automatically adds to PATH, but you may need to restart your terminal.
Error: Python 3.11+ requiredCheck current version:
Install Python 3.11+:
Force specific Python version:
Error: ModuleNotFoundError or package installation failsCommon missing modules:
  • httpx - HTTP client library
  • beautifulsoup4 - HTML parsing
  • markdownify - HTML to Markdown conversion
  • mcp - MCP SDK
Solutions:
  1. Reinstall completely:
  2. Upgrade to latest version:
  3. Clear uv cache:
  4. Manual installation:
If issues persist, check if you have conflicting Python package managers (pip, conda, pipx).
Error: Server shows in tools but says “disconnected”Diagnosis steps:
  1. Test server directly:
  2. Check client logs:
  3. Verify configuration:
Common causes:
  • Syntax error in config file
  • Wrong command path in config
  • Server crashes on startup
  • Permission issues
Solutions:
  • Fix JSON syntax errors (trailing commas, quotes)
  • Use full path: "/usr/local/bin/uvx" instead of "uvx"
  • Restart client completely (quit and relaunch)
  • Check client logs for specific error messages
Expected log output: "arch-ops server connected successfully"

Tools Return Errors

Error: command 'checkupdates' not foundSolution: This is Arch-only and requires pacman-contrib:
On non-Arch systems, this tool is not available.
Error: TimeoutError or request timed outSolution:
  1. Check internet connection: ping google.com
  2. Try a simpler query first
  3. Verify Arch Wiki and AUR are accessible:
    • Wiki: xh https://wiki.archlinux.org/api.php
    • AUR: xh https://aur.archlinux.org/rpc
  4. Increase timeout if needed (requires code change)
Error: AUR package not found or HTTP 404Solution:
  1. Double-check package name spelling
  2. Try searching instead: Search AUR for 'package-name'
  3. The AUR might be temporarily down (rare)
  4. Try again in a few minutes
Error: Too many requests or HTTP 429Solution:
  • AUR has rate limiting
  • Wait a few minutes before retrying
  • Don’t spam requests
  • Share your use case (it’s reasonable)

Platform-Specific Issues

On Non-Arch Systems

On Arch Linux

All features available. If something isn’t working:
  1. Check system is updated: sudo pacman -Syu
  2. Verify dependencies: which pacman checkupdates yay paru
  3. Test locally: pacman -Si python (should work)

Configuration Issues

Error: JSON parse error or invalid configurationSolution:
  1. Validate JSON: Use jq or an online JSON validator
  2. Check for trailing commas
  3. Ensure proper JSON formatting
  4. Example valid config:
Error: MCP server doesn’t appear in clientSolution:
  1. Restart your MCP client completely
  2. Check config file location:
    • Claude: ~/.config/Claude/claude_desktop_config.json
    • Cursor: ~/.cursor/mcp_config.json
  3. Verify file has valid JSON
  4. Clear client cache if available

Getting Help

Debug Commands

Resources

  • Arch Wiki Issues: Check Arch Wiki
  • AUR Issues: Check AUR
  • MCP Protocol: Review MCP Docs
  • Bug Reports: Open an issue on GitHub
  • Feature Requests: GitHub discussions

Still stuck? Check the server logs, verify your config is correct, and ensure all prerequisites are installed.