Docs: https://mcp-z.github.io/cli MCP server lifecycle management and inspection from the command line.
.mcp.jsonserver.jsonnpm install -g @mcp-z/cli
{
"mcpServers": {
"my-server": {
"command": "node",
"args": ["path/to/server.js"]
}
}
}
mcp-z up
{
"mcpServers": {
"my-server": {
"type": "http",
"url": "http://localhost:3000/mcp"
}
}
}
mcp-z up
{
"mcpServers": {
"my-server": {
"type": "http",
"url": "http://localhost:3000/mcp",
"start": {
"command": "node",
"args": ["path/to/http-server.js"]
}
}
}
}
start is an extension used by npx @mcp-z/cli up to launch HTTP servers for you.
mcp-z upStart MCP servers from .mcp.json.
Common use cases:
start blocksmcp-z inspectInspect tools, resources, prompts, and health.
Common use cases:
mcp-z call-toolCall a tool with JSON arguments.
Common use cases:
mcp-z get-promptGet a prompt with optional JSON arguments.
Common use cases:
mcp-z read-resourceRead a resource by URI.
Common use cases:
mcp-z searchSearch tools, prompts, and resources across servers.
Common use cases:
mcp-z manifestGenerate or validate server.json.
Common use cases:
# Stdio
mcp-z inspect --run "npx -y @modelcontextprotocol/server-everything"
# HTTP
mcp-z inspect --url "https://api.example.com/mcp"
MCP server config supports stdio and HTTP.
Stdio
{
"command": "node",
"args": ["server.js"],
"env": { "LOG_LEVEL": "info" }
}
HTTP
{
"type": "http",
"url": "http://localhost:3000/mcp",
"headers": { "Authorization": "Bearer token" }
}