Schema | Portage-UCP

Portage-UCP

Describes the environment variables required to run the server.

Name	Required	Description
`NO_PROXY`	No	Standard fallback proxy exclusion variable: anything left unconfigured falls back to the standard HTTPS_PROXY/HTTP_PROXY/NO_PROXY variables, except payment traffic, which goes direct unless you name a proxy for it.
`HTTP_PROXY`	No	Standard fallback proxy variable: anything left unconfigured falls back to the standard HTTPS_PROXY/HTTP_PROXY/NO_PROXY variables, except payment traffic, which goes direct unless you name a proxy for it.
`HTTPS_PROXY`	No	Standard fallback proxy variable: anything left unconfigured falls back to the standard HTTPS_PROXY/HTTP_PROXY/NO_PROXY variables, except payment traffic, which goes direct unless you name a proxy for it.
`PORTAGE_PROXY`	No	Proxy settings supplied as PORTAGE_PROXY* environment variables (equivalent to the --proxy* flags and the "proxy" section of ~/.portage/config.json). Applies to buy, find, compare, check, doctor and payment enroll.
`PORTAGE_UCP_CONFIG`	No	Hook used by the adapter gem's exe/ server (the merchant-side MCP/UCP server) to load the store configuration. Each adapter gem (portage-ucp-shopify, portage-ucp-wix, portage-ucp-woocommerce, portage-ucp-bigcommerce, portage-ucp-magento, portage-ucp-etsy, portage-ucp-instagram) ships an exe/ server and the PORTAGE_UCP_CONFIG hook, with a shared examples/portage_ucp.rb starting point; it points at the Adapter subclass and its store credentials.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed