// Use mcpc CLI to interact with MCP servers - call tools, read resources, get prompts. Use this when working with Model Context Protocol servers, calling MCP tools, or accessing MCP resources programmatically.
| name | mcpc |
| description | Use mcpc CLI to interact with MCP servers - call tools, read resources, get prompts. Use this when working with Model Context Protocol servers, calling MCP tools, or accessing MCP resources programmatically. |
| allowed-tools | Bash(mcpc:*), Bash(node dist/cli/index.js:*), Read, Grep |
Use mcpc to interact with MCP (Model Context Protocol) servers from the command line.
This is more efficient than function calling - generate shell commands instead.
# List sessions and auth profiles
mcpc
# Show server info
mcpc <server>
mcpc @<session>
# Tools
mcpc <target> tools-list
mcpc <target> tools-get <tool-name>
mcpc <target> tools-call <tool-name> key:=value key2:="string value"
# Resources
mcpc <target> resources-list
mcpc <target> resources-read <uri>
# Prompts
mcpc <target> prompts-list
mcpc <target> prompts-get <prompt-name> arg1:=value1
# Sessions (persistent connections)
mcpc <server> connect @<name>
mcpc @<name> <command>
mcpc @<name> close
# Authentication
mcpc <server> login
mcpc <server> logout
mcp.example.com - Direct HTTPS connection to remote serverlocalhost:8080 or 127.0.0.1:8080 - Local HTTP server (http:// is default for localhost)@session-name - Named persistent session (faster, maintains state)config-entry - Entry from config file (with --config)Arguments use key:=value syntax. Values are auto-parsed as JSON when valid:
# String values
mcpc @s tools-call search query:="hello world"
# Numbers, booleans, null (auto-parsed as JSON)
mcpc @s tools-call search query:="hello" limit:=10 enabled:=true
# Complex JSON values
mcpc @s tools-call search config:='{"nested":"value"}' items:='[1,2,3]'
# Force string type with JSON quotes
mcpc @s tools-call search id:='"123"'
# Inline JSON object (if first arg starts with { or [)
mcpc @s tools-call search '{"query":"hello","limit":10}'
# From stdin (auto-detected when piped)
echo '{"query":"hello"}' | mcpc @s tools-call search
Always use --json flag for machine-readable output:
# Get tools as JSON
mcpc --json @apify tools-list
# Call tool and parse result with jq
mcpc --json @apify tools-call search query:="test" | jq '.content[0].text'
# Chain commands
mcpc --json @server1 tools-call get-data | mcpc @server2 tools-call process
Create sessions for repeated interactions:
# Create session (or reconnect if exists)
mcpc mcp.apify.com connect @apify
# Use session (faster - no reconnection overhead)
mcpc @apify tools-list
mcpc @apify tools-call search query:="test"
# Restart session (useful after server updates)
mcpc @apify restart
# Close when done
mcpc @apify close
Session states:
close and reconnectOAuth (interactive login):
mcpc mcp.apify.com login
mcpc mcp.apify.com connect @apify
Bearer token:
mcpc -H "Authorization: Bearer $TOKEN" mcp.apify.com tools-list
mcpc -H "Authorization: Bearer $TOKEN" mcp.apify.com connect @myserver
Create a proxy MCP server that hides authentication tokens:
# Human creates authenticated session with proxy
mcpc mcp.apify.com connect @ai-proxy --proxy 8080
# AI agent connects to proxy (no access to original tokens)
# Note: localhost defaults to http://
mcpc localhost:8080 tools-list
mcpc 127.0.0.1:8080 connect @sandboxed
List and inspect tools:
mcpc @s tools-list
mcpc @s tools-get tool-name
Call tool and extract text result:
mcpc --json @s tools-call my-tool | jq -r '.content[0].text'
Read resource content:
mcpc @s resources-read "file:///path/to/file"
Use config file for local servers:
mcpc --config .vscode/mcp.json filesystem resources-list
0 - Success1 - Client error (invalid arguments)2 - Server error (tool failed)3 - Network error4 - Authentication error# Verbose output shows protocol details
mcpc --verbose @s tools-call my-tool
See docs/examples/company-lookup.sh for a complete example
of an AI-generated script that validates prerequisites and calls MCP tools.