Mcporter
Wire your coding agent to MCP servers by listing tools, authenticating, and calling them from the terminal without hand-rolling HTTP or stdio clients.
Overview
mcporter is an agent skill for the Build phase that teaches agents to list, authenticate, call, and inspect MCP servers and tools via the mcporter CLI over HTTP or stdio.
Install
npx skills add https://github.com/steipete/clawdis --skill mcporterWhat is this skill?
- List MCP servers and dump per-server tool schemas with `mcporter list` and `--schema`
- Call tools over HTTP URLs, dotted selectors, function syntax, JSON `--args`, or `--stdio` subprocess servers
- OAuth and config lifecycle: `auth`, `config list|get|add|remove|import|login|logout`
- Optional daemon for long-running MCP processes: start, status, stop, restart
- Codegen helpers: `generate-cli`, `inspect-cli`, and `emit-ts` in client or types mode
- Documents list, call, auth, config, daemon, and codegen command families in one SKILL.md quick start
Adoption & trust: 2.7k installs on skills.sh; 378k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have MCP servers to use from an agent session but no consistent way to list tools, handle OAuth, or invoke calls across HTTP and stdio transports.
Who is it for?
Builders actively integrating MCP servers into local agent workflows who want a single CLI for auth, calls, and inspection.
Skip if: Teams that only need a hosted MCP dashboard with no terminal workflow, or projects with zero MCP usage.
When should I use this skill?
You need to list, configure, authenticate, call, or inspect MCP servers and tools with mcporter over HTTP or stdio.
What do I get? / Deliverables
You can run documented mcporter commands to configure servers, call tools with structured payloads, and optionally generate CLI or TypeScript bindings for repeat use.
- Successful MCP tool invocations with logged arguments and responses
- Updated mcporter config or auth state for named servers
- Optional generated CLI wrapper or TypeScript client/types from `generate-cli` / `emit-ts`
Recommended Skills
Journey fit
MCP wiring is part of assembling agent capabilities while you build integrations and local tooling. mcporter is purpose-built for Model Context Protocol servers—the same layer as skills, tools, and agent runtimes—not for shipping or growth work.
How it compares
Use as a focused MCP operations CLI skill—not a replacement for writing custom MCP server code in your repo.
Common Questions / FAQ
Who is mcporter for?
Solo and indie developers using AI coding agents who need to discover, authenticate, and call MCP tools from the terminal during integration work.
When should I use mcporter?
Use it in the Build phase while wiring agent-tooling: after you add an MCP server, when debugging tool schemas, or when you need OAuth or stdio calls before shipping an agent feature.
Is mcporter safe to install?
It requires running the mcporter binary and often network access for remote MCP endpoints; review the Security Audits panel on this Prism page and treat OAuth tokens like production secrets.
SKILL.md
READMESKILL.md - Mcporter
# 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.