Schema | CraveUp MCP Server

CraveUp MCP Server

Official

Describes the environment variables required to run the server.

Name	Required	Description	Default
`EXPO_TOKEN`	No	Scoped Expo robot-user token. Required only for mobile release tools.
`CRAVEUP_API_KEY`	No	Merchant API key. Must match the environment prefix (crv_test_ for sandbox, crv_live_ for production). Used for menu, discount, and readiness tools.
`CRAVEUP_ENVIRONMENT`	Yes	Required. The environment selects all dashboard, API, and Clerk hosts together. Must be 'sandbox' or 'production'.
`CRAVEUP_LOCATION_ID`	No	Optional default location ID. Every tool also accepts an explicit locationId.
`CRAVEUP_ACCESS_TOKEN`	No	Optional alternative to the keychain session. A session token for CLI/MCP shared browser authentication.
`CRAVEUP_ALLOW_CUSTOM_ENDPOINTS`	No	Set to 'true' to allow custom deployments with endpoint overrides. Normally unnecessary.	false

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

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/craveup/craveup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server