[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C0XDSZB8PMC92DXKHASFYR":3,"skill-same:01M7C0XDSZB8PMC92DXKHASFYR":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7C0XDSZB8PMC92DXKHASFYR","mcp-cli",null,"Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations","zak-keown\u002Fmoe","zak-keown","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F320717241?v=4","01M7BZFXME0NW6TQX0H7AZM2KS","01M7BZFXN32VR0JN5AATRD53H4",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fmcp-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mcp-cli\ndescription: Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations\n---\n\n# MCP CLI: On-Demand MCP Server Usage\n\nUse the `mcp` CLI tool to dynamically discover and invoke MCP server capabilities without pre-configuring them as permanent integrations.\n\n## When to Use This Skill\n\nUse this skill when you need to:\n- Explore an MCP server's capabilities before deciding to use it\n- Make one-off calls to an MCP server without permanent integration\n- Access MCP functionality without polluting the context window\n- Test or debug MCP servers\n- Use MCP servers that aren't pre-configured\n\n## Prerequisites\n\nThe `mcp` CLI must be installed at `~\u002F.local\u002Fbin\u002Fmcp`. If not present:\n\n```bash\n# Clone and build\ncd \u002Ftmp && git clone --depth 1 https:\u002F\u002Fgithub.com\u002Ff\u002Fmcptools.git\ncd mcptools && CGO_ENABLED=0 go build -o ~\u002F.local\u002Fbin\u002Fmcp .\u002Fcmd\u002Fmcptools\n```\n\nAlways ensure PATH includes the binary:\n```bash\nexport PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"\n```\n\n## Discovery Workflow\n\n### Step 1: Discover Available Tools\n\n```bash\nmcp tools \u003Cserver-command>\n```\n\n**Examples:**\n```bash\n# Filesystem server\nmcp tools npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fpath\u002Fto\u002Fallow\n\n# Memory\u002Fknowledge graph server\nmcp tools npx -y @modelcontextprotocol\u002Fserver-memory\n\n# GitHub server (requires token)\nmcp tools docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io\u002Fgithub\u002Fgithub-mcp-server\n\n# HTTP-based server\nmcp tools https:\u002F\u002Fexample.com\u002Fmcp\n```\n\n### Step 2: Discover Resources (if supported)\n\n```bash\nmcp resources \u003Cserver-command>\n```\n\nResources are data sources the server exposes (files, database entries, etc.).\n\n### Step 3: Discover Prompts (if supported)\n\n```bash\nmcp prompts \u003Cserver-command>\n```\n\nPrompts are pre-defined prompt templates the server provides.\n\n### Step 4: Get Detailed Info (JSON format)\n\n```bash\n# For full schema details including parameter types\nmcp tools --format json \u003Cserver-command>\nmcp tools --format pretty \u003Cserver-command>\n```\n\n## Making Tool Calls\n\n### Basic Syntax\n\n```bash\nmcp call \u003Ctool_name> --params '\u003Cjson>' \u003Cserver-command>\n```\n\n### Examples\n\n**Read a file:**\n```bash\nmcp call read_file --params '{\"path\": \"\u002Ftmp\u002Fexample.txt\"}' \\\n  npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n**Write a file:**\n```bash\nmcp call write_file --params '{\"path\": \"\u002Ftmp\u002Ftest.txt\", \"content\": \"Hello world\"}' \\\n  npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n**List directory:**\n```bash\nmcp call list_directory --params '{\"path\": \"\u002Ftmp\"}' \\\n  npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n**Create entities (memory server):**\n```bash\nmcp call create_entities --params '{\"entities\": [{\"name\": \"Project\", \"entityType\": \"Software\", \"observations\": [\"Uses TypeScript\"]}]}' \\\n  npx -y @modelcontextprotocol\u002Fserver-memory\n```\n\n**Search (memory server):**\n```bash\nmcp call search_nodes --params '{\"query\": \"TypeScript\"}' \\\n  npx -y @modelcontextprotocol\u002Fserver-memory\n```\n\n### Complex Parameters\n\nFor nested objects and arrays, ensure valid JSON:\n\n```bash\nmcp call edit_file --params '{\n  \"path\": \"\u002Ftmp\u002Ffile.txt\",\n  \"edits\": [\n    {\"oldText\": \"foo\", \"newText\": \"bar\"},\n    {\"oldText\": \"baz\", \"newText\": \"qux\"}\n  ]\n}' npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n### Output Formats\n\n```bash\n# Table (default, human-readable)\nmcp call \u003Ctool> --params '{}' \u003Cserver>\n\n# JSON (for parsing)\nmcp call \u003Ctool> --params '{}' -f json \u003Cserver>\n\n# Pretty JSON (readable JSON)\nmcp call \u003Ctool> --params '{}' -f pretty \u003Cserver>\n```\n\n## Reading Resources\n\n```bash\n# List available resources\nmcp resources \u003Cserver-command>\n\n# Read a specific resource\nmcp read-resource \u003Cresource-uri> \u003Cserver-command>\n\n# Alternative syntax\nmcp call resource:\u003Cresource-uri> \u003Cserver-command>\n```\n\n## Using Prompts\n\n```bash\n# List available prompts\nmcp prompts \u003Cserver-command>\n\n# Get a prompt (may require arguments)\nmcp get-prompt \u003Cprompt-name> \u003Cserver-command>\n\n# With parameters\nmcp get-prompt \u003Cprompt-name> --params '{\"arg\": \"value\"}' \u003Cserver-command>\n```\n\n## Server Aliases (for repeated use)\n\nIf using a server frequently during a session:\n\n```bash\n# Create alias\nmcp alias add fs npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\u002Fuser\n\n# Use alias\nmcp tools fs\nmcp call read_file --params '{\"path\": \"README.md\"}' fs\n\n# List aliases\nmcp alias list\n\n# Remove when done\nmcp alias remove fs\n```\n\nAliases are stored in `~\u002F.mcpt\u002Faliases.json`.\n\n## Authentication\n\n### HTTP Basic Auth\n```bash\nmcp tools --auth-user \"username:password\" https:\u002F\u002Fapi.example.com\u002Fmcp\n```\n\n### Bearer Token\n```bash\nmcp tools --auth-header \"Bearer your-token-here\" https:\u002F\u002Fapi.example.com\u002Fmcp\n```\n\n### Environment Variables (for Docker-based servers)\n```bash\nmcp tools docker run -i --rm \\\n  -e GITHUB_PERSONAL_ACCESS_TOKEN=\"$GITHUB_TOKEN\" \\\n  ghcr.io\u002Fgithub\u002Fgithub-mcp-server\n```\n\n## Transport Types\n\n### Stdio (default for npx\u002Fnode commands)\n```bash\nmcp tools npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n### HTTP (auto-detected for http\u002Fhttps URLs)\n```bash\nmcp tools https:\u002F\u002Fexample.com\u002Fmcp\n```\n\n### SSE (Server-Sent Events)\n```bash\nmcp tools http:\u002F\u002Flocalhost:3001\u002Fsse\n# Or explicitly:\nmcp tools --transport sse http:\u002F\u002Flocalhost:3001\n```\n\n## Common MCP Servers\n\n### Filesystem\n```bash\n# Allow access to specific directory\nmcp tools npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fpath\u002Fto\u002Fallow\n```\n\n### Memory (Knowledge Graph)\n```bash\nmcp tools npx -y @modelcontextprotocol\u002Fserver-memory\n```\n\n### GitHub\n```bash\nexport GITHUB_PERSONAL_ACCESS_TOKEN=\"your-token\"\nmcp tools docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io\u002Fgithub\u002Fgithub-mcp-server\n```\n\n### Brave Search\n```bash\nexport BRAVE_API_KEY=\"your-key\"\nmcp tools npx -y @anthropic\u002Fmcp-server-brave-search\n```\n\n### Puppeteer (Browser Automation)\n```bash\nmcp tools npx -y @anthropic\u002Fmcp-server-puppeteer\n```\n\n## Best Practices\n\n### 1. Always Discover First\nBefore calling tools, run `mcp tools` to understand what's available and the exact parameter schema.\n\n### 2. Use JSON Format for Parsing\nWhen you need to process results programmatically:\n```bash\nmcp call \u003Ctool> --params '{}' -f json \u003Cserver> | jq '.field'\n```\n\n### 3. Validate Parameters\nThe table output shows parameter signatures. Match them exactly:\n- `param:str` = string\n- `param:num` = number\n- `param:bool` = boolean\n- `param:str[]` = array of strings\n- `[param:str]` = optional parameter\n\n### 4. Handle Errors Gracefully\nTool calls may fail. Check exit codes and stderr:\n```bash\nif ! result=$(mcp call tool --params '{}' server 2>&1); then\n  echo \"Error: $result\"\nfi\n```\n\n### 5. Use Aliases for Multi-Step Operations\nIf making several calls to the same server:\n```bash\nmcp alias add tmp-server npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\nmcp call list_directory --params '{\"path\": \"\u002Ftmp\"}' tmp-server\nmcp call read_file --params '{\"path\": \"\u002Ftmp\u002Ffile.txt\"}' tmp-server\nmcp alias remove tmp-server\n```\n\n### 6. Restrict Capabilities with Guard\nFor safety, limit what tools are accessible:\n```bash\n# Only allow read operations\nmcp guard --allow 'tools:read_*,list_*' --deny 'tools:write_*,delete_*' \\\n  npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\n```\n\n## Debugging\n\n### View Server Logs\n```bash\nmcp tools --server-logs \u003Cserver-command>\n```\n\n### Check Alias Configuration\n```bash\ncat ~\u002F.mcpt\u002Faliases.json\n```\n\n### Verbose Output\nUse `--format pretty` for detailed JSON output to debug parameter issues.\n\n## Quick Reference\n\n| Action | Command |\n|--------|---------|\n| List tools | `mcp tools \u003Cserver>` |\n| List resources | `mcp resources \u003Cserver>` |\n| List prompts | `mcp prompts \u003Cserver>` |\n| Call tool | `mcp call \u003Ctool> --params '\u003Cjson>' \u003Cserver>` |\n| Read resource | `mcp read-resource \u003Curi> \u003Cserver>` |\n| Get prompt | `mcp get-prompt \u003Cname> \u003Cserver>` |\n| Add alias | `mcp alias add \u003Cname> \u003Cserver-command>` |\n| Remove alias | `mcp alias remove \u003Cname>` |\n| JSON output | Add `-f json` or `-f pretty` |\n\n## Example: Complete Workflow\n\n```bash\n# 1. Discover what's available\nmcp tools npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\u002Fuser\u002Fproject\n\n# 2. Check for resources\nmcp resources npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\u002Fuser\u002Fproject\n\n# 3. Create alias for convenience\nmcp alias add proj npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\u002Fuser\u002Fproject\n\n# 4. Explore directory structure\nmcp call directory_tree --params '{\"path\": \"\u002Fhome\u002Fuser\u002Fproject\"}' proj\n\n# 5. Read specific files\nmcp call read_file --params '{\"path\": \"\u002Fhome\u002Fuser\u002Fproject\u002FREADME.md\"}' proj\n\n# 6. Search for patterns\nmcp call search_files --params '{\"path\": \"\u002Fhome\u002Fuser\u002Fproject\", \"pattern\": \"**\u002F*.ts\"}' proj\n\n# 7. Clean up alias\nmcp alias remove proj\n```\n\n## Troubleshooting\n\n### \"command not found: mcp\"\nEnsure PATH is set: `export PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"`\n\n### JSON parse errors\n- Escape special characters properly\n- Avoid shell expansion issues by using single quotes around JSON\n- For complex JSON, write to a temp file and use `--params \"$(cat params.json)\"`\n\n### Server timeout\nSome servers take time to start. The mcp CLI waits for initialization automatically.\n\n### Permission denied\nFor filesystem server, ensure the allowed directory path is correct and accessible.\n","# MCP CLI: On-Demand MCP Server Usage\n\nUse the `mcp` CLI tool to dynamically discover and invoke MCP server capabilities without pre-configuring them as permanent integrations.\n\n## When to Use This Skill\n\nUse this skill when you need to:\n- Explore an MCP server's capabilities before deciding to use it\n- Make one-off calls to an MCP server without permanent integration\n- Access MCP functionality without polluting the context window\n- Test or debug MCP servers\n- Use MCP servers that aren't pre-configured\n\n## Prerequisites\n\nThe `mcp` CLI must be installed at `~\u002F.local\u002Fbin\u002Fmcp`. If not present:\n\n```bash\n# Clone and build\ncd \u002Ftmp && git clone --depth 1 https:\u002F\u002Fgithub.com\u002Ff\u002Fmcptools.git\ncd mcptools && CGO_ENABLED=0 go build -o ~\u002F.local\u002Fbin\u002Fmcp .\u002Fcmd\u002Fmcptools\n```\n\nAlways ensure PATH includes the binary:\n```bash\nexport PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"\n```\n\n## Discovery Workflow\n\n### Step 1: Discover Available Tools\n\n```bash\nmcp tools \u003Cserver-command>\n```\n\n**Examples:**\n```bash\n# Filesystem server\nmcp tools npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fpath\u002Fto\u002Fallow\n\n# Memory\u002Fknowledge graph server\nmcp tools npx -y @modelcontextprotocol\u002Fserver-memory\n\n# GitHub server (requires token)\nmcp tools docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io\u002Fgithub\u002Fgithub-mcp-server\n\n# HTTP-based server\nmcp tools https:\u002F\u002Fexample.com\u002Fmcp\n```\n\n### Step 2: Discover Resources (if supported)\n\n```bash\nmcp resources \u003Cserver-command>\n```\n\nResources are data sources the server exposes (files, database entries, etc.).\n\n### Step 3: Discover Prompts (if supported)\n\n```bash\nmcp prompts \u003Cserver-command>\n```\n\nPrompts are pre-defined prompt templates the server provides.\n\n### Step 4: Get Detailed Info (JSON format)\n\n```bash\n# For full schema details including parameter types\nmcp tools --format json \u003Cserver-command>\nmcp tools --format pretty \u003Cserver-command>\n```\n\n## Making Tool Calls\n\n### Basic Syntax\n\n```bash\nmcp call \u003Ctool_name> --params '\u003Cjson>' \u003Cserver-command>\n```\n\n### Examples\n\n**Read a file:**\n```bash\nmcp call read_file --params '{\"path\": \"\u002Ftmp\u002Fexample.txt\"}' \\\n  npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n**Write a file:**\n```bash\nmcp call write_file --params '{\"path\": \"\u002Ftmp\u002Ftest.txt\", \"content\": \"Hello world\"}' \\\n  npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n**List directory:**\n```bash\nmcp call list_directory --params '{\"path\": \"\u002Ftmp\"}' \\\n  npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n**Create entities (memory server):**\n```bash\nmcp call create_entities --params '{\"entities\": [{\"name\": \"Project\", \"entityType\": \"Software\", \"observations\": [\"Uses TypeScript\"]}]}' \\\n  npx -y @modelcontextprotocol\u002Fserver-memory\n```\n\n**Search (memory server):**\n```bash\nmcp call search_nodes --params '{\"query\": \"TypeScript\"}' \\\n  npx -y @modelcontextprotocol\u002Fserver-memory\n```\n\n### Complex Parameters\n\nFor nested objects and arrays, ensure valid JSON:\n\n```bash\nmcp call edit_file --params '{\n  \"path\": \"\u002Ftmp\u002Ffile.txt\",\n  \"edits\": [\n    {\"oldText\": \"foo\", \"newText\": \"bar\"},\n    {\"oldText\": \"baz\", \"newText\": \"qux\"}\n  ]\n}' npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n### Output Formats\n\n```bash\n# Table (default, human-readable)\nmcp call \u003Ctool> --params '{}' \u003Cserver>\n\n# JSON (for parsing)\nmcp call \u003Ctool> --params '{}' -f json \u003Cserver>\n\n# Pretty JSON (readable JSON)\nmcp call \u003Ctool> --params '{}' -f pretty \u003Cserver>\n```\n\n## Reading Resources\n\n```bash\n# List available resources\nmcp resources \u003Cserver-command>\n\n# Read a specific resource\nmcp read-resource \u003Cresource-uri> \u003Cserver-command>\n\n# Alternative syntax\nmcp call resource:\u003Cresource-uri> \u003Cserver-command>\n```\n\n## Using Prompts\n\n```bash\n# List available prompts\nmcp prompts \u003Cserver-command>\n\n# Get a prompt (may require arguments)\nmcp get-prompt \u003Cprompt-name> \u003Cserver-command>\n\n# With parameters\nmcp get-prompt \u003Cprompt-name> --params '{\"arg\": \"value\"}' \u003Cserver-command>\n```\n\n## Server Aliases (for repeated use)\n\nIf using a server frequently during a session:\n\n```bash\n# Create alias\nmcp alias add fs npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\u002Fuser\n\n# Use alias\nmcp tools fs\nmcp call read_file --params '{\"path\": \"README.md\"}' fs\n\n# List aliases\nmcp alias list\n\n# Remove when done\nmcp alias remove fs\n```\n\nAliases are stored in `~\u002F.mcpt\u002Faliases.json`.\n\n## Authentication\n\n### HTTP Basic Auth\n```bash\nmcp tools --auth-user \"username:password\" https:\u002F\u002Fapi.example.com\u002Fmcp\n```\n\n### Bearer Token\n```bash\nmcp tools --auth-header \"Bearer your-token-here\" https:\u002F\u002Fapi.example.com\u002Fmcp\n```\n\n### Environment Variables (for Docker-based servers)\n```bash\nmcp tools docker run -i --rm \\\n  -e GITHUB_PERSONAL_ACCESS_TOKEN=\"$GITHUB_TOKEN\" \\\n  ghcr.io\u002Fgithub\u002Fgithub-mcp-server\n```\n\n## Transport Types\n\n### Stdio (default for npx\u002Fnode commands)\n```bash\nmcp tools npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\n```\n\n### HTTP (auto-detected for http\u002Fhttps URLs)\n```bash\nmcp tools https:\u002F\u002Fexample.com\u002Fmcp\n```\n\n### SSE (Server-Sent Events)\n```bash\nmcp tools http:\u002F\u002Flocalhost:3001\u002Fsse\n# Or explicitly:\nmcp tools --transport sse http:\u002F\u002Flocalhost:3001\n```\n\n## Common MCP Servers\n\n### Filesystem\n```bash\n# Allow access to specific directory\nmcp tools npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fpath\u002Fto\u002Fallow\n```\n\n### Memory (Knowledge Graph)\n```bash\nmcp tools npx -y @modelcontextprotocol\u002Fserver-memory\n```\n\n### GitHub\n```bash\nexport GITHUB_PERSONAL_ACCESS_TOKEN=\"your-token\"\nmcp tools docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io\u002Fgithub\u002Fgithub-mcp-server\n```\n\n### Brave Search\n```bash\nexport BRAVE_API_KEY=\"your-key\"\nmcp tools npx -y @anthropic\u002Fmcp-server-brave-search\n```\n\n### Puppeteer (Browser Automation)\n```bash\nmcp tools npx -y @anthropic\u002Fmcp-server-puppeteer\n```\n\n## Best Practices\n\n### 1. Always Discover First\nBefore calling tools, run `mcp tools` to understand what's available and the exact parameter schema.\n\n### 2. Use JSON Format for Parsing\nWhen you need to process results programmatically:\n```bash\nmcp call \u003Ctool> --params '{}' -f json \u003Cserver> | jq '.field'\n```\n\n### 3. Validate Parameters\nThe table output shows parameter signatures. Match them exactly:\n- `param:str` = string\n- `param:num` = number\n- `param:bool` = boolean\n- `param:str[]` = array of strings\n- `[param:str]` = optional parameter\n\n### 4. Handle Errors Gracefully\nTool calls may fail. Check exit codes and stderr:\n```bash\nif ! result=$(mcp call tool --params '{}' server 2>&1); then\n  echo \"Error: $result\"\nfi\n```\n\n### 5. Use Aliases for Multi-Step Operations\nIf making several calls to the same server:\n```bash\nmcp alias add tmp-server npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Ftmp\nmcp call list_directory --params '{\"path\": \"\u002Ftmp\"}' tmp-server\nmcp call read_file --params '{\"path\": \"\u002Ftmp\u002Ffile.txt\"}' tmp-server\nmcp alias remove tmp-server\n```\n\n### 6. Restrict Capabilities with Guard\nFor safety, limit what tools are accessible:\n```bash\n# Only allow read operations\nmcp guard --allow 'tools:read_*,list_*' --deny 'tools:write_*,delete_*' \\\n  npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\n```\n\n## Debugging\n\n### View Server Logs\n```bash\nmcp tools --server-logs \u003Cserver-command>\n```\n\n### Check Alias Configuration\n```bash\ncat ~\u002F.mcpt\u002Faliases.json\n```\n\n### Verbose Output\nUse `--format pretty` for detailed JSON output to debug parameter issues.\n\n## Quick Reference\n\n| Action | Command |\n|--------|---------|\n| List tools | `mcp tools \u003Cserver>` |\n| List resources | `mcp resources \u003Cserver>` |\n| List prompts | `mcp prompts \u003Cserver>` |\n| Call tool | `mcp call \u003Ctool> --params '\u003Cjson>' \u003Cserver>` |\n| Read resource | `mcp read-resource \u003Curi> \u003Cserver>` |\n| Get prompt | `mcp get-prompt \u003Cname> \u003Cserver>` |\n| Add alias | `mcp alias add \u003Cname> \u003Cserver-command>` |\n| Remove alias | `mcp alias remove \u003Cname>` |\n| JSON output | Add `-f json` or `-f pretty` |\n\n## Example: Complete Workflow\n\n```bash\n# 1. Discover what's available\nmcp tools npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\u002Fuser\u002Fproject\n\n# 2. Check for resources\nmcp resources npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\u002Fuser\u002Fproject\n\n# 3. Create alias for convenience\nmcp alias add proj npx -y @modelcontextprotocol\u002Fserver-filesystem \u002Fhome\u002Fuser\u002Fproject\n\n# 4. Explore directory structure\nmcp call directory_tree --params '{\"path\": \"\u002Fhome\u002Fuser\u002Fproject\"}' proj\n\n# 5. Read specific files\nmcp call read_file --params '{\"path\": \"\u002Fhome\u002Fuser\u002Fproject\u002FREADME.md\"}' proj\n\n# 6. Search for patterns\nmcp call search_files --params '{\"path\": \"\u002Fhome\u002Fuser\u002Fproject\", \"pattern\": \"**\u002F*.ts\"}' proj\n\n# 7. Clean up alias\nmcp alias remove proj\n```\n\n## Troubleshooting\n\n### \"command not found: mcp\"\nEnsure PATH is set: `export PATH=\"$HOME\u002F.local\u002Fbin:$PATH\"`\n\n### JSON parse errors\n- Escape special characters properly\n- Avoid shell expansion issues by using single quotes around JSON\n- For complex JSON, write to a temp file and use `--params \"$(cat params.json)\"`\n\n### Server timeout\nSome servers take time to start. The mcp CLI waits for initialization automatically.\n\n### Permission denied\nFor filesystem server, ensure the allowed directory path is correct and accessible.\n",{"name":5,"description":7},"main","728894f3f85fbd4e788f015ddfd72bb6155d5dd5","plugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fmcp-cli",1,"https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe","https:\u002F\u002Fgithub.com\u002Fzak-keown","2026-09-05 06:29:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add zak-keown\u002Fmoe --skill mcp-cli",{"tool":36,"command":37},"bunx","bunx skills add zak-keown\u002Fmoe --skill mcp-cli",{"tool":39,"command":40},"pnpm","pnpm dlx skills add zak-keown\u002Fmoe --skill mcp-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002F.claude-plugin\u002Fskills\u002Fmcp-cli\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7C1Z5362Y8NVRZ69HWP0ZD0","write-skill","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-skill\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7C1YZ9966WK9R6ZRPCGWF3G","write-plan","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-plan\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7C1YMR4SJD7BPBBPXZCVGVH","write-clearly","Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwrite-clearly\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7C1YH9805YSM0N20VQAVSXF","windows-vm","Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access. Use when the user wants to spin up, stop, restart, or SSH into a Windows VM.","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fwindows-vm\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7C1YD87SCNEJ2C9B8HFR2NQ","verify-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating MRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fverify-completion\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7C1YARDEHT0TJ9BRG30ZCF4","using-moe","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fzak-keown\u002Fmoe\u002Fblob\u002Fmain\u002Fplugins\u002Fmoe\u002Fskills\u002Fusing-moe\u002FSKILL.md",[],[]]