convez.ai
MCP ServerDevOps & InfraestruturaIntermediário
learnrudi

RUDI CLI - Gestor Universal de Ferramentas

learnrudi/cli

Gerenciador universal de MCP stacks, ferramentas CLI e runtimes

Ver no GitHub
InicialPluginScore · de 0 a 100

Ferramenta de linha de comando para instalação e gerenciamento unificado de MCP stacks, CLI tools, runtimes e AI agents. Oferece arquitetura baseada em shims, suporte a múltiplas fontes de pacotes (npm, registro curado, binários upstream) e gerenciamento seguro de secrets com injeção de variáveis de ambiente.

Instalação

$npx convez-ai learnrudi/cli

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
62%
Último commit
há 3 semanas
Versão
—
Issues abertas
13
Contribuidores
1

Casos de uso

  • Instalar e gerenciar MCP servers para Claude, Codex e Gemini de forma centralizada
  • Manter múltiplas versões de ferramentas CLI isoladas sem conflitos de PATH
  • Integrar stacks com AI agents através de configuração automatizada
  • Gerenciar secrets e credenciais de APIs de forma segura para MCP stacks

Veredito

RUDI resolve um problema real para quem trabalha com ecosistemas MCP: centralizar a instalação e orquestração de componentes heterogêneos (npm, binários, runtimes). A abordagem com shims é sensata, mas a curva de aprendizado é moderada e depende da maturidade do registry curado. Útil para arquitetos de AI agents, porém ainda em consolidação.

README

A tradução para o português deste README ainda está na fila.

RUDI CLI

A universal tool manager for MCP stacks, CLI tools, runtimes, and AI agents.

RUDI provides a unified installation and management system for:

  • MCP Stacks - Model Context Protocol servers for Claude, Codex, and Gemini
  • CLI Tools - Any npm package or upstream binary (ffmpeg, ripgrep, etc.)
  • Runtimes - Node.js, Python, Deno, Bun
  • AI Agents - Claude Code, Codex CLI, Gemini CLI

Installation

npm install -g @learnrudi/cli

Requires Node.js 18 or later. The installer creates ~/.rudi/.

Shims are opt-in. If you want PATH exposure for installed tools:

rudi shims rebuild
export PATH="$HOME/.rudi/bins:$PATH"

Core Concepts

Shim-Based Architecture

When you opt in (rudi shims rebuild), tools installed through RUDI get a wrapper script (shim) in ~/.rudi/bins/. This provides:

  • Clean PATH integration without modifying system directories
  • Version isolation per package
  • Ownership tracking for clean uninstalls
  • Consistent invocation across different package sources

When you run tsc, the shell finds ~/.rudi/bins/tsc, which delegates to the actual TypeScript installation at ~/.rudi/binaries/npm/typescript/node_modules/.bin/tsc.

Package Sources

RUDI supports three installation sources:

  1. Dynamic npm (npm:<package>) - Any npm package with a bin field
  2. Curated Registry - Pre-configured stacks and binaries with documentation
  3. Upstream Binaries - Direct downloads from official sources

Secret Management

MCP stacks often require API keys and tokens. RUDI stores secrets in ~/.rudi/secrets.json (mode 0600) and injects them as environment variables when running stacks. Secrets are never exposed in process listings or logs.

Usage

Installing Packages

# Install any npm CLI tool
rudi install npm:typescript       # Installs tsc, tsserver
rudi install npm:@stripe/cli      # Installs stripe
rudi install npm:vercel           # Installs vercel

# Install from curated registry
rudi install slack                # MCP stack for Slack
rudi install binary:ffmpeg        # Upstream ffmpeg binary
rudi install binary:supabase      # Supabase CLI

# Install with scripts enabled (when needed)
rudi install npm:puppeteer --allow-scripts

# Optional: create shims immediately (opt-in)
rudi install binary:ffmpeg --with-shims

Listing Installed Packages

rudi list                # All installed packages
rudi list stacks         # MCP stacks only
rudi list binaries       # CLI tools only
rudi list runtimes       # Language runtimes
rudi list agents         # AI agent CLIs

Searching the Registry

rudi search pdf          # Search for packages
rudi search --all        # List all available packages
rudi search --stacks     # Filter to MCP stacks
rudi search --binaries   # Filter to CLI tools

Managing Secrets

rudi secrets list                      # Show configured secrets (masked)
rudi secrets set SLACK_BOT_TOKEN       # Set a secret (prompts for value)
rudi secrets set OPENAI_API_KEY "sk-..." # Set with value
rudi secrets remove SLACK_BOT_TOKEN    # Remove a secret

Integrating with AI Agents

rudi shims rebuild     # Create rudi-router and rudi-mcp shims (opt-in)
rudi integrate claude    # Add stacks to Claude Desktop config
rudi integrate codex     # Add stacks to Codex config
rudi integrate gemini    # Add stacks to Gemini config
rudi integrate all       # Add to all detected agents

This modifies the agent's MCP configuration file (e.g., ~/Library/Application Support/Claude/claude_desktop_config.json) to include your installed stacks with proper secret injection.

Inspecting Packages

rudi pkg slack           # Show package details
rudi pkg npm:typescript  # Show shims and paths

rudi shims list          # List all shims
rudi shims check         # Validate shim targets exist

Maintenance

rudi update              # Update all packages
rudi update stack:slack  # Reinstall a specific stack and rebuild its tool index
rudi update stack:slack --preserve-state  # Opt in to preserving install-local state paths
rudi remove slack        # Uninstall a package
rudi doctor              # Check system health

Directory Structure

~/.rudi/
├── stacks/               # Installed MCP stack package code
├── skills/               # Installed reusable skill definitions
├── workflows/            # Installed workflow definitions
├── runtimes/             # Managed language runtimes
├── binaries/             # Managed third-party CLI tools
├── agents/               # Managed AI agent CLI installations
│
├── bins/                 # Current command shims and router entrypoints
├── shims/                # Legacy shim directory for older integrations
├── router/               # Local MCP router and permission-hook runtime files
│
├── state/                # Persistent per-stack runtime state
│   └── stacks/
│       └── google-workspace/
│           └── accounts/ # OAuth tokens and selected account state
├── secrets/              # Stack-specific secret/env files
├── secrets.json          # Primary secret store (mode 0600)
│
├── rudi.db               # SQLite database
├── rudi.db-wal           # SQLite write-ahead log, SQLite-managed
├── rudi.db-shm           # SQLite shared-memory file, SQLite-managed
├── rudi.json             # Installed package and stack configuration
├── settings.json         # Local settings
├── shim-registry.json    # Shim ownership tracking
│
├── cache/                # Rebuildable registry/package/tool-index cache
├── locks/                # Package install lock files
├── logs/                 # Daemon and runtime logs
├── notes/                # Local user artifacts from RUDI workflows
├── archive/              # Manual cleanup archives
├── prompts/              # Legacy prompt directory; new assets map to skills/
├── .rudi-lite-port       # Current daemon port file, legacy Lite naming
└── .rudi-lite-token      # Current daemon auth token, legacy Lite naming

Use rudi home for a lifecycle-oriented view of this tree. It labels each path as installed code, persistent state, secret material, generated cache, operational logs, or legacy compatibility. Use rudi home --json for machine-readable output.

How MCP Integration Works

When you run rudi integrate claude, RUDI:

  1. Reads the Claude Desktop config at ~/Library/Application Support/Claude/claude_desktop_config.json
  2. Adds entries for each installed stack pointing to ~/.rudi/bins/rudi-mcp
  3. Passes the stack ID as an argument

When Claude invokes the MCP server:

  1. rudi-mcp receives the stack ID
  2. Loads secrets from ~/.rudi/secrets.json
  3. Injects secrets as environment variables
  4. Spawns the actual MCP server process
  5. Proxies stdio between Claude and the server

This architecture means secrets stay local and are never written to agent config files.

Security Model

npm Package Installation

By default, npm packages install with --ignore-scripts to prevent arbitrary code execution during install. If a package requires lifecycle scripts (e.g., native compilation), use:

rudi install npm:puppeteer --allow-scripts

Secret Storage

Secrets are stored in ~/.rudi/secrets.json with file permissions 0600 (owner read/write only). This matches the security model used by SSH, AWS CLI, and other credential stores.

Shim Isolation

Each package installs to its own directory. Shims are thin wrappers that set up the environment and delegate to the real binary. This prevents packages from interfering with each other.

Available Stacks

StackDescriptionRequired Secrets
slackChannels, messages, reactionsSLACK_BOT_TOKEN
google-workspaceGmail, Sheets, Docs, DriveGOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET
notion-workspacePages, databases, searchNOTION_API_KEY
githubIssues, PRs, repos, actionsGITHUB_TOKEN
postgresSQL queriesDATABASE_URL
stripePayments, subscriptionsSTRIPE_SECRET_KEY
openaiDALL-E, Whisper, TTSOPENAI_API_KEY
google-aiGemini, ImagenGOOGLE_AI_API_KEY

Available Binaries

BinaryDescriptionSource
ffmpegVideo/audio processingUpstream
ripgrepFast text searchUpstream
supabaseSupabase CLInpm
vercelVercel CLInpm
uvPython package managerUpstream

Troubleshooting

Command not found after install

Ensure ~/.rudi/bins is in your PATH:

echo $PATH | grep -q '.rudi/bins' && echo "OK" || echo "Add ~/.rudi/bins to PATH"

Shim points to missing target

Run rudi shims check to validate all shims. If a target is missing, reinstall the package:

rudi remove npm:typescript
rudi install npm:typescript

MCP stack not appearing in agent

  1. Check the stack is installed: rudi list stacks
  2. Run integration: rudi integrate claude
  3. Restart the AI agent application

Permission denied on secrets

Ensure correct permissions:

chmod 600 ~/.rudi/secrets.json

Links

License

MIT

Ver o original no GitHub

Bom para

Relacionados