mcp-z-cli
@mcp-z/cli
Use a project's existing MCP configuration from a shell-capable agent, without writing a connection script. When the project selects CLI access, keep its calls on that route rather than substituting native agent MCP tools.
Run and locate configuration
Requires Node.js 20 or newer. For one-shot use:
npx -y @mcp-z/cli inspect --servers SERVER --tools
Alternatively, install with npm install -g @mcp-z/cli and use mcp-z or its alias z. The examples below use mcp-z; the remaining arguments are identical with either executable or the npx prefix. SERVER and TOOL are placeholders for discovered names, not built-in aliases.
With no --config, commands find the nearest .mcp.json from the current working directory upward, through the home directory inclusive. Outside the home directory tree, lookup checks only the current directory. Run from the intended project or its subdirectory; a nearer config takes precedence over a parent's. Configured child processes start with the config directory as their working directory.
Let that lookup select the project's ordinary .mcp.json; examples omit --config for this reason. Use --config when the task selects another configuration or needs an exact path: a bare filename such as .mcp.staging.json searches upward; ./.mcp.staging.json or an absolute path selects that exact file. Server names are keys under mcpServers. Inspect the relevant entry without exposing its credentials.