Documentation Index
Fetch the complete documentation index at: https://mintlify.com/superradcompany/tool-cli/llms.txt
Use this file to discover all available pages before exploring further.
tool info shows everything a tool exposes: its available tools, prompts, and resources. This is what MCP clients see when they connect.
tool info # inspect tool in current directory
tool info appcypher/bash # inspect installed tool
tool info appcypher/bash -c # concise output
tool info . -m exec # show specific method details
tool info . -m exec -m read # show multiple methods
tool info . -m exec --input # show only input schema
tool info . -m exec --output # show only output schema
tool info . -m exec -d # show only description
tool info . --tools # list tools only
tool info . --prompts # list prompts only
tool info . --resources # list resources only
tool info . -a # show all capabilities
tool info . --json # JSON output for parsing
tool info . -k API_KEY=xxx # pass config value inline
tool info . -L 5 # expand nested types to depth 5
Call a method
tool call invokes any method directly from the terminal. No MCP client required. Parameters are passed as KEY=VALUE pairs.
tool call . -m exec -p command="ls" # call method in current dir
tool call bash -m exec -p cmd="pwd" # call method with param
tool call bash -m exec -p cmd=ls # use -p flag for params
tool call weather -m get -p loc=NYC # unquoted param value
tool call api -m query -k KEY=xxx # pass config inline
tool call . -m test --config-file ./creds.json # config from file
tool call . -m run -y # skip interactive prompts
tool call . -m debug -v # verbose output
Method shorthand
MCP tools often name their methods using toolname__method convention. You can use . as shorthand for the tool name prefix, saving you from typing the full compound name.
# .exec expands to bash__exec
tool call bash -m .exec -p command="ls -la"
# .fs.read expands to files__fs__read
tool call files -m .fs.read -p path="/tmp"
The .method shorthand is especially useful when a tool name is long or when you’re scripting calls against multiple tools.
tool run starts a tool as an MCP server so any MCP client can connect to it.
tool run # run tool in current directory
tool run appcypher/bash # run installed tool
tool run . -k API_KEY=xxx # pass config value
tool run . --config-file creds.json # config from file
tool run . -v # verbose output
Transport bridging
By default tool run uses the tool’s native transport. Use --expose to bridge between transports — for example, to make a stdio-based tool available over HTTP, or to wrap a remote HTTP server in a stdio interface.
# Bridge a remote HTTP MCP server to a local stdio interface
tool run ns/remote-mcp --expose stdio
Transport bridging lets you connect stdio-only clients to HTTP servers and vice versa without changing the tool itself.