mcp-cli

Discover, inspect, and invoke MCP server tools from the command line.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill mcp-cli-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-cli
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/mcp-cli
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill mcp-cli-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interacting with Model Context Protocol servers normally requires writing client code or using a dedicated host application, making quick exploration and ad-hoc tool calls cumbersome. This Skill provides a direct command-line interface to list servers, inspect tool schemas, and execute MCP tools without boilerplate. ## Core Features & Use Cases - Server and Tool Discovery: List all configured MCP servers and their tools, search tools by name with glob patterns, and optionally include descriptions. - Schema Inspection: Retrieve the full JSON input schema for any tool before calling it, so arguments are always correctly structured. - Tool Execution with Scripting Support: Call tools with JSON arguments via inline strings, heredocs, or piped input, and get JSON or raw output for chaining with jq and shell pipelines. - Use Case: A developer wants to read a file through the filesystem MCP server: they run mcp-cli filesystem/read_file '{"path": "./README.md"}' and immediately get the result, then pipe JSON output into jq for further processing. ## Quick Start Ask the AI to list all available MCP servers and tools by running mcp-cli, then call a specific tool such as reading a file through the filesystem server.

Frequently Asked Questions about mcp-cli

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

FAQPage Schema
How do I list available MCP servers and tools from the command line?

Run mcp-cli with no arguments to list all configured servers and their tool names. Add a server name like mcp-cli filesystem to see tools with parameters, and append -d to include descriptions.

How do I call an MCP tool with JSON arguments?

Use the pattern mcp-cli server/tool '{"arg": "value"}' with a single-quoted JSON string. For complex JSON containing quotes, pipe input via heredoc or stdin, for example cat args.json | mcp-cli server/tool.

How can I get the input schema for an MCP tool before calling it?

Run mcp-cli server/tool without arguments, such as mcp-cli filesystem/read_file, to retrieve the tool's full JSON input schema. This shows required parameters and types so you can construct valid calls.

Can mcp-cli output be used in shell scripts and pipelines?

Yes, use the -j or --json flag for machine-readable JSON output and -r or --raw for raw text content. Output can be piped to tools like jq, for example extracting file paths from search results and passing them to read_file.

What do mcp-cli exit codes mean when a call fails?

Exit code 0 indicates success, 1 indicates a client error such as bad arguments or missing configuration, 2 indicates a server-side tool failure, and 3 indicates a network error. Scripts can branch on these codes for error handling.