mcporter

Manage MCP servers and call tools via a terminal interface.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill mcporter-devmoez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcporter
Source: https://github.com/devMoez/titan/tree/main/optional-skills/mcp/mcporter
Command: npx skills add https://github.com/devMoez/titan --skill mcporter-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of discovering, configuring, authenticating, and calling MCP (Model Context Protocol) servers/tools by letting you manage them directly from your terminal.

Core Features & Use Cases

  • MCP discovery & listing: Auto-discover MCP servers configured by other clients on the same machine, and list available tools with schema details.
  • Tool calling (HTTP or stdio): Invoke tools via configured servers, ad-hoc HTTP endpoints, or on-the-fly stdio servers, with support for structured JSON output.
  • Auth & configuration management: Perform OAuth login, manage server configuration, and run a daemon for persistent connections.
  • Code generation: Generate CLI wrappers and emit TypeScript clients/types from MCP server definitions.

Use case: You have an MCP tool that creates and queries issues; you want to list its available operations and then create an issue with validated parameters while returning machine-readable JSON for downstream automation.

Quick Start

Run mcporter call <server.tool> key=value --output json to call an MCP tool and get 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 terminal?▼

You can invoke MCP tools from the terminal by running a command with the server.tool name, passing arguments as key=value pairs, and using the --output json flag to receive deterministic JSON output for parsing.

What is Model Context Protocol discovery and how does it work?▼

Model Context Protocol discovery auto-detects MCP servers configured by other clients on the same machine and lists their available tools with schema details, simplifying terminal-based server management and tool invocation.

Can I use ad-hoc HTTP or stdio endpoints for MCP tool calling?▼

Yes, you can invoke MCP tools via configured servers, ad-hoc HTTP endpoints, or on-the-fly stdio servers, allowing flexible tool calling without requiring permanent server configurations.

Do I need Node.js to run MCP CLI integrations?▼

Yes, you need Node.js installed because MCP CLI integrations require Node.js execution, typically initiated via npx, to manage server configurations and invoke tools from the terminal.

How do I handle OAuth login for MCP servers in a CLI?▼

You can handle OAuth login for MCP servers directly in the CLI using the built-in authentication management features, which also support running a daemon for persistent server connections.

Can I generate TypeScript clients from MCP server definitions?▼

Yes, you can generate CLI wrappers and emit TypeScript clients and types from MCP server definitions, streamlining the integration of tool-calling workflows into automation pipelines.