CLI Mode
CLI mode is activated by passing a subcommand (tool, resource, or prompt) after the connection flags.
mcp-tui [connection-flags] <subcommand> [args]# list available toolsmcp-tui --cmd npx --args "@modelcontextprotocol/server-everything,stdio" tool list
# describe one toolmcp-tui ... tool describe echo
# call a tool with key=value argsmcp-tui ... tool call echo message='hello'

Resources
Section titled “Resources”mcp-tui ... resource listmcp-tui ... resource read 'file:///example.txt'Prompts
Section titled “Prompts”mcp-tui ... prompt listmcp-tui ... prompt get my-prompt arg=valueArgument coercion
Section titled “Argument coercion”Strings are passed verbatim. Numeric, boolean, and JSON-shaped values are coerced based on the tool’s input schema:
# auto-coercedmcp-tui ... tool call sum a=1 b=2mcp-tui ... tool call enabled flag=truemcp-tui ... tool call query filter='{"limit":10}'If schema coercion is wrong, force a string with key:str=value (planned).
Exit codes
Section titled “Exit codes”| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | Connection failure |
| 2 | Invalid arguments / usage |
| 3 | Tool / resource not found |
| 4 | Tool execution error |
| 5 | Protocol error |
See Automation & CI for pipeline patterns.