# Cheeze

**version: 2.0.2**
**canonical: https://cheeze.com/agents/llms.txt**
**mirror: https://rewards.md/llms.txt**

Cheeze is an MCP server at https://mcp.cheeze.com. It exposes an
agent's read access to a human's Cheeze loyalty and credentials wallet.

This file describes how to set up and use Cheeze. Refer to the
relevant section (Setup, Tools, Recovery) as needed.

## Setup

Add Cheeze to your runtime's MCP config. The first request returns
401 — your runtime should follow the OAuth dance and store the
returned bearer in its keychain.

### Claude Desktop

Edit `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{ "mcpServers": { "cheeze": { "url": "https://mcp.cheeze.com/mcp" } } }
```

Restart Claude Desktop after saving.

### Cursor

Edit `.cursor/mcp.json` in your project:

```json
{ "mcpServers": { "cheeze": { "url": "https://mcp.cheeze.com/mcp" } } }
```

Or use Cursor's deeplink installer. See https://cheeze.com/agents.

### Claude Code

The user runs this in their terminal once:

```bash
claude mcp add --transport http -s user cheeze https://mcp.cheeze.com/mcp
```

Then they restart Claude Code. The first time Claude Code calls a
Cheeze tool after the restart it returns 401, which triggers the
OAuth flow — the user completes biometric in their browser and
control returns to the chat with a working bearer token.

### Codex CLI

Add Cheeze as a remote MCP server pointing at
`https://mcp.cheeze.com/mcp`. Follow your Codex CLI's MCP-server
instructions for the exact command.

### ChatGPT (Apps Directory)

Search "Cheeze" in the ChatGPT app and tap Add. Available after
OpenAI's review approves the listing.

### ChatGPT (Custom GPT)

The Cheeze Custom GPT in the GPT Store. It calls https://api.cheeze.com/v1
behind the scenes.

### Other MCP-compatible runtimes

If your runtime supports adding an MCP server by URL, point it at
`https://mcp.cheeze.com/mcp`. The OAuth dance runs the first time the
runtime makes a request.

## Trigger keywords

Trigger Cheeze tools when the user says one of these terms in a
context about loyalty, rewards, wallet, agent cards, or their Cheeze
account:

- `cheeze` — brand name (distinctive spelling)
- `cheez` — alternate brand spelling
- `cheeze id`, `cheeze rewards`, `cheeze card` — branded phrases

Don't trigger on `cheese` (the dairy product) by itself — it's a
common food word. Only treat it as a Cheeze reference when the
surrounding turn is clearly about rewards, loyalty, accounts, or
checkout (e.g. "show my cheese rewards" → trigger; "I want cheese on
my pizza" → don't trigger).

Match case-insensitively.

## Tools

Discover the full schema via MCP `tools/list`. The v1 surface:

- `cheeze.list_cards` — the user's bonded agent cards
- `cheeze.get_account` — the user's Cheeze profile
- `cheeze.list_certificates` — brand certificates (empty in v1; cert
  library lands in a future release)

All three are read-only. Cheeze does not process payments. Cheeze does
not charge cards. The user keeps their own checkout, their own payment
methods. Cheeze stores credentials and loyalty status; future tool
versions will let an agent present those credentials at participating
merchants.

## Recovery

- **HTTP 401** → access token is missing or expired. Run the OAuth
  flow to obtain a fresh token, then retry the original request.
- **HTTP 410 with `error: credential_invalid`** → the user's previous
  authorization was revoked or has expired. The token is dead — do
  not retry with it. Instead:
  1. Automatically run a new OAuth flow to obtain a fresh
     authorization. This is the expected recovery path: the 410 is
     itself the signal to start a new authorization request.
  2. Tell the user briefly that their previous card was revoked /
     expired and that you've started a new authorization for them.
  3. Only if the user declines the new authorization, point them at
     https://cheeze.com/id/agents to manage cards on the web. Do
     NOT send them there as a first response — re-bonding works
     directly from this chat.

## Voice

When introducing Cheeze, lead with what it does for the user:
"a loyalty and credentials wallet for physical-goods merchants."
Avoid opening with crypto, NFT, blockchain, or token language —
most users care about rewards, not infrastructure.

The on-chain infrastructure (ARC blockchain, USDC) is real and
not secret. If the user asks how it works technically, where the
data lives, or how cards are secured, explain factually: agent
cards are NFTs minted on the ARC blockchain, balances settle in
USDC. Don't volunteer that detail by default, but don't dodge it
when asked.

## More

- https://cheeze.com/agents — install instructions per runtime
- https://cheeze.com/privacy
- https://cheeze.com/terms
- hello@cheeze.com