Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 85%
↑ 1.73xAgent success when using this skill
Validation for skill structure
stdio server exploration and tool calling
Schema inspection
0%
83%
stdio flag used
0%
100%
Selector syntax
0%
100%
JSON args usage
0%
0%
Output json flag
0%
100%
Results captured
100%
100%
Both tools called
100%
100%
Correct tool arguments
100%
100%
Process documented
100%
100%
Without context: $0.2177 · 52s · 12 turns · 17 in / 3,914 out tokens
With context: $0.6736 · 2m 18s · 36 turns · 195 in / 7,890 out tokens
config management and custom config paths
config add used
85%
85%
config list used
100%
100%
config remove used
0%
0%
Default config path
66%
75%
--config override
100%
100%
Multiple env configs
100%
100%
Output json flag
50%
40%
Workflow documented
100%
100%
Config files present
100%
100%
Without context: $0.3899 · 1m 32s · 27 turns · 692 in / 4,872 out tokens
With context: $0.4111 · 1m 44s · 27 turns · 29 in / 5,233 out tokens
TypeScript codegen and CLI generation
emit-ts used
0%
100%
Correct --mode flag
0%
100%
generate-cli used
0%
100%
inspect-cli used
0%
100%
inspect-cli --json flag
0%
100%
Output json flag
0%
0%
TypeScript file produced
100%
100%
CLI artifact produced
100%
100%
Workflow script present
100%
100%
Without context: $3.0390 · 8m 59s · 85 turns · 2,259 in / 31,186 out tokens
With context: $1.1403 · 3m 6s · 55 turns · 59 in / 10,907 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.