output_path

MCP tool from MCP Zero by zeromicro

(optional): Output file path (uses defaults based on template type)

How to use it

output_path is exposed by the MCP Zero MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the output_path tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

FULL MCP ZERO LISTING

Other tools in MCP Zero (22)

(optional): Type of analysis - "api", "rpc", "model", or "full" (default: "full")

(required): Path to the .api specification file

(optional): Configuration type - "dev", "test", or "prod" (default: "dev")

(required): Content to validate

(optional): Documentation type - "concept", "migration", or "both" (default: "both")

(required): Array of endpoint objects with method, path, and handler

(required): Input type - "apispec", "proto", or "config"

Edit ~/Library/Application Support/Claude/claudedesktopconfig.json:

(optional): Output directory (default: current directory)

(optional): Output file path (default: servicename.api)

(optional): Port number (default: 8888)

(required): Path to the project directory

(required): Protobuf definition content

(required): Natural language query about go-zero concepts or migration

(required): Name of the API service

(required): Service type - "api" or "rpc"

(required): Database connection string or DDL file path

(required): Source type - "mysql", "postgresql", "mongo", or "ddl"

(optional): Enable strict validation mode (default: false)

(optional): Code style - "gozero" or "gozero" (default: "gozero")

(optional): Specific table name (for database sources)

(required): Template type - "middleware", "errorhandler", "dockerfile", "dockercompose", or "kubernetes"