$npx -y skills add minghinmatthewlam/agent-guards --skill mcporterCLI access to MCP servers without loading them into agent context (saves tokens). Use when: (1) calling MCP tools on-demand, (2) want to avoid MCP context overhead.
| 1 | # MCPorter |
| 2 | |
| 3 | Call MCP server tools via CLI without a persistent connection. Keeps tool schemas out of context. |
| 4 | |
| 5 | ## Quick Start |
| 6 | |
| 7 | ```bash |
| 8 | mcporter list # available servers |
| 9 | mcporter list <server> --schema # tools + args (always run before first call) |
| 10 | mcporter call <server>.<tool> key:val # call a tool |
| 11 | ``` |
| 12 | |
| 13 | ## Rules |
| 14 | |
| 15 | - Always run `mcporter list <server> --schema` before first call — tool names drift between versions. |
| 16 | - If a server is offline or auth-gated, report it and continue with fallback tools. |
| 17 | |
| 18 | ## Non-Obvious Workflows |
| 19 | |
| 20 | ### Chrome live-session debugging |
| 21 | |
| 22 | Connects to the user's running Chrome with existing login state and cookies. Requires Chrome remote debugging and user consent prompt approval. |
| 23 | |
| 24 | ```bash |
| 25 | mcporter list chrome-devtools --schema |
| 26 | mcporter call chrome-devtools.list_pages |
| 27 | mcporter call chrome-devtools.select_page pageIndex:0 |
| 28 | mcporter call chrome-devtools.take_screenshot |
| 29 | mcporter call chrome-devtools.evaluate_script function:"() => document.title" |
| 30 | ``` |
| 31 | |
| 32 | ### When to use mcporter vs direct MCP |
| 33 | |
| 34 | - **mcporter**: One-off or infrequent tool calls. Keeps context clean. |
| 35 | - **Direct MCP**: Frequent use in a session, need streaming, tight integration. |