mcporter

Manage MCP servers and invoke tools from a unified CLI.

247|22|Updated Dec 11, 2024
One-click install
npx skills add https://github.com/graniet/kheish --skill mcporter-graniet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcporter
Source: https://github.com/graniet/kheish/tree/main/skills/mcp/mcporter
Command: npx skills add https://github.com/graniet/kheish --skill mcporter-graniet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Working with Model Context Protocol (MCP) servers often requires manual configuration, client-specific setup, and fragmented access to tools, making it slow and error-prone to invoke MCP tools directly from the terminal for development or automation workflows.

Core Features & Use Cases

  • Unified MCP Server Management: List, configure, authenticate, and manage both locally configured and ad-hoc MCP servers (via HTTP or stdio) without editing config files manually.
  • Direct Tool Invocation: Auto-discover tools from configured MCP clients, view full tool schemas, and call tools with simple key=value or JSON syntax, with optional structured JSON output for automation.
  • Code Generation: Generate ready-to-use CLI wrappers and TypeScript client/types for MCP servers to integrate them into custom applications and workflows. For example, a developer can use this skill to quickly call a filesystem MCP server to read local project files, or authenticate with a project management MCP server to pull issue data directly into a terminal script.

Quick Start

Use the mcporter skill to list all MCP servers configured on your machine and call a tool from your preferred server with a single natural language command.

Frequently Asked Questions about mcporter

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

FAQPage Schema
How do I invoke MCP server tools directly from the terminal?

Yes, you can manage MCP servers with a single CLI that handles both locally configured and ad-hoc servers via HTTP or stdio. It allows you to list, configure, and authenticate connections without editing config files manually.

What is the best way to generate TypeScript clients for Model Context Protocol integrations?

The best way to generate TypeScript clients for Model Context Protocol integrations is using a CLI tool that produces ready-to-use wrappers and types. This allows developers to integrate MCP servers directly into custom applications.

Can I get structured JSON output from MCP tool calls for automation?

Yes, you can get structured JSON output from MCP tool calls for automation by enabling optional JSON output during invocation. This provides seamless integration into automated terminal pipelines and scripts.

Does Model Context Protocol support ad-hoc server connections without manual setup?

Yes, Model Context Protocol supports ad-hoc server connections without manual setup through a unified CLI. You can connect to servers via HTTP or stdio and invoke tools directly without editing configuration files.

How do I view tool schemas for a configured MCP client?

You can view tool schemas for a configured MCP client by using a CLI that auto-discovers tools from the server. This provides full visibility into available tools and their required parameters before invocation.