Use it when your goal in servers and infrastructure is clear and you can limit it to the data and actions it actually needs.
Directory → SKILL
SKILLoptionalHermes Optional Skills
Mcporter
List, auth, and call MCP servers/tools from the terminal
Last registry verification2026-08-18v1.0.0community
What does it add to Hermes?
List, auth, and call MCP servers/tools from the terminal
Mcporter is a skill related to servers and infrastructure. It helps the agent understand or operate technical resources that can affect cost, availability, and security.
This plain-language explanation is based on the publisher description. The original text remains visible for verification.
Do not add it merely to experiment when Hermes already has a simpler path, or when you cannot review its source and permissions.
Best for users who want a repeatable way of working inside Hermes.
Start in a test environment with a limited account and inspect status before creating or deleting anything.
Original publisher description
List, auth, and call MCP servers/tools from the terminal
Data source
This entry was indexed from Hermes Optional Skills. Our explanation interprets the type and domain without inventing a capability not present upstream.
Security review
The source is official or editorially reviewed, but you still need to review permissions and version compatibility.
Inspect, install, then test.
- 01Open the source
Match the publisher, license, and description to your need. Check the real update history.
- 02Review permissions and secrets
Never paste a secret value into this site. Use environment-variable names and grant the smallest scope.
- 03Copy setup only after review
The controls below copy text. They do not execute commands on your device.
- 04Test with a non-sensitive task
Inspect the visible tools, then exclude write or delete tools you do not need.
Review the command, then copy it.
hermes skills install mcporterHermes Belarabi does not execute this command. Installation happens on your device and remains subject to Hermes scanning and your review.
Exactly what Hermes loads when this skill runs.
Reproduced from the official documentation. Read it before enabling the skill: this text becomes the agent's instructions.
List, auth, and call MCP servers/tools from the terminal.
Skill metadata
A lookup table. Do not read it all; find the row that applies to you.
| Source | Optional — install with hermes skills install official/mcp/mcporter |
| Path | optional-skills/mcp/mcporter |
| Version | 1.0.0 |
| Author | community |
| License | MIT |
| Platforms | linux, macos, windows |
| Tags | MCP, Tools, API, Integrations, Interop |
Reference: full SKILL.md
Explains the idea itself. Read it slowly; the later sections build on it.
Use mcporter to discover, call, and manage MCP (Model Context Protocol) ↗ servers and tools directly from the terminal.
Prerequisites
Explains the idea itself. Read it slowly; the later sections build on it.
Requires Node.js:
# No install needed (runs via npx)
npx mcporter list
# Or install globally
npm install -g mcporterQuick Start
Ordered, practical steps. Run one and confirm it worked before moving on.
# List MCP servers already configured on this machine
mcporter list
# List tools for a specific server with schema details
mcporter list <server> --schema
# Call a tool
mcporter call <server.tool> key=valueDiscovering MCP Servers
Explains the idea itself. Read it slowly; the later sections build on it.
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 fly
mcporter list --stdio "npx -y @modelcontextprotocol/server-filesystem" --name fsCalling Tools
Explains the idea itself. Read it slowly; the later sections build on it.
# Key=value syntax
mcporter call linear.list_issues team=ENG limit:5
# Function syntax
mcporter 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 server
mcporter call --stdio "bun run ./server.ts" scrape url=https://example.com
# JSON payload
mcporter call <server.tool> --args '{"limit": 5}'
# Machine-readable output (recommended for Hermes)
mcporter call <server.tool> key=value --output jsonAuth and Config
Explains the idea itself. Read it slowly; the later sections build on it.
# OAuth login for a server
mcporter auth <server | url> [--reset]
# Manage config
mcporter config list
mcporter 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
Explains the idea itself. Read it slowly; the later sections build on it.
For persistent server connections:
mcporter daemon start
mcporter daemon status
mcporter daemon stop
mcporter daemon restartCode Generation
Explains the idea itself. Read it slowly; the later sections build on it.
# Generate a CLI wrapper for an MCP server
mcporter generate-cli --server <name>
mcporter generate-cli --command <url>
# Inspect a generated CLI
mcporter inspect-cli <path> [--json]
# Generate TypeScript types/client
mcporter emit-ts <server> --mode client
mcporter emit-ts <server> --mode typesNotes
Explains the idea itself. Read it slowly; the later sections build on it.
- 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