Schema | MCPay

MCPay

Describes the environment variables required to run the server.

Name	Required	Description
`MCPAY_TARGET`	No	The upstream MCP server URL that the gateway proxies to (e.g., https://your-mcp-server.example).
`MCPAY_MCP_PATH`	No	The MCP endpoint path on the upstream server (default is /mcp).
`MCPAY_SERVER_ID`	No	The server identifier issued by the MCPay dashboard (e.g., srv_example).
`MCPAY_USAGE_API`	No	The usage records API endpoint (e.g., https://api.example/v1/usage-records).
`MCPAY_STATE_FILE`	No	Path to a persistent state file for the gateway (e.g., ./mcpay-gateway.db).
`MCPAY_ENVIRONMENT`	No	The environment name (e.g., beta).
`MCPAY_TOKEN_ISSUER`	No	The token issuer identifier (e.g., mcpay.beta).
`MCPAY_NONCE_CLAIM_API`	No	The nonce claim API endpoint (e.g., https://api.example/v1/gateway/nonces/claim).
`MCPAY_USAGE_API_TOKEN`	No	API token for the usage records endpoint. Provided as $MCPAY_GATEWAY_API_TOKEN in the README.
`MCPAY_CONTROL_PLANE_API`	No	The control-plane API URL for fetching gateway configuration (e.g., https://api.example/v1/gateway/servers/srv_example).
`MCPAY_VERIFICATION_KEYS`	No	Verification keys for token signature validation, used when no control-plane API is provided.

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

ActivityActive

ResponsivenessNo issues