Add on-demand heavy MCP activation commands

.gitattributes

@@ -1,2 +1,3 @@
 * text eol=lf
 *.png binary
+dist-bun/*.tar.gz binary

README.md

@@ -20,6 +20,7 @@ MCPorter helps you lean into the "code execution" workflows highlighted in Anthr
 - **One-command CLI generation.** `mcporter generate-cli` turns any MCP server definition into a ready-to-run CLI, with optional bundling/compilation and metadata for easy regeneration.
 - **Typed tool clients.** `mcporter emit-ts` emits `.d.ts` interfaces or ready-to-run client wrappers so agents/tests can call MCP servers with strong TypeScript types without hand-writing plumbing.
 - **Friendly composable API.** `createServerProxy()` exposes tools as ergonomic camelCase methods, automatically applies JSON-schema defaults, validates required arguments, and hands back a `CallResult` with `.text()`, `.markdown()`, `.json()`, `.images()`, and `.content()` helpers.
+- **On-demand heavy MCPs.** Keep large schema payloads such as `chrome-devtools` out of your default config until you need them, then toggle them with `mcporter heavy list|activate|deactivate`.
 - **OAuth and stdio ergonomics.** Built-in OAuth caching, log tailing, and stdio wrappers let you work with HTTP, SSE, and stdio transports from the same interface.
 - **Ad-hoc connections.** Point the CLI at *any* MCP endpoint (HTTP or stdio) without touching config, then persist it later if you want. Hosted MCPs that expect a browser login (Supabase, Vercel, etc.) are auto-detected—just run `mcporter auth <url>` and the CLI promotes the definition to OAuth on the fly. See [docs/adhoc.md](docs/adhoc.md).
 
@@ -184,6 +185,18 @@ npx mcporter call --stdio "bun run ./local-server.ts" --name local-tools
 - The daemon only manages named servers that come from your config/imports. Ad-hoc STDIO/HTTP targets invoked via `--stdio …`, `--http-url …`, or inline function-call syntax remain per-process today; persist them into `config/mcporter.json` (or use `--persist`) if you need them to participate in the shared daemon.
 - Troubleshooting? Run `mcporter daemon start --log` (or `--log-file /tmp/daemon.log`) to tee stdout/stderr into a file, and add `--log-servers chrome-devtools` when you only want call traces for a specific MCP. Per-server configs can also set `"logging": { "daemon": { "enabled": true } }` to force detailed logging for that entry.
 
+### Load heavy MCPs on demand
+
+If a server ships an unusually large schema payload, keep it out of your default config and enable it only when needed:
+
+```bash
+npx mcporter heavy list
+npx mcporter heavy activate chrome-devtools
+npx mcporter heavy deactivate chrome-devtools
+```
+
+Heavy definitions live next to your resolved `mcporter.json` under `heavy/available/`, and activation merges the selected definition into the main config while tracking its status under `heavy/active/`. If a heavy definition would overwrite an existing `mcpServers` entry with different settings, activation aborts instead of clobbering your config.
+
 
 ## Friendlier Tool Calls
 

src/cli.ts

@@ -8,6 +8,7 @@ import { handleDaemonCli } from './cli/daemon-command.js';
 import { handleEmitTs } from './cli/emit-ts-command.js';
 import { CliUsageError } from './cli/errors.js';
 import { handleGenerateCli } from './cli/generate-cli-runner.js';
+import { handleHeavyCli } from './cli/heavy-command.js';
 import { consumeHelpTokens, isHelpToken, isVersionToken, printHelp, printVersion } from './cli/help-output.js';
 import { handleInspectCli } from './cli/inspect-cli-command.js';
 import { handleList, printListHelp } from './cli/list-command.js';
@@ -23,6 +24,7 @@ export { handleAuth, printAuthHelp } from './cli/auth-command.js';
 export { parseCallArguments } from './cli/call-arguments.js';
 export { handleCall } from './cli/call-command.js';
 export { handleGenerateCli } from './cli/generate-cli-runner.js';
+export { handleHeavyCli } from './cli/heavy-command.js';
 export { handleInspectCli } from './cli/inspect-cli-command.js';
 export { extractListFlags, handleList } from './cli/list-command.js';
 export { resolveCallTimeout } from './cli/timeouts.js';
@@ -100,6 +102,11 @@ export async function runCli(argv: string[]): Promise<void> {
     return;
   }
 
+  if (command === 'heavy') {
+    await handleHeavyCli(args, { configPath, rootDir: rootOverride });
+    return;
+  }
+
   if (command === 'emit-ts') {
     const runtime = await createRuntime(runtimeOptionsWithPath);
     try {