mcporter

Invoke MCP servers and tools from the command line with JSON output.

641|104|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/eastreams/loong --skill mcporter-eastreams
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcporter
Source: https://github.com/eastreams/loong/tree/main/skills/mcporter
Command: npx skills add https://github.com/eastreams/loong --skill mcporter-eastreams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single terminal workflow for discovering, authenticating, configuring, and invoking MCP (Model Context Protocol) servers and tools, removing the friction of switching between GUIs, ad-hoc endpoints, and custom scripts.

Core Features & Use Cases

  • Discovery & Inspection: Auto-discovers local MCP servers and lists remote registries, including schema-aware tool listings for quick inspection.
  • Ad-hoc Connectivity: Connects to HTTP or stdio servers without config for one-off calls and testing.
  • Invocation & Structured Output: Calls tools with key=value or JSON payloads and supports machine-readable JSON output for automation and Hermes-style integrations.
  • Auth, Config & Daemon: Manages OAuth logins, editable config files, and a daemon mode for persistent connections; also generates CLIs and TypeScript clients for integrations.

Quick Start

Run npx mcporter list to discover MCP servers on your machine and then use mcporter call <server.tool> key=value --output json to invoke a tool and receive structured results.

Frequently Asked Questions about mcporter

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

FAQPage Schema
How do I call MCP server tools from the command line?▼

Call MCP server tools from the command line using npx mcporter call <server.tool> with key=value arguments or JSON payloads to invoke endpoints and receive structured results directly in your terminal.

What is the Model Context Protocol and when do I need a CLI for it?▼

The Model Context Protocol connects AI models to external tools, and a CLI is needed when you want to discover local servers, handle OAuth authentication, and run tool calls without switching to GUIs or custom scripts.

Can I connect to an ad-hoc HTTP or stdio MCP server without writing a config file?▼

Yes, you can connect to ad-hoc HTTP or stdio MCP servers without configuration for one-off calls and testing, allowing you to quickly invoke tools and inspect schemas on the fly.

Does mcporter support OAuth interactive authentication for MCP servers?▼

Yes, mcporter supports OAuth interactive authentication for MCP servers, managing logins and editable configuration files to securely handle connections requiring authorized access.

How do I generate TypeScript clients and CLIs for my MCP server integrations?▼

Generate TypeScript clients and CLIs for MCP server integrations using mcporter's code generation features, producing ready-to-use interfaces for your Node.js npx runtime workflows.

What are the limitations of using a daemonized CLI for persistent MCP connections?▼

Daemonized persistent connections optimize repeated MCP tool calls but require an active Node.js npx runtime environment, limiting usage in contexts where background processes are restricted.