MCP service management
Use the mcporter CLI to list, configure, authenticate, and directly call the MCP server/tool (HTTP or stdio).
What this skill does
# mcporter Use `mcporter` to work with MCP servers directly. Quick start - `mcporter list` - `mcporter list <server> --schema` - `mcporter call <server.tool> key=value` Call tools - Selector: `mcporter call linear.list_issues team=ENG limit:5` - Function syntax: `mcporter call "linear.create_issue(title: \"Bug\")"` - Full URL: `mcporter call https://api.example.com/mcp.fetch url:https://example.com` - Stdio: `mcporter call --stdio "bun run ./server.ts" scrape url=https://example.com` - JSON payload: `mcporter call <server.tool> --args '{"limit":5}'` Auth + config - OAuth: `mcporter auth <server | url> [--reset]` - Config: `mcporter config list|get|add|remove|import|login|logout` Daemon - `mcporter daemon start|status|stop|restart` Codegen - CLI: `mcporter generate-cli --server <name>` or `--command <url>` - Inspect: `mcporter inspect-cli <path> [--json]` - TS: `mcporter emit-ts <server> --mode client|types` Notes - Config default: `./config/mcporter.json` (override with `--config`). - Prefer `--output json` for machine-readable results.
- Clarifies goals, inputs, and success criteria
- Preserves evidence and marks uncertain boundaries
- Produces structured, editable results