mcporter

Discover, configure, and invoke MCP servers and tools from the terminal.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/KarlinskyS/hermesSkills --skill mcporter-karlinskys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcporter
Source: https://github.com/KarlinskyS/hermesSkills/tree/main/mcp/mcporter
Command: npx skills add https://github.com/KarlinskyS/hermesSkills --skill mcporter-karlinskys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover, configure, and call MCP servers and tools directly from the terminal, eliminating manual setup and scattered workflows.

Core Features & Use Cases

  • List MCP servers configured on the machine and inspect tool schemas.
  • Call MCP tools and ad-hoc servers via HTTP or stdio with structured arguments.
  • Generate CLI wrappers and TypeScript types from MCP server definitions to automate tooling.

Quick Start

Install and run mcporter to discover MCP servers, view tools, and call a tool with key=value pairs.

Frequently Asked Questions about mcporter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage and call MCP servers from the terminal?

You can manage MCP servers from the terminal by using a CLI tool to discover configured servers, inspect tool schemas, and invoke tools with structured key=value arguments. It supports both HTTP and stdio server protocols.

Can I generate TypeScript types and CLI wrappers from MCP server definitions?

Yes, you can generate TypeScript types and CLI wrappers from MCP server definitions. This automates tooling setup by creating structured code artifacts directly from the discovered server schemas.

Do I need Node.js to run MCP server management commands via CLI?

Yes, you need Node.js installed to run MCP server management commands via CLI. The tool executes through npx, requiring a valid Node.js environment to discover and invoke local or ad-hoc servers.

What's the best way to inspect MCP tool schemas before invoking them?

The best way to inspect MCP tool schemas is using a terminal-based discovery command that lists configured servers and outputs their tool schemas. This eliminates manual setup and prevents scattered workflow errors.

How do I call an ad-hoc MCP tool with structured arguments from the command line?

You call an ad-hoc MCP tool from the command line by passing structured key=value pairs as arguments to the CLI. The tool supports both HTTP and stdio transports for invoking servers directly.

Does this CLI approach work with both HTTP and stdio MCP servers?

Yes, this CLI approach works with both HTTP and stdio MCP servers. It automates configuration and invocation for local or ad-hoc workflows, allowing you to list servers and call tools regardless of the transport protocol.