system-setup

Install and verify MCP runtime dependencies across Windows, Linux, and macOS.

8|3|Updated Jul 14, 2025
One-click install
npx skills add https://github.com/fritzprix/libr-agent --skill system-setup-fritzprix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-setup
Source: https://github.com/fritzprix/libr-agent/tree/main/.github/skills/system-setup
Command: npx skills add https://github.com/fritzprix/libr-agent --skill system-setup-fritzprix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the installation and verification of MCP runtime dependencies (Python, Node.js, uv) across Windows, Linux, and macOS, ensuring that MCP servers can run without manual setup.

Core Features & Use Cases

  • Automatic OS detection and platform-specific installers for Python, Node.js, and uv.
  • Unified verification step to confirm executables exist and meet minimum versions.
  • Use cases include setting up LibrAgent on a fresh machine, troubleshooting missing runtimes, and preparing environments for MCP servers.

Quick Start

  • Run the verification script: ./scripts/verify_setup.sh
  • Install missing components as needed:
    • Linux/macOS: ./scripts/install_python.sh; ./scripts/install_node.sh; ./scripts/install_uv.sh
    • Windows: use corresponding installers for Python, Node.js, and uv and verify with ./scripts/verify_setup.sh
  • Re-run verification after installations: ./scripts/verify_setup.sh
  • If PATH changes are required, restart the terminal or run source your shell RC file

Frequently Asked Questions about system-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install MCP runtime dependencies like Python and Node.js automatically?

To install MCP runtime dependencies automatically, you can use a skill that detects your OS and applies platform-specific installers for Python, Node.js, and uv. This ensures MCP servers run without manual setup across Windows, Linux, and macOS.

Why does my MCP server fail to start due to missing runtimes?

MCP servers fail due to missing runtimes when required executables like Python, Node.js, or uv are not installed or do not meet minimum version requirements. An automated environment readiness check can verify executable availability and install missing components.

Can I verify Python and Node.js versions for MCP servers across different operating systems?

Yes, you can verify Python and Node.js versions across different operating systems using a unified verification script. It confirms executable availability and checks that the installed runtimes meet the minimum version requirements for MCP servers.

What is the best way to prepare a new machine for running MCP servers?

The best way to prepare a new machine for running MCP servers is to automate the installation and verification of runtime dependencies. This process detects the OS, installs required components like Python, Node.js, and uv, and verifies their versions to ensure environment readiness.

How do I troubleshoot missing uv or Python executables when setting up MCP?

To troubleshoot missing uv or Python executables when setting up MCP, run a verification script to identify gaps, install the missing components using platform-specific installers, and restart your terminal to apply any required PATH changes.

Do I need to restart my terminal after installing MCP runtime components?

Yes, you need to restart your terminal or source your shell RC file after installing MCP runtime components if PATH changes are required. This ensures the newly installed executables for Python, Node.js, and uv are recognized by the system.