# @web4w3/install
A registry package that ships pre-compiled, self-contained bundles of every MCP server in the Web4W3 ecosystem. Drop it into your Claude config with one line and start using any MCP immediately. No TypeScript, no esbuild, no manual npm installs required.
## How It Works
Each MCP server in the Web4W3 ecosystem is bundled into a single self-contained .mjs file using esbuild. The @web4w3/install package ships these bundles on npm. When you run `npx @web4w3/install chrome-bridge`, npx downloads the package (once, then cached), the index.js launcher validates your environment variables, and dynamically imports the pre-compiled bundle — which then takes over stdio as a standard MCP server.
npx @web4w3/install <mcp-name>
└── index.js (launcher)
├── validate env vars
└── import dist/<mcp-name>.mjs
└── MCP server speaks stdio to Claude## Screenshots
❯ npx @web4w3/install --list Available MCPs: ✓ android-bridge Control Android device settings ✓ brotherhood Bridge two Claude Code sessions ✓ chrome-bridge AI control of your Chrome browser ✓ gmail Read and manage Gmail via IMAP ✓ msteams Microsoft Teams via Graph API ✓ nut-js Desktop automation — mouse + keyboard ✓ outlook Outlook email via Microsoft Graph
❯ npx -y @web4w3/install chrome-bridge ← Starting chrome-bridge MCP server... ← Connecting to Chrome DevTools Protocol... ✓ Connected to Chrome (tab: New Tab) ✓ MCP server ready on stdio [Waiting for MCP client commands]
❯ cat claude_desktop_config.json { "mcpServers": { "chrome-bridge": { "command": "npx", "args": ["-y", "@web4w3/install", "chrome-bridge"] }, "gmail": { "command": "npx", "args": ["-y", "@web4w3/install", "gmail"], "env": { "GMAIL_USER": "you@gmail.com" } } } }
## Features
- +All 7 MCP servers bundled and ready to run
- +Single npx command — works offline after first run
- +Validates required environment variables on startup
- +Lists all available MCPs with build status
- +Zero runtime dependencies
## vs. The Field
| Feature | @web4w3/install | Manual install | Docker MCP |
|---|---|---|---|
| One command to start | ✓ | ✗ | partial |
| No build step | ✓ | ✗ | ✓ |
| Native Node.js speed | ✓ | ✓ | ✗ |
| Works offline (after first run) | ✓ | ✓ | ✗ |
| All MCPs in one package | ✓ | ✗ | partial |
| Env var validation | ✓ | ✗ | ✗ |
| Claude Code compatible | ✓ | ✓ | partial |
## Installation
Add to Claude Code config
Edit your Claude config to add any MCP with a single entry.
{
"mcpServers": {
"chrome-bridge": {
"command": "npx",
"args": ["-y", "@web4w3/install", "chrome-bridge"]
}
}
}Or run directly from terminal
Start any MCP server manually to test it.
npx @web4w3/install chrome-bridge # Or list all available MCPs: npx @web4w3/install --list
Set required environment variables
Some MCPs need credentials — set them in the env block or your shell.
# Gmail example
"env": {
"GMAIL_USER": "you@gmail.com",
"GMAIL_APP_PASSWORD": "xxxx xxxx xxxx xxxx"
}
# Brotherhood example
"env": {
"BROTHERHOOD_ROOM_ID": "my-room",
"BROTHERHOOD_SECRET": "s3cr3t",
"BROTHERHOOD_RELAY_URL": "wss://relay.example.com"
}⚠ Run `npx @web4w3/install <mcp-name>` without env vars to see exactly which are required.