Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →trpc-group/mcporter
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, CLI/type generation, and MCP-backed skills that need a durable command path.
Passed 17 of 20 test cases with the skill, and 3 of 20 without it.
and 21 more in the full report
16 fixed3 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to create an issue on Linear using function-style syntax on the command line rather than space-separated key-value pairs. I need to call `linear.create_issue` with a `title` of `Bug`. Show the function-style command.
| Checked | Without skill | With skill |
|---|---|---|
| Uses function-syntax linear.create_issue(title: "Bug") in the mcporter call command | Missed | Passed |
The instructions your model reads when the skill loads.
Use mcporter to work with MCP servers directly.
In OpenClaw, treat mcporter as the execution substrate for MCP-backed
skills. When a user wants to keep an MCP capability for future work, prefer
creating or updating a skill that describes when to use the capability and
stores the repeatable mcporter command path. Do not create a separate runtime
registry when a skill can carry the durable behavior.
Skill-first MCP shape
SKILL.md: triggers, workflow, constraints, examples, and recovery steps.mcp.json: mcporter-native server config when the skill needs a dedicated
server definition.references/: schemas, API notes, or longer operation guides.scripts/: wrappers for fragile multi-step calls or post-processing.Credential handling
mcp.json in a writable
user-managed skill root, or a dedicated user-managed private mcporter config
file. Keep it non-shared and excluded from source control and packaging. Set
file permissions to 0600 when possible. Do not ask the user to re-enter the
same value as an environment variable, and do not edit shell startup or
trusted env files just to persist it. Do not echo the secret value back in
CLI output, logs, or errors; redact or omit token and secret fields from
displayed tool results.mcp.json. Use mcporter --config path/to/skill/mcp.json ...
as the durable command path. Treat ~/.mcporter/mcporter.json as an
interoperability copy when useful, not as the capability boundary. The
credential-bearing source of truth for a durable skill run is the explicit
--config file you pass.test cases passed, vs 3 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.