Mcporter
Mcporter
Section titled “Mcporter”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.
Skill metadata
Section titled “Skill metadata”| Source | Optional — install with hermes skills install official/mcp/mcporter |
| Path | optional-skills/mcp/mcporter |
| Version | 1.0.0 |
| Author | community |
| License | MIT |
| Tags | MCP, Tools, API, Integrations, Interop |
Reference: full SKILL.md
Section titled “Reference: full SKILL.md”The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
mcporter
Section titled “mcporter”Use mcporter to discover, call, and manage MCP (Model Context Protocol) servers and tools directly from the terminal.
Prerequisites
Section titled “Prerequisites”Requires Node.js:
# No install needed (runs via npx)npx mcporter list
# Or install globallynpm install -g mcporterQuick Start
Section titled “Quick Start”# List MCP servers already configured on this machinemcporter list
# List tools for a specific server with schema detailsmcporter list <server> --schema
# Call a toolmcporter call <server.tool> key=valueDiscovering MCP Servers
Section titled “Discovering MCP Servers”mcporter auto-discovers servers configured by other MCP clients (Claude Desktop, Cursor, etc.) on the machine. To find new servers to use, browse registries like mcpfinder.dev or mcp.so, then connect ad-hoc:
# Connect to any MCP server by URL (no config needed)mcporter list --http-url https://some-mcp-server.com --name my_server
# Or run a stdio server on the flymcporter list --stdio "npx -y @modelcontextprotocol/server-filesystem" --name fsCalling Tools
Section titled “Calling Tools”# Key=value syntaxmcporter call linear.list_issues team=ENG limit:5
# Function syntaxmcporter call "linear.create_issue(title: \"Bug fix needed\")"
# Ad-hoc HTTP server (no config needed)mcporter call https://api.example.com/mcp.fetch url=https://example.com
# Ad-hoc stdio servermcporter call --stdio "bun run ./server.ts" scrape url=https://example.com
# JSON payloadmcporter call <server.tool> --args '{"limit": 5}'
# Machine-readable output (recommended for Hermes)mcporter call <server.tool> key=value --output jsonAuth and Config
Section titled “Auth and Config”# OAuth login for a servermcporter auth <server | url> [--reset]
# Manage configmcporter config listmcporter config get <key>mcporter config add <server>mcporter config remove <server>mcporter config import <path>Config file location: ./config/mcporter.json (override with --config).
Daemon
Section titled “Daemon”For persistent server connections:
mcporter daemon startmcporter daemon statusmcporter daemon stopmcporter daemon restartCode Generation
Section titled “Code Generation”# Generate a CLI wrapper for an MCP servermcporter generate-cli --server <name>mcporter generate-cli --command <url>
# Inspect a generated CLImcporter inspect-cli <path> [--json]
# Generate TypeScript types/clientmcporter emit-ts <server> --mode clientmcporter emit-ts <server> --mode types- Use
--output jsonfor structured output that’s easier to parse - Ad-hoc servers (HTTP URL or
--stdiocommand) work without any config — useful for one-off calls - OAuth auth may require interactive browser flow — use
terminal(command="mcporter auth <server>", pty=true)if needed