mcp-cli

Discover and invoke MCP servers on demand using the mcp CLI.

2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/tianzecn/myclaudecode --skill mcp-cli-tianzecn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-cli
Source: https://github.com/tianzecn/myclaudecode/tree/main/plugins/superpowers-lab/skills/mcp-cli
Command: npx skills add https://github.com/tianzecn/myclaudecode --skill mcp-cli-tianzecn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized workflow to dynamically discover and invoke MCP servers using the mcp CLI, enabling one-off checks and ad-hoc integrations without permanent hard-wiring.

Core Features & Use Cases

  • On-demand discovery: Discover available MCP tools and resources without permanent integrations.
  • One-off tool calls: Invoke a discovered MCP server for a single task or test.
  • Environment setup guidance: Clear steps to install and configure the mcp CLI and required servers.

Quick Start

Ensure the mcp binary is installed at ~/.local/bin/mcp, then use commands like mcp tools, mcp resources, and mcp prompts to explore and call MCP servers.

Frequently Asked Questions about mcp-cli

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

FAQPage Schema
How do I discover MCP tools and resources without permanent integration?

On-demand discovery with MCP lets you explore available tools and resources dynamically using the mcp CLI. Commands like `mcp tools` and `mcp resources` show what's available without pre-configuring integrations, letting you test and evaluate servers before committing to permanent setup.

Can I invoke MCP servers for one-off tasks without hardwiring them?

Yes, the mcp CLI enables temporary MCP server access for single tasks or tests. Invoke discovered servers on demand, execute parameterized calls, and switch between transport options without permanently wiring integrations into your system.

How do I set up the mcp CLI to start using MCP servers?

Install the mcp binary to ~/.local/bin/mcp, then use commands like `mcp tools`, `mcp resources`, and `mcp prompts` to explore and call MCP servers. The CLI provides immediate access to configured servers with built-in discovery and invocation workflows.

What's the difference between using MCP CLI for discovery versus permanent integrations?

MCP CLI handles ad-hoc exploration and testing without configuration overhead, while permanent integrations require upfront setup. Choose the CLI for one-off checks, debugging, and accessing unconfigured servers; use permanent integration when servers are part of your standard workflow.

Can I use MCP CLI to test servers before adding them to my workflow?

Yes, on-demand MCP server usage through the CLI is designed for testing and debugging. Discover tools, resources, and prompts from any server, execute parameterized calls, and validate behavior before committing to permanent integration.