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, list available MCP servers/tools, or call MCP tools from command line.
bunx add-skill github/awesome-copilot -s mcp-cliLoading…
Access MCP servers through the command line. MCP enables interaction with external systems like GitHub, filesystems, databases, and APIs.
| Command | Output |
|---|---|
mcp-cli | List all servers and tool names |
mcp-cli <server> | Show tools with parameters |
mcp-cli <server>/<tool> | Get tool JSON schema |
mcp-cli <server>/<tool> '<json>' | Call tool with arguments |
mcp-cli grep "<glob>" | Search tools by name |
Add -d to include descriptions (e.g., )
mcp-cli filesystem -dmcp-cli → see available servers and toolsmcp-cli <server> → see tools with parametersmcp-cli <server>/<tool> → get full JSON input schemamcp-cli <server>/<tool> '<json>' → run with arguments# List all servers and tool names
mcp-cli
# See all tools with parameters
mcp-cli filesystem
# With descriptions (more verbose)
mcp-cli filesystem -d
# Get JSON schema for specific tool
mcp-cli filesystem/read_file
# Call the tool
mcp-cli filesystem/read_file '{"path": "./README.md"}'
# Search for tools
mcp-cli grep "*file*"
# JSON output for parsing
mcp-cli filesystem/read_file '{"path": "./README.md"}' --json
# Complex JSON with quotes (use heredoc or stdin)
mcp-cli server/tool <<EOF
{"content": "Text with 'quotes' inside"}
EOF
# Or pipe from a file/command
cat args.json | mcp-cli server/tool
# Find all TypeScript files and read the first one
mcp-cli filesystem/search_files '{"path": "src/", "pattern": "*.ts"}' --json | jq -r '.content[0].text' | head -1 | xargs -I {} sh -c 'mcp-cli filesystem/read_file "{\"path\": \"{}\"}"'
| Flag | Purpose |
|---|---|
-j, --json | JSON output for scripting |
-r, --raw | Raw text content |
-d | Include descriptions |
0: Success1: Client error (bad args, missing config)2: Server error (tool failed)3: Network errorUse when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.