tzachbon/srulik-toolkit / plugins/mcporter-plugin/skills/mcporter
mcporter
UnverifiedUse MCP servers through the mcporter CLI and saved deterministic scripts instead of native MCP tools. Use whenever a task needs an MCP server's tools, when the session hint lists mcporter servers, or when the user asks to script, save, or maintain MCP calls.
mcporter
Native MCP tools cost one model turn per call, and every raw result lands in context. mcporter runs the same tools from the shell, so one command can make many calls and return only the answer.
Choose the form
| Task | Use |
|---|---|
| One call, look at the result | mcporter call <server>.<tool> key:value --output json |
| Two or more calls, a loop, filtering, or something you may repeat | a script in .mcporter/scripts/ |
| A server you use every day | mcporter generate-cli --server <name> for a typed CLI |
Discover before calling: mcporter list shows servers, and
mcporter list <server> --schema shows tool signatures. Read only the schema
you need.
Servers the harness injects itself (they are absent from mcporter list) stay
on their native tools.
Login needed
When a call fails with Authorization required ... run 'mcporter auth <name>',
stop. Do not retry, switch to the native tool, or edit the config: ask the user
to run that command (with --no-browser it prints the login URL), then
continue. Run with MCPORTER_OAUTH_NO_BROWSER=1 so a call fails at once
instead of opening a browser and waiting for a login.
Write a script
- Read
.mcporter/scripts/README.md. Reuse or extend an existing script before adding one. - Write the script. Use a Node script with
createRuntime()frommcporterwhen it makes several calls: one process keeps one connection, and it can be recorded and replayed. A bash one-liner around a singlemcporter callis fine for one call. Node resolvesimport 'mcporter'from the project'snode_modulesonly, not from a global install ornpx, so install it once per project:npm install --save-dev mcporter@0.17.0. - Start with the header: purpose, arguments, servers and tools used, output format, and the replay command. Print only the result to stdout (JSON, TSV or one value). Send errors to stderr and exit non-zero.
- Run it once against the live server.
- Record a fixture:
mcporter record <script-name> -- node .mcporter/scripts/<file>, then copy~/.mcporter/recordings/<script-name>.ndjsonto.mcporter/fixtures/. Check the fixture for secrets before committing it. - Add one row to
.mcporter/scripts/README.md.
A worked example lives in examples/.mcporter:
inventory-gold-stock.mjs pages through a server and returns one integer, and
inventory-item.sh wraps a single call. Its config/mcporter.json points
at the benchmark's local fake server, so the example runs offline from that
directory once npm install mcporter@0.17.0 has run there.
Maintain scripts
- Where: per project in
.mcporter/scripts/, committed. Scripts shared by every project go in~/.mcporter/scripts/. - Check: copy the fixture into
~/.mcporter/recordings/, then runmcporter replay <script-name> -- node .mcporter/scripts/<file>. Replay runs offline and fails when the script's calls no longer match the recording. - Drift: when a live call fails on a changed tool, run
mcporter list <server> --schema, fix the script, rerun it live, and record the fixture again. - Remove a script that fails its replay and is no longer used, along with its fixture and README row.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |