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
Use mcporter to work with MCP servers directly.
Quick start
mcporter listmcporter list <server> --schemamcporter call <server.tool> key=valueCall tools
mcporter call linear.list_issues team=ENG limit:5mcporter call "linear.create_issue(title: \"Bug\")"mcporter call https://api.example.com/mcp.fetch url:https://example.commcporter call --stdio "bun run ./server.ts" scrape url=https://example.commcporter call <server.tool> --args '{"limit":5}'Auth + config
mcporter auth <server | url> [--reset]mcporter config list|get|add|remove|import|login|logoutDaemon
mcporter daemon start|status|stop|restartCodegen
mcporter generate-cli --server <name> or --command <url>mcporter inspect-cli <path> [--json]mcporter emit-ts <server> --mode client|typesNotes
./config/mcporter.json (override with --config).--output json for machine-readable results.cc4d1f7
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.