agentleFS
philschmidphilschmid/mcp-cli/SKILL.md

mcp-cli

Skill1.3k starsChanged 10 months agoMITView on GitHub

Interface for MCP (Model Context Protocol) servers via CLI. Use when you need to interact with external tools, APIs, or data sources through MCP servers.

9 other projects use a version of this, 6 of them edited.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 10 mentionsFeb 2026: 3 mentionsMar 2026: 1 mentionApr 2026: 1 mentionMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the philschmid/mcp-cli repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about philschmid/mcp-cli

The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 18

Talked about on GitHub, Bluesky and Hacker News (18 times).

On GitHub · 15

10 more on GitHub

On Hacker News · 1

The file

Files
SKILL.md

MCP-CLI

Access MCP servers through the command line. MCP enables interaction with external systems like GitHub, filesystems, databases, and APIs.

Commands

CommandOutput
mcp-cliList all servers and tools
mcp-cli info <server>Show server tools and parameters
mcp-cli info <server> <tool>Get tool JSON schema
mcp-cli grep "<pattern>"Search tools by name
mcp-cli call <server> <tool>Call tool (reads JSON from stdin if no args)
mcp-cli call <server> <tool> '<json>'Call tool with arguments

Both formats work: <server> <tool> or <server>/<tool>

Workflow

  1. Discover: mcp-cli → see available servers
  2. Explore: mcp-cli info <server> → see tools with parameters
  3. Inspect: mcp-cli info <server> <tool> → get full JSON schema
  4. Execute: mcp-cli call <server> <tool> '<json>' → run with arguments

Examples

# List all servers
mcp-cli

# With descriptions  
mcp-cli -d

# See server tools
mcp-cli info filesystem

# Get tool schema (both formats work)
mcp-cli info filesystem read_file
mcp-cli info filesystem/read_file

# Call tool
mcp-cli call filesystem read_file '{"path": "./README.md"}'

# Pipe from stdin (no '-' needed!)
cat args.json | mcp-cli call filesystem read_file

# Search for tools
mcp-cli grep "*file*"

# Output is raw text (pipe-friendly)
mcp-cli call filesystem read_file '{"path": "./file"}' | head -10

Advanced Chaining

# Chain: search files → read first match
mcp-cli call filesystem search_files '{"path": ".", "pattern": "*.md"}' \
  | head -1 \
  | xargs -I {} mcp-cli call filesystem read_file '{"path": "{}"}'

# Loop: process multiple files
mcp-cli call filesystem list_directory '{"path": "./src"}' \
  | while read f; do mcp-cli call filesystem read_file "{\"path\": \"$f\"}"; done

# Conditional: check before reading
mcp-cli call filesystem list_directory '{"path": "."}' \
  | grep -q "README" \
  && mcp-cli call filesystem read_file '{"path": "./README.md"}'

# Multi-server aggregation
{
  mcp-cli call github search_repositories '{"query": "mcp", "per_page": 3}'
  mcp-cli call filesystem list_directory '{"path": "."}'
}

# Save to file
mcp-cli call github get_file_contents '{"owner": "x", "repo": "y", "path": "z"}' > output.txt

Note: call outputs raw text content directly (no jq needed for text extraction)

Options

FlagPurpose
-dInclude descriptions
-c <path>Specify config file

Common Errors

Wrong CommandErrorFix
mcp-cli server toolAMBIGUOUS_COMMANDUse call server tool or info server tool
mcp-cli run server toolUNKNOWN_SUBCOMMANDUse call instead of run
mcp-cli listUNKNOWN_SUBCOMMANDUse info instead of list
mcp-cli call serverMISSING_ARGUMENTAdd tool name
mcp-cli call server tool {bad}INVALID_JSONUse valid JSON with quotes

Exit Codes

  • 0: Success
  • 1: Client error (bad args, missing config)
  • 2: Server error (tool failed)
  • 3: Network error

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.