Preview, draft, and publish an MCP

Review the operations and authentication of a standalone MCP deployment before making it callable.

 
elva --collection "Orders API" mcp create \
  --name "Orders MCP" --operations "GET /orders" \
  --auth-type bearer --dry-run

Use operation keys exactly as returned by collection endpoints. Repeat --operations for multiple keys, or use --operations - for a JSON list on stdin. Omitting the operations filter can expose the entire collection. Set authentication explicitly; the default no-auth setting is suitable only for intentionally public APIs.

 
elva --collection "Orders API" --yes mcp create \
  --name "Orders MCP" --operations "GET /orders" \
  --auth-type bearer --draft
elva mcp list
elva mcp show orders-mcp

Use the actual slug returned by creation in subsequent commands. --dry-run saves nothing; --draft reserves a server slot and saves configuration without publishing. These two options cannot be combined. --base-url overrides the upstream target and --timeout accepts a request budget from 1000 to 300000 milliseconds.

 
elva --yes mcp publish orders-mcp
elva mcp show orders-mcp

Use the returned runtime URL and install-page instructions to connect a client. Confirm the tools and make a read-only test call. Contract-generated MCP servers must be published through their parent contract so approval and governance checks apply.