Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add magus-cli -- npx -y magus-cli@7.14.2Ejecútalo en una terminal.
{ "mcpServers": { "magus-cli": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirWhile you're fighting with AI prompts, elite teams are shipping 3x faster.
At MadAppGang and 10xLabs, we don't do "good enough." We're the teams that Fortune 500 companies hire when their own developers can't deliver. We architect platforms processing $50M+ in annual transactions. We scale systems to 500,000+ concurrent users. We ship features that make or break businesses.
Here's what separates us: While most developers adopt new tools, we engineer competitive advantages.
When Claude Code launched, we didn't experiment—we weaponized it into production workflows that have:
⚡ Generated $2.3M in value through faster time-to-market on enterprise contracts ⚡ Eliminated 156+ hours per sprint of repetitive development work ⚡ Shipped 47 major features to production with zero rollbacks ⚡ Scaled to 23-person engineering teams without losing velocity ⚡ Cut AI token costs by 40% while improving output quality by 60%
Most developers are doing AI-assisted development wrong.
They're copying prompts from Reddit. Following tutorials from people who've never shipped to production. Using workflows that optimize for demos, not delivery.
The cost? Weeks of wasted time. Features that ship broken. AI bills that balloon. Teams that slow down instead of speed up.
Every single workflow in these plugins was forged in the fire of real deadlines, real users, and real revenue. Not built for GitHub stars. Built to win contracts and crush competitors.
We don't use "good enough" tools. We use the tools that win.
Stop burning cash on inefficient AI usage. Our semantic search optimization alone has saved our teams $14,000+ annually in API costs.
Stop shipping buggy code. Our multi-stage review system (manual + AI + browser testing) catches 89% of bugs before they hit production.
Stop reinventing workflows. These plugins encode 2,500+ hours of workflow optimization that you get in 60 seconds.
Option A: Keep experimenting with generic AI prompts, watching your competitors ship faster, burning budget on trial-and-error.
Option B: Use the exact workflows that elite teams use to build products worth millions.
These aren't "best practices" from blog posts. This is the battle-tested playbook that ships features to Fortune 500 clients, scales to hundreds of thousands of users, and wins against competitors with 10x your budget.
This is how the top 1% actually builds software in 2025.
Already installed? Update to get the latest features:
/plugin marketplace update magus
This single command updates everything - works for both global and local installations. No need to reinstall plugins.
Recommended Setup: Add marketplace globally, enable plugins per-project.
# Step 1: Add marketplace globally (one-time setup)
/plugin marketplace add MadAppGang/magus
# Optional: content plugins (image generation, video editing)
/plugin marketplace add MadAppGang/magus-marketing
Then add to your project's .claude/settings.json:
{
"enabledPlugins": {
"dev@magus": true,
"code-search@magus": true,
"multimodel@magus": true,
"terminal@magus": true
}
}
That's it! The plugins are now enabled for this project. Commit .claude/settings.json so your team gets the same setup automatically.
This repository contains production-ready plugins designed for modern web development teams. Each plugin includes specialized agents, custom slash commands, and workflow skills to streamline your development process.
Version: 5.3.0 | Category: Development | Marketplace: magus
Read-only code investigation for understanding complex codebases, behind one stable tool surface that does not change when the search engine does.
Highlights:
code-search:analyze agent - Investigates code patterns, relationships, and architecturecode-search, investigate, deep-analysiscode_search is always present; call-graph and blast-radius tools
appear only when the configured search engine genuinely supports themPerfect for: Code exploration, bug investigation, understanding legacy code, architectural analysis, large codebase navigation
Version: 3.2.0 | Category: Development | Marketplace: magus
Multi-agent coordination and multi-model orchestration. Run the same task across several AI
models in parallel and collect independent verdicts. Requires the
claudish runtime plugin (declared as a dependency).
Commands:
/multimodel:team - Blind voting across models in parallel; aggregates APPROVE/REJECT verdicts/multimodel:delegate - Hand a task to one external model running a full Claude Code sessionSkills (2 under plugins/multimodel/skills/):
Model routing and provider backends are covered by claudish:claudish-usage, which ships
with the claudish runtime plugin. Read it before ANY claudish command.
Perfect for: complex multi-phase workflows, multi-model validation, parallel execution patterns, production-grade error handling
Model IDs come from claudish's live catalog (
list_models/search_models) — pass the bare model ID and let claudish route it. Never add provider prefixes, and never resolve an ID from memory or a committed file.
Repository: github.com/MadAppGang/claudish | Category: Development Tools | Type: Standalone CLI
Run Claude Code with any OpenRouter model via local Anthropic API proxy. 100% VERIFIED - Routes to real OpenRouter models, NOT Anthropic.
Model selection resolves against claudish's live catalog via the list_models and search_models MCP tools — a curated database fed by 18+ provider collectors and cached for 24 hours, so it never needs a manual sync. Name a family like grok, gemini or gpt and claudish resolves the current model and provider automatically.
Features:
--no-auto-approve)Installation:
npm install -g claudish
Usage:
# Interactive mode - shows model selector
claudish "implement user authentication"
# Specific model (use aliases — claudish resolves providers)
claudish --model grok "add tests"
# Or full model ID
claudish --model grok-4.5 "your task"
# Disable auto-approve
claudish --no-auto-approve "make changes"
# List all models
claudish --list-models
# Help
claudish --help
Documentation: See github.com/MadAppGang/claudish for detailed setup and usage.
Perfect for: Exploring different AI models, cost optimization, specialized tasks requiring specific model capabilities, testing model performance, avoiding Anthropic API limitations
Claude Code Requirements:
.claude-plugin/plugin.json (required)enabledPlugins must be object with boolean values:
{
"enabledPlugins": {
"plugin-name@marketplace-name": true
}
}
System Requirements:
This approach gives you the best of both worlds: marketplace installed once globally, plugins enabled individually per project.
Each developer on your team does this once:
/plugin marketplace add MadAppGang/magus
This registers the Magus marketplace in your Claude Code installation. You only need to do this once, and it works for all your projects.
Magus ships on three channels. Core development plugins live in magus; add the others only
if you need them:
Plugin IDs carry the marketplace, so enable them as image@magus-marketing, not image@magus.
Add or edit .claude/settings.json in your project root:
{
"enabledPlugins": {
"dev@magus": true,
"code-search@magus": true
}
}
Commit this file to git:
git add .claude/settings.json
git commit -m "Enable Magus plugins for this project"
git push
When team members who have added the marketplace (Step 1) pull your project, Claude Code automatically:
No manual installation needed!
✅ One-time marketplace setup - Add the marketplace once, use in all projects ✅ Per-project plugin control - Each project specifies its own plugins ✅ Team consistency - Everyone gets the same plugins automatically ✅ Version controlled - Plugin configuration committed with your code ✅ No environment drift - All team members have identical plugin setup ✅ Project isolation - Plugins only active where you need them
Need more than one plugin? Just add more entries:
{
"enabledPlugins": {
"dev@magus": true,
"code-search@magus": true,
"multimodel@magus": true,
"terminal@magus": true,
"setup@magus": true
}
}
After setup, verify everything works:
# Check for any errors
/doctor
# List installed plugins
/plugin list
# Should show:
# dev@magus (project-specific)
# Version: 1.35.1
# Status: ✓ Loaded
Common issues:
/doctor shows errors, see Troubleshooting below.claude/settings.jsonOnce installed, plugins work seamlessly with Claude Code:
Agents are automatically invoked by Claude when appropriate, or you can request them explicitly.
Slash Commands provide powerful one-line workflows for common tasks.
Skills enhance Claude's capabilities and are automatically used when relevant.
/implement Create a user profile page with avatar upload and bio editing
This single command:
Result: Complete feature in minutes, not hours.
/import-figma NavigationBar
Fetches your Figma component, adapts it to your codebase, installs dependencies, and opens it in browser for validation.
Start at the documentation home.
Writing a plugin is a separate tutorial; those guides live in docs/authoring/ and are not
part of the user documentation.
Have a plugin idea? Open an issue with the plugin-request label.
Planned work and candidate plugins live in ROADMAP.md. This README describes what ships today.
This project is licensed under the MIT License - see the LICENSE file for details.
Individual plugins may have their own licenses specified in their plugin.json files.
Jack Rudenko Email: [email protected] Company: MadAppGang
Made with ❤️ by MadAppGang
TUI tool for managing Claude Code plugins, MCPs, and configuration
{ "mcpServers": { "magus-cli": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Magus Cli se ejecuta localmente por stdio.
Última comprobación: 2026-11-14. TUI tool for managing Claude Code plugins, MCPs, and configuration