mcp-cli

Manage MCP servers and invoke their tools via CLI JSON payloads.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Typeless-Git/skills --skill mcp-cli-typeless-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-cli
Source: https://github.com/Typeless-Git/skills/tree/main/mcp-cli
Command: npx skills add https://github.com/Typeless-Git/skills --skill mcp-cli-typeless-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interact with MCP servers from the command line to manage external tools, APIs, and data sources more efficiently.

Core Features & Use Cases

  • Discover MCP servers and list available tools.
  • Explore tools with parameters and their JSON schemas.
  • Execute a tool by providing a JSON payload from the CLI.

Quick Start

Use mcp-cli to discover MCP servers, list tools, and call a tool with a JSON payload.

Frequently Asked Questions about mcp-cli

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

FAQPage Schema
How do I interact with MCP servers from the command line?

You can interact with MCP servers from the command line using the mcp-cli command to discover servers, list available tools, inspect JSON schemas, and invoke tools with a serialized JSON payload.

What's the best way to discover available tools on an MCP server?

The best way to discover available tools on an MCP server is using the mcp-cli command, which lists tools along with their parameters and allows you to inspect each tool's JSON schema.

Can I invoke an MCP tool by passing a JSON payload via the CLI?

Yes, you can invoke an MCP tool via the CLI by executing the tool with a serialized JSON payload, passing optional JSON output flags to format the response.

Do I need a specific file structure to use mcp-cli for server automation?

Yes, using mcp-cli requires a SKILL.md frontmatter file containing the name and description at the root directory to properly configure and execute server automation tasks.

Why am I unable to inspect a tool's parameters when managing MCP servers?

You may be unable to inspect a tool's parameters if the server connection fails or the tool lacks a defined JSON schema, which mcp-cli relies on to list parameters and execute commands.