ThriveCart MCP Server &amp; CLI

Add it with a single command in a terminal.

Put your own API token in place of the example.

claude mcp add thrivecart \
  -e THRIVECART_API_KEY=your-api-key \
  -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
In Claude Code, type /mcp. ThriveCart should show as connected.
```
/mcp
```

Add it with a single command in a terminal.

Put your own API token in place of the example.

claude mcp add thrivecart -e THRIVECART_API_KEY="your-api-key" -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
In Claude Code, type /mcp. ThriveCart should show as connected.
```
/mcp
```

Add it with a single command in a terminal.

Put your own API token in place of the example.

claude mcp add thrivecart \
  -e THRIVECART_API_KEY=your-api-key \
  -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
In Claude Code, type /mcp. ThriveCart should show as connected.
```
/mcp
```

Your computer

Add it with a single command in a terminal.

Put your own API token in place of the example.

codex mcp add thrivecart \
  --env THRIVECART_API_KEY=your-api-key \
  -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
Check that Codex lists it.
```
codex mcp list
```

Add it with a single command in a terminal.

Put your own API token in place of the example.

codex mcp add thrivecart --env THRIVECART_API_KEY="your-api-key" -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
Check that Codex lists it.
```
codex mcp list
```

Add it with a single command in a terminal.

Put your own API token in place of the example.

codex mcp add thrivecart \
  --env THRIVECART_API_KEY=your-api-key \
  -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
Check that Codex lists it.
```
codex mcp list
```

1
Open Cursor's settings, go to the MCP tab, and click Add new global MCP server.

Add the server.

Put your own API token in place of the example.

{
  "mcpServers": {
    "thrivecart": {
      "command": "npx",
      "args": ["-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "env": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

3
Open the MCP tab again. It should show 24 tools.

1
Open the Command Palette and run MCP: Open User Configuration.

Add the server to that mcp.json.

If the file already has servers, add only this one inside servers. Put your own API token in place of the example.

{
  "servers": {
    "thrivecart": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "env": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

Your computer

Add it with a single command in a terminal.

Put your own API token in place of the example.

copilot mcp add thrivecart \
  --env THRIVECART_API_KEY=your-api-key \
  -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
Check that Copilot CLI has it.
```
copilot mcp get thrivecart
```

Add it with a single command in a terminal.

Put your own API token in place of the example.

copilot mcp add thrivecart --env THRIVECART_API_KEY="your-api-key" -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
Check that Copilot CLI has it.
```
copilot mcp get thrivecart
```

Add it with a single command in a terminal.

Put your own API token in place of the example.

copilot mcp add thrivecart \
  --env THRIVECART_API_KEY=your-api-key \
  -- npx -y @thenavidm/thrivecart-mcp-cli@latest

2
Check that Copilot CLI has it.
```
copilot mcp get thrivecart
```

Your computer

1
Open your Gemini CLI settings.
```
~/.gemini/settings.json
```

Add the server to settings.json.

If the file already has servers, add only this one inside mcpServers. Put your own API token in place of the example.

{
  "mcpServers": {
    "thrivecart": {
      "command": "npx",
      "args": ["-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "env": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

3
Restart Gemini CLI and type /mcp to check it.
```
/mcp
```

1
Open your Gemini CLI settings.
```
%USERPROFILE%\.gemini\settings.json
```

Add the server to settings.json.

If the file already has servers, add only this one inside mcpServers. Put your own API token in place of the example.

{
  "mcpServers": {
    "thrivecart": {
      "command": "npx",
      "args": ["-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "env": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

3
Restart Gemini CLI and type /mcp to check it.
```
/mcp
```

1
Open your Gemini CLI settings.
```
~/.gemini/settings.json
```

Add the server to settings.json.

If the file already has servers, add only this one inside mcpServers. Put your own API token in place of the example.

{
  "mcpServers": {
    "thrivecart": {
      "command": "npx",
      "args": ["-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "env": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

3
Restart Gemini CLI and type /mcp to check it.
```
/mcp
```

Your computer

1
Open your OpenCode config.
```
~/.config/opencode/opencode.json
```

Add the server under mcp.

If the file already has servers, add only this one inside mcp. Put your own API token in place of the example.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thrivecart": {
      "type": "local",
      "command": ["npx", "-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "enabled": true,
      "environment": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

3
Restart OpenCode.

Open your OpenCode config.

%USERPROFILE%\.config\opencode\opencode.json

Add the server under mcp.

If the file already has servers, add only this one inside mcp. Put your own API token in place of the example.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thrivecart": {
      "type": "local",
      "command": ["npx", "-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "enabled": true,
      "environment": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

3
Restart OpenCode.

1
Open your OpenCode config.
```
~/.config/opencode/opencode.json
```

Add the server under mcp.

If the file already has servers, add only this one inside mcp. Put your own API token in place of the example.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thrivecart": {
      "type": "local",
      "command": ["npx", "-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "enabled": true,
      "environment": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

3
Restart OpenCode.

Your computer

Add it with a single command in a terminal.

Put your own API token in place of the example.

openclaw mcp add thrivecart \
  --command npx \
  --arg -y \
  --arg @thenavidm/thrivecart-mcp-cli@latest \
  --env THRIVECART_API_KEY=your-api-key

2
Check that it starts and lists its tools.
```
openclaw mcp doctor thrivecart --probe
```

Add it with a single command in a terminal.

Put your own API token in place of the example.

openclaw mcp add thrivecart --command npx --arg -y --arg @thenavidm/thrivecart-mcp-cli@latest --env THRIVECART_API_KEY="your-api-key"

2
Check that it starts and lists its tools.
```
openclaw mcp doctor thrivecart --probe
```

Add it with a single command in a terminal.

Put your own API token in place of the example.

openclaw mcp add thrivecart \
  --command npx \
  --arg -y \
  --arg @thenavidm/thrivecart-mcp-cli@latest \
  --env THRIVECART_API_KEY=your-api-key

2
Check that it starts and lists its tools.
```
openclaw mcp doctor thrivecart --probe
```

1
In the agent panel, click the … menu, then MCP Servers, Manage MCP Servers and View raw config.

Add the server to mcp_config.json.

If the file already has servers, add only this one inside mcpServers. Put your own API token in place of the example.

{
  "mcpServers": {
    "thrivecart": {
      "command": "npx",
      "args": ["-y", "@thenavidm/thrivecart-mcp-cli@latest"],
      "env": {
        "THRIVECART_API_KEY": "your-api-key"
      }
    }
  }
}

Your computer

1
Open your Hermes config.
```
~/.hermes/config.yaml
```

Add the server under mcp_servers.

If the file already has mcp_servers, add only this one under it. Put your own API token in place of the example.

mcp_servers:
  thrivecart:
    command: "npx"
    args: ["-y", "@thenavidm/thrivecart-mcp-cli@latest"]
    env:
      THRIVECART_API_KEY: "your-api-key"

1
Open your Hermes config.
```
%USERPROFILE%\.hermes\config.yaml
```

Add the server under mcp_servers.

If the file already has mcp_servers, add only this one under it. Put your own API token in place of the example.

mcp_servers:
  thrivecart:
    command: "npx"
    args: ["-y", "@thenavidm/thrivecart-mcp-cli@latest"]
    env:
      THRIVECART_API_KEY: "your-api-key"

1
Open your Hermes config.
```
~/.hermes/config.yaml
```

Add the server under mcp_servers.

If the file already has mcp_servers, add only this one under it. Put your own API token in place of the example.

mcp_servers:
  thrivecart:
    command: "npx"
    args: ["-y", "@thenavidm/thrivecart-mcp-cli@latest"]
    env:
      THRIVECART_API_KEY: "your-api-key"

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give Claude Code the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Claude Code what each command does and which ones ask first.
```
mkdir -p ~/.claude/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.claude/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Claude Code to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Claude Code finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

Give Claude Code the skill, so it knows every command.

The skill is the SKILL.md in the package. It tells Claude Code what each command does and which ones ask first.

New-Item -ItemType Directory -Force "$HOME\.claude\skills\thrivecart" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\thrivecart-mcp-cli\SKILL.md" "$HOME\.claude\skills\thrivecart\"

3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Claude Code to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Claude Code finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give Claude Code the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Claude Code what each command does and which ones ask first.
```
mkdir -p ~/.claude/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.claude/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Claude Code to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Claude Code finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give Codex the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Codex what each command does and which ones ask first.
```
mkdir -p ~/.agents/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.agents/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Codex to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Codex finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

Give Codex the skill, so it knows every command.

The skill is the SKILL.md in the package. It tells Codex what each command does and which ones ask first.

New-Item -ItemType Directory -Force "$HOME\.agents\skills\thrivecart" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\thrivecart-mcp-cli\SKILL.md" "$HOME\.agents\skills\thrivecart\"

3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Codex to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Codex finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give Codex the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Codex what each command does and which ones ask first.
```
mkdir -p ~/.agents/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.agents/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Codex to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Codex finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Cursor to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Cursor finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Cursor to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Cursor finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Cursor to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Cursor finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask VS Code to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so VS Code finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask VS Code to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so VS Code finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask VS Code to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so VS Code finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give Copilot CLI the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Copilot CLI what each command does and which ones ask first.
```
mkdir -p ~/.copilot/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.copilot/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Copilot CLI to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Copilot CLI finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

Give Copilot CLI the skill, so it knows every command.

The skill is the SKILL.md in the package. It tells Copilot CLI what each command does and which ones ask first.

New-Item -ItemType Directory -Force "$HOME\.copilot\skills\thrivecart" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\thrivecart-mcp-cli\SKILL.md" "$HOME\.copilot\skills\thrivecart\"

3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Copilot CLI to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Copilot CLI finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give Copilot CLI the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Copilot CLI what each command does and which ones ask first.
```
mkdir -p ~/.copilot/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.copilot/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask Copilot CLI to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Copilot CLI finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Gemini CLI to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Gemini CLI finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Gemini CLI to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Gemini CLI finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Gemini CLI to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Gemini CLI finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give OpenCode the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenCode what each command does and which ones ask first.
```
mkdir -p ~/.config/opencode/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.config/opencode/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask OpenCode to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so OpenCode finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

Give OpenCode the skill, so it knows every command.

The skill is the SKILL.md in the package. It tells OpenCode what each command does and which ones ask first.

New-Item -ItemType Directory -Force "$HOME\.config\opencode\skills\thrivecart" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\thrivecart-mcp-cli\SKILL.md" "$HOME\.config\opencode\skills\thrivecart\"

3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask OpenCode to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so OpenCode finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give OpenCode the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenCode what each command does and which ones ask first.
```
mkdir -p ~/.config/opencode/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.config/opencode/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask OpenCode to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so OpenCode finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give OpenClaw the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenClaw what each command does and which ones ask first.
```
mkdir -p ~/.openclaw/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.openclaw/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask OpenClaw to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so OpenClaw finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

Give OpenClaw the skill, so it knows every command.

The skill is the SKILL.md in the package. It tells OpenClaw what each command does and which ones ask first.

New-Item -ItemType Directory -Force "$HOME\.openclaw\skills\thrivecart" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\thrivecart-mcp-cli\SKILL.md" "$HOME\.openclaw\skills\thrivecart\"

3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask OpenClaw to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so OpenClaw finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Give OpenClaw the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenClaw what each command does and which ones ask first.
```
mkdir -p ~/.openclaw/skills/thrivecart
cp "$(npm root -g)/@thenavidm/thrivecart-mcp-cli/SKILL.md" ~/.openclaw/skills/thrivecart/
```
3
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
4
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
5
Ask OpenClaw to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so OpenClaw finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Antigravity to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Antigravity finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Antigravity to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Antigravity finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Antigravity to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Antigravity finds the one it needs.

Your computer

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Hermes to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Hermes finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Hermes to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Hermes finds the one it needs.

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```
4
Ask Hermes to use thrivecart-cli.
Running thrivecart-cli on its own lists every command, so Hermes finds the one it needs.

Your computer

Sales page teardown Pricing page teardown Grand slam offer generator Value ladder generator Profit margin calculator Stripe fee calculator

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.zshrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```

List every command, then try one.

thrivecart-cli
thrivecart-cli list-products

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
setx THRIVECART_API_KEY "your-api-key"
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```

List every command, then try one.

thrivecart-cli
thrivecart-cli list-products

Install the CLI. It needs Node 22 or newer.

npm install -g @thenavidm/thrivecart-mcp-cli@latest

2
Save your ThriveCart details, so every new session has them.
Put your own API token in place of the example.
```
echo 'export THRIVECART_API_KEY=your-api-key' >> ~/.bashrc
```
3
Check your setup.
It names anything that's wrong and the fix.
```
thrivecart-cli doctor
```

List every command, then try one.

thrivecart-cli
thrivecart-cli list-products

Needs Node 22 or newer and an API token from your ThriveCart dashboard. Get one in a minute.

It's free and open source. If it saves you time, star it on GitHub, so more people find it.

Rate this tool

This free ThriveCart MCP server and CLI gives your AI real access to your ThriveCart carts. It reads products, transactions, revenue, customers, subscriptions and affiliates, across several carts at once.

It's one install with two ways in. Claude, Codex, Cursor or any other MCP app calls its 24 tools for you, and the same tools work as a CLI that agents like Claude Code, Codex and OpenCode run, or that you type yourself.

In this guide, I'll show you:

What the ThriveCart MCP server & CLI is, and what you can ask it
How to install it and check that it works
When to use the MCP server, and when the CLI
Every tool, and how to keep your account safe

Every tool on this page comes from the server itself, and every cost was measured in Claude Code.

key_takeaways.md

TL;DR

Key takeaways

It gives your AI 24 tools for your ThriveCart carts: products, transactions, revenue, customers, subscriptions and affiliates.

It works across several carts at once.

Refunds and cancellations wait for your approval, because neither can be undone.

The same tools run as a CLI, which costs your AI nothing until it runs.

What is the ThriveCart MCP server & CLI?

The ThriveCart MCP server & CLI is a free, open source program that lets AI agents work with your ThriveCart carts for you, in two ways. The MCP server is what an AI app like Claude, Codex or Cursor connects to, through MCP (Model Context Protocol), the open standard AI apps use to call outside tools.

You ask in plain language. Your AI picks the right tool, and the server makes the call to ThriveCart's API.

The CLI is the same program as commands. thrivecart-cli get-revenue-summary runs the same code your AI runs when you ask how a quarter went, whether an agent like Claude Code runs it or you do.

In an AI OS, the layer that connects your AI to your context, your data and your tools, a server like this is how your AI reaches ThriveCart. I explain how the parts fit together in how to build an AI operating system, and here's how I use AI myself.

What can you ask it?

Once it's set up, you ask the way you'd ask an assistant. These are real prompts it handles:

Try asking
Revenue by product last quarter, compared to the quarter before.
How much of my revenue comes from bumps and upsells rather than the main products?
Find every customer who bought the bundle but never the course.
What is this person paying right now, and is anything paused?
Which affiliates drove real revenue this year, not just clicks?
Compare both my carts side by side, kept separate.

The last one shows why this is useful. Each cart stays separate, and every tool takes an account, so nothing gets quietly added together.

It works well next to my Kit MCP server and WordPress MCP server, so your AI can email your buyers and update your sales pages in the same chat. Every server I've made is on my MCP servers page.

For your offers, my free sales page teardown and pricing page teardown help too. I compare ThriveCart with the alternatives in the best shopping cart software and the best sales funnel software.

How to install the ThriveCart MCP server

Pick your app in the box at the top of this page. Each one is a single command or a pasted block, and they all run through npx, so there's nothing to install first.

Windsurf, Zed and Cline take the same server, though they don't have a tab in the box yet. Follow the box's Cursor tab, and put its block here instead:

App	Where the block goes
Windsurf	In the Cascade panel, open the Actions menu (…) and choose Open MCP config file, then paste the block.
Cline	Click the MCP Servers icon in the Cline panel, open the Configure tab, click Configure MCP Servers, and paste the block.
Zed	Go to Settings, then AI, then MCP Servers, and choose Add Server, then Add Local Server. Enter the block's command, arguments and variables, and Zed saves them under `context_servers`.

Before you start0/4

You use an AI app that speaks MCP, like Claude Code, Codex or Cursor. Here's how to install Claude Code if you don't have one yet.

You have Node 22 or newer on your computer.

You have a ThriveCart account.

You have an API token from that account.

Set up your ThriveCart account

ThriveCart uses a plain API token. There's no sign-in flow and nothing to renew.

Get your API token0/4

1Open your ThriveCart dashboard.

2Go to Settings, then API & webhooks, then API tokens.

3Create a token and copy it.

4Put it in the command for your app, in place of the example.

That token reaches everything in that one cart, refunds included, so treat it like a password. Each cart needs its own token.

ThriveCart allows 60 requests a minute per cart. The server spaces its requests a second apart by default, so you shouldn't hit that.

Check that it works

Run the doctor. It checks each cart on its own and tells you the fix, not an error code.

THRIVECART_API_KEY=your-api-key npx -y @thenavidm/thrivecart-mcp-cli doctor

When every line says ok, restart your app and ask for last month's revenue.

In Claude Code, /mcp also shows whether the ThriveCart server is connected. It's one of the Claude Code commands worth knowing.

Use the ThriveCart CLI

The CLI is the same 24 tools as commands. AI agents that run commands, like Claude Code, Codex and OpenCode, use it on their own, and you can type the same commands in a terminal or a script.

Every tool name becomes a command with dashes, so get_revenue_summary runs as thrivecart-cli get-revenue-summary.

npm install -g @thenavidm/thrivecart-mcp-cli
thrivecart-cli
thrivecart-cli list-products
thrivecart-cli get-revenue-summary

The bare thrivecart-cli lists every command, thrivecart-cli which <words> finds the command for a task, and thrivecart-cli <command> --help shows what a command takes. Refunding and cancelling need --confirm, the terminal's version of your approval.

thrivecart-cli install <app> adds the server to Claude Code, Codex, Claude Desktop, Cursor, VS Code or Gemini CLI, in each app's own format.

These are the flags you'll use most:

Flag	What it does
`--json`	Prints JSON
`--compact`	Prints the JSON on one line
`--select a,b.c`	Keeps only those fields, and a dotted path goes deeper
`--agent`	Machine mode: compact JSON, no prompts, and it never confirms anything
`--confirm`	Lets a write that asks first go ahead
`--dry-run`	Shows what a write would do, without doing it

A script can branch on the exit code:

Exit code	What it means
0	It worked
1	Something unexpected went wrong
2	The command was typed wrong, or a write needed `--confirm`
3	It wasn't found
4	ThriveCart rejected the credentials
5	ThriveCart failed or couldn't be reached
7	You hit a rate limit, so wait and try again
10	Nothing is set up yet

MCP server or CLI: which one?

Both are the same program with the same 24 tools. The difference is when your AI pays for them, in the tokens it reads.

Every message, in an app that loads every tool

MCP server: 7,200 tokens
CLI: Nothing

Every message, in Claude Code

MCP server: 910 tokens
CLI: Nothing

When ThriveCart comes up

MCP server: Nothing more, or in Claude Code the tools it picks
CLI: 3,800 tokens, once

20 messages with ThriveCart in one, every tool loaded

MCP server: 144,000 tokens
CLI: 3,800 tokens

Works in Claude Desktop's chat

MCP server: Yes
CLI: No, there's no terminal there

Works in a script, a cron job or CI

MCP server: No
CLI: Yes

What it costs	MCP server	CLI
Every message, in an app that loads every tool	7,200 tokens	Nothing
Every message, in Claude Code	910 tokens	Nothing
When ThriveCart comes up	Nothing more, or in Claude Code the tools it picks	3,800 tokens, once
20 messages with ThriveCart in one, every tool loaded	144,000 tokens	3,800 tokens
Works in Claude Desktop's chat	Yes	No, there's no terminal there
Works in a script, a cron job or CI	No	Yes

An app that loads every tool up front sends the full list with every message, whether you mention ThriveCart or not. Claude Code doesn't by default: its tool search sends only the tool names and the server's instructions, and loads a tool's full definition when your AI reaches for it.

The CLI costs nothing until ThriveCart comes up. Then your agent reads its skill file once and runs the commands it needs. With the skill added, Claude Code also lists its one-line description with every message, about 170 tokens.

When the whole conversation is about ThriveCart, the gap closes. Then the MCP server is the better experience, because you ask in plain language and your AI never has to look up a command.

Where the MCP server's tokens go

Part of the tool list	Share
JSON Schema structure, like types, required lists and nesting	52%
Argument descriptions	25%
Tool descriptions	23%

52% of it is MCP writing every tool out as JSON Schema, which any server with this many tools pays. The rest is the wording that lets your AI use each tool without guessing.

How to spend less

In Claude Code, leave tool search on, which it is unless you've set ENABLE_TOOL_SEARCH=false.

Turn the server off when you aren't using ThriveCart. In Claude Code that's the /mcp panel, and every AI app has its own switch. THRIVECART_READ_ONLY=1 cuts it to the 19 reading tools.

Or install the CLI and connect the server later, on the days it earns its place. Every tool stays in reach, and the standing cost drops to nothing.

Every number here was measured on October 5, 2026 in Claude Code 2.1.286 with Claude Opus 5.5. It's the same one-line prompt with and without the server connected, once with tool search off so every tool loads, and once with Claude Code's default. The skill was measured the same way, and other apps and models count tokens a little differently.

Every ThriveCart tool

The tables below list all 24 tools, grouped the way the repo groups them. Of these, 19 only read, and five change something in your carts.

Revenue and transactions

get_transactions

What it does: Get transactions from a ThriveCart account, with optional date and product-name filtering.
Kind: Reads

get_revenue_summary

What it does: Revenue for a date range, grouped by product and sorted highest first, for one ThriveCart account.
Kind: Reads

Tool	What it does	Kind
`get_transactions`	Get transactions from a ThriveCart account, with optional date and product-name filtering.	Reads
`get_revenue_summary`	Revenue for a date range, grouped by product and sorted highest first, for one ThriveCart account.	Reads

Products

list_products

What it does: List every product on a ThriveCart account, with ids and names.
Kind: Reads

get_product

What it does: Get the full details of one product by id.
Kind: Reads

get_product_pricing

What it does: Get every price point configured on a product: one-time, split pay and subscription.
Kind: Reads

Tool	What it does	Kind
`list_products`	List every product on a ThriveCart account, with ids and names.	Reads
`get_product`	Get the full details of one product by id.	Reads
`get_product_pricing`	Get every price point configured on a product: one-time, split pay and subscription.	Reads

Bumps, upsells and downsells

list_bumps

What it does: List every bump across all products on a ThriveCart account.
Kind: Reads

get_bump

What it does: Get the full details of one bump by id, including what it offers and at what price.
Kind: Reads

get_bump_pricing

What it does: Get every price point configured on one bump.
Kind: Reads

list_upsells

What it does: List every upsell across all products on a ThriveCart account.
Kind: Reads

get_upsell

What it does: Get the full details of one upsell by id, including what it offers and at what price.
Kind: Reads

get_upsell_pricing

What it does: Get every price point configured on one upsell.
Kind: Reads

list_downsells

What it does: List every downsell across all products on a ThriveCart account.
Kind: Reads

get_downsell

What it does: Get the full details of one downsell by id, including what it offers and at what price.
Kind: Reads

get_downsell_pricing

What it does: Get every price point configured on one downsell.
Kind: Reads

Tool	What it does	Kind
`list_bumps`	List every bump across all products on a ThriveCart account.	Reads
`get_bump`	Get the full details of one bump by id, including what it offers and at what price.	Reads
`get_bump_pricing`	Get every price point configured on one bump.	Reads
`list_upsells`	List every upsell across all products on a ThriveCart account.	Reads
`get_upsell`	Get the full details of one upsell by id, including what it offers and at what price.	Reads
`get_upsell_pricing`	Get every price point configured on one upsell.	Reads
`list_downsells`	List every downsell across all products on a ThriveCart account.	Reads
`get_downsell`	Get the full details of one downsell by id, including what it offers and at what price.	Reads
`get_downsell_pricing`	Get every price point configured on one downsell.	Reads

Customers

get_customer

What it does: Get one customer's full record by email address: their purchases, subscriptions and order ids.
Kind: Reads

Tool	What it does	Kind
`get_customer`	Get one customer's full record by email address: their purchases, subscriptions and order ids.	Reads

Subscriptions and refunds

pause_subscription

What it does: Pause a customer's subscription, stopping future billing while keeping the subscription itself.
Kind: Writes

resume_subscription

What it does: Resume a paused subscription, restarting billing.
Kind: Writes

cancel_subscription

What it does: Cancel a customer's subscription permanently.
Kind: Asks first

refund_transaction

What it does: Refund a transaction, returning the money to the customer.
Kind: Asks first

Tool	What it does	Kind
`pause_subscription`	Pause a customer's subscription, stopping future billing while keeping the subscription itself.	Writes
`resume_subscription`	Resume a paused subscription, restarting billing.	Writes
`cancel_subscription`	Cancel a customer's subscription permanently.	Asks first
`refund_transaction`	Refund a transaction, returning the money to the customer.	Asks first

Affiliates

search_affiliates

What it does: List affiliates on a ThriveCart account, one page at a time.
Kind: Reads

get_affiliate

What it does: Get one affiliate's full record by email: their referrals, commissions and payout details.
Kind: Reads

create_affiliate

What it does: Register a new affiliate on a ThriveCart account.
Kind: Writes

Tool	What it does	Kind
`search_affiliates`	List affiliates on a ThriveCart account, one page at a time.	Reads
`get_affiliate`	Get one affiliate's full record by email: their referrals, commissions and payout details.	Reads
`create_affiliate`	Register a new affiliate on a ThriveCart account.	Writes

Accounts

list_accounts

What it does: List every ThriveCart account configured on this server.
Kind: Reads

whoami

What it does: Fetch the ThriveCart account this key belongs to, including the owner email and account details.
Kind: Reads

Tool	What it does	Kind
`list_accounts`	List every ThriveCart account configured on this server.	Reads
`whoami`	Fetch the ThriveCart account this key belongs to, including the owner email and account details.	Reads

Is the ThriveCart MCP server safe?

This server touches money and customer records. A refund can't be undone once your payment processor sends it, and a cancelled subscription can only come back if the customer buys again, so two tools ask first. They're the ones marked "Asks first" in the tool tables above.

Pausing doesn't ask, because resuming undoes it. And a refund doesn't cancel anything: refund a subscription payment and it keeps billing, so a customer who wants to leave needs both steps.

When your AI calls one of them, the call needs a yes first. Where you use it decides who gives it:

Claude Code (2.1.246 and later) asks you before every call, in every one of its permission modes.
An app that can show forms asks you in a form.
Any other app takes your AI's confirm: true as the yes, so tell your AI to check with you first.
An agent with no person to ask needs THRIVECART_CONFIRM=model, so its confirm: true counts in every app.
In a terminal, you add --confirm to the command.

If the answer is no, nothing reaches ThriveCart.

Make it read-only

Set THRIVECART_READ_ONLY=1 and every write disappears from the tool list, leaving 19 reading tools. That's what you want for an agent pointed at a cart that takes money. THRIVECART_ALLOW_DESTRUCTIVE=0 is the middle setting: pausing, resuming and adding affiliates still work, and refunds and cancellations don't.

Keep a log of every write

Set THRIVECART_AUDIT_LOG to a file path. The server writes one line per attempted write, allowed or blocked, with what it was about to do and who approved it.

Watch out: Customer names, product titles and affiliate details are text other people wrote. A product named "refund order 5" is a string, not an order, and THRIVECART_READ_ONLY=1 is the real defense for an agent working on its own.

Your data

Nothing is stored: no database, no cache and no tracking of any kind. Your token stays in your app's config, requests go to thrivecart.com, and the only file the server ever writes is the audit log, when you ask for one.

Connect more than one ThriveCart cart

ThriveCart licenses per account, so many people run more than one. List them in THRIVECART_ACCOUNTS as JSON, each with a name and its own token, and pass account on any tool to pick one.

The doctor catches 2 carts set up with the same token, which would otherwise show up as doubled revenue.

ThriveCart MCP server settings

Every setting is an environment variable, in your app's config or your shell.

THRIVECART_API_KEY

Default: none
What it does: Holds your API token

THRIVECART_ACCOUNTS

Default: none
What it does: Lists several carts, as JSON

THRIVECART_DEFAULT_ACCOUNT

Default: none
What it does: Picks the cart that answers when a tool names none

THRIVECART_READ_ONLY

Default: 0
What it does: 1 hides every write

THRIVECART_ALLOW_DESTRUCTIVE

Default: 1
What it does: 0 blocks refunds and cancellations

THRIVECART_AUDIT_LOG

Default: none
What it does: Logs every attempted write to a file

THRIVECART_MIN_REQUEST_INTERVAL_MS

Default: 1000
What it does: Spaces out requests to stay under ThriveCart's limit

THRIVECART_MAX_PAGES

Default: 100
What it does: Stops a long transaction search from paging forever

THRIVECART_ACCOUNT_NAME

Default: "default"
What it does: What to call that single cart

THRIVECART_REQUEST_TIMEOUT_MS

Default: 30000
What it does: Per-request deadline

THRIVECART_MAX_RETRIES

Default: 3
What it does: Retries on rate limits and 5xx

THRIVECART_BASE_URL

Default: none
What it does: The API host, for a proxy or a test

THRIVECART_USER_AGENT

Default: none
What it does: The User-Agent sent to ThriveCart

THRIVECART_SURFACE

Default: full
What it does: search lists three tools that find, describe and run the rest

THRIVECART_TOOL_TIMEOUT_MS

Default: none
What it does: Gives up on any tool after this many milliseconds

THRIVECART_CONFIRM

Default: human
What it does: model lets your AI's confirm: true approve on its own, for an agent with no person to ask

THRIVECART_HTTP_PORT

Default: 8788
What it does: Sets the port for --http

THRIVECART_HTTP_HOST

Default: 127.0.0.1
What it does: Sets the address for --http, and any other needs a token

THRIVECART_HTTP_TOKEN

Default: none
What it does: Sets the bearer token every --http request needs

THRIVECART_HTTP_ALLOWED_ORIGINS

Default: none
What it does: Lists other websites allowed to call --http, comma separated

THRIVECART_DEBUG

Default: off
What it does: 1 prints debug lines

Variable	Default	What it does
`THRIVECART_API_KEY`	none	Holds your API token
`THRIVECART_ACCOUNTS`	none	Lists several carts, as JSON
`THRIVECART_DEFAULT_ACCOUNT`	none	Picks the cart that answers when a tool names none
`THRIVECART_READ_ONLY`	`0`	`1` hides every write
`THRIVECART_ALLOW_DESTRUCTIVE`	`1`	`0` blocks refunds and cancellations
`THRIVECART_AUDIT_LOG`	none	Logs every attempted write to a file
`THRIVECART_MIN_REQUEST_INTERVAL_MS`	`1000`	Spaces out requests to stay under ThriveCart's limit
`THRIVECART_MAX_PAGES`	`100`	Stops a long transaction search from paging forever
`THRIVECART_ACCOUNT_NAME`	`"default"`	What to call that single cart
`THRIVECART_REQUEST_TIMEOUT_MS`	`30000`	Per-request deadline
`THRIVECART_MAX_RETRIES`	`3`	Retries on rate limits and 5xx
`THRIVECART_BASE_URL`	none	The API host, for a proxy or a test
`THRIVECART_USER_AGENT`	none	The User-Agent sent to ThriveCart
`THRIVECART_SURFACE`	`full`	`search` lists three tools that find, describe and run the rest
`THRIVECART_TOOL_TIMEOUT_MS`	none	Gives up on any tool after this many milliseconds
`THRIVECART_CONFIRM`	`human`	`model` lets your AI's `confirm: true` approve on its own, for an agent with no person to ask
`THRIVECART_HTTP_PORT`	`8788`	Sets the port for `--http`
`THRIVECART_HTTP_HOST`	`127.0.0.1`	Sets the address for `--http`, and any other needs a token
`THRIVECART_HTTP_TOKEN`	none	Sets the bearer token every `--http` request needs
`THRIVECART_HTTP_ALLOWED_ORIGINS`	none	Lists other websites allowed to call `--http`, comma separated
`THRIVECART_DEBUG`	off	`1` prints debug lines

Troubleshooting

Run the doctor first. It names the step that failed and the fix.

What you see	What to do
"key rejected"	Use an API token from Settings, API & webhooks, not your account password
Everything returns 404	Something is pointed at api.thrivecart.com. The API lives at thrivecart.com/api/external
Revenue looks too low	Without `fetch_all`, `get_transactions` returns one page, and the result says so
Revenue looks doubled	2 carts use the same token. Run the doctor
A truncation warning	It reached `THRIVECART_MAX_PAGES`. Narrow the dates or raise the limit
`thrivecart-cli: command not found`	npm's global folder isn't on your PATH. Use the npx form instead

If the server doesn't show up in your app at all, run the command your app runs, in a terminal, and read the error.

More free tools for selling

Tag the links you share so you can check what sent buyers, or make a QR code for an offer.

Free tools

MCP servers

Kit MCP server & CLI WordPress MCP server & CLI

FAQs about the ThriveCart MCP server & CLI

Here are the questions people ask most about the ThriveCart MCP server and CLI.

What is the ThriveCart MCP server & CLI?

The ThriveCart MCP server & CLI is a free, open source program that lets an AI app like Claude, Codex or Cursor work with your ThriveCart carts.

It has 24 tools for products, bumps, upsells, transactions, revenue, customers, subscriptions and affiliates, and the same tools run as a CLI that agents like Claude Code and Codex use, or that you type yourself.

What is an MCP server?

An MCP server is a standard way to give an AI app real access to a tool, so it can act instead of guessing.

MCP stands for Model Context Protocol, and Claude, Codex, Cursor and many other AI apps speak it.

Every server I've made is on my MCP servers page.

What is the ThriveCart CLI?

The ThriveCart CLI is the same program as the ThriveCart MCP server, run as commands.

AI agents like Claude Code, Codex and OpenCode run them for you, and you can type them in a terminal or a script.

One npm package installs both.

Should I use the ThriveCart MCP server or the CLI?

Use the ThriveCart MCP server in an AI app with no terminal, like Claude Desktop's chat, and the CLI in a terminal, a script or a cron job.

In an AI app that can run commands, like Claude Code, Codex or Cursor, the CLI is the lighter choice, because it costs nothing until it runs.

Is the ThriveCart MCP server free?

Yes, the ThriveCart MCP server is free and open source under the MIT license.

ThriveCart's API comes with your account, so the only thing you pay for is your own AI app.

Do I need a ThriveCart account?

Yes, the ThriveCart MCP server works with your own ThriveCart account and an API token from it.

If you don't have ThriveCart yet, you can get a ThriveCart account here.

Does the ThriveCart MCP server need OAuth?

No, the ThriveCart MCP server uses a plain API token from your dashboard.

There's no sign-in flow and nothing to renew.

Can the ThriveCart MCP server refund money by accident?

The ThriveCart MCP server only refunds or cancels once you approve it, and it names the order first.

Read-only mode removes every write, which is the right setting for an agent working on its own.

Does a refund cancel the subscription?

No, a refund in ThriveCart doesn't cancel the subscription, which keeps billing on its normal schedule.

A customer who wants to leave needs a refund and a cancellation.

Can I connect more than one ThriveCart cart?

Yes, the ThriveCart MCP server connects as many carts as you list, each with its own token.

Every tool takes an optional account, and each cart's numbers stay separate.

Which AI apps does the ThriveCart MCP server work with?

The ThriveCart MCP server works with any app that speaks MCP.

That includes Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, Zed, Cline, GitHub Copilot CLI, Gemini CLI, OpenCode, OpenClaw, Antigravity and Hermes.

Who made the ThriveCart MCP server & CLI?

I did.

I'm Navid Moazzez, and I made the ThriveCart MCP server & CLI as one of my free tools on navid.me.

You can read more about me.

The code is on GitHub under the MIT license, and the package is on npm.

More MCP servers & CLIs

View all

Kit MCP server & CLI

Draft newsletters, manage subscribers and tags, and read your email stats from Claude, Codex or Cursor.

NewslettersKit

WordPress MCP server & CLI

Edit posts, pages, Elementor and Rank Math SEO on WordPress from Claude, Codex or Cursor.

Blogs

WordPress

Substack MCP server & CLI

Draft posts, publish Notes and check your stats on Substack from Claude, Codex or Cursor.

Newsletters

Substack

Bluesky MCP server & CLI

Post, read and search Bluesky from Claude, Codex or Cursor, or from your terminal.

Bluesky

Threads MCP server & CLI

Post, reply and read your insights on Threads from Claude, Codex or Cursor.

Threads

Mastodon MCP server & CLI

Post, edit and read your timelines on any Mastodon instance from Claude, Codex or Cursor.

Mastodon

TikTok MCP server & CLI

Rank your videos, read your stats and publish to TikTok from Claude, Codex or Cursor.

TikTok

Midjourney MCP server & CLI

Generate images, follow jobs and download the files from Midjourney with Claude, Codex or Cursor.

AI images

Midjourney

Google Photos MCP server & CLI

Pick photos, build albums and upload to Google Photos from Claude, Codex or Cursor.

Photos

Google Photos

Apple Photos MCP server & CLI

Search, look at and organize your Apple Photos library from Claude, Codex or Cursor, on your Mac.

Photos

Apple Photos

Apple Podcasts MCP server & CLI

Track chart ranks, read reviews and search your podcast library from Claude, Codex or Cursor.

Podcasts

Apple Podcasts

Podcast Index MCP server & CLI

Search 4 million podcasts and read episode transcripts from Claude, Codex or Cursor.

Podcasts

Podcast Index

Google Search Console MCP server & CLI

Read your search traffic, check indexing and submit sitemaps from Claude, Codex or Cursor.

SEO

Google Search Console

Google Workspace MCP server & CLI

Work across Gmail, Drive, Sheets, Docs and Calendar from Claude, Codex or Cursor.

Productivity

Google Workspace

iMessage MCP server & CLI

Catch up, search your history and send iMessages from Claude, Codex or Cursor, on your Mac.

Messaging

iMessage

Facebook MCP server & CLI

Read your Page insights, schedule posts and moderate comments, from Claude, Codex or Cursor.

Facebook

Facebook Ad Library MCP server & CLI

Research the ads any brand runs on Facebook and Instagram, from Claude, Codex or Cursor.

Research

Facebook

Vimeo MCP server & CLI

Read transcripts, file videos into folders and add chapters from Claude, Codex or Cursor.

Vimeo

YouTube MCP server & CLI

Read any video's transcript, research channels and manage your own from Claude, Codex or Cursor.

YouTube

Telegram MCP server & CLI

Catch up, search years of chats and reply on Telegram from Claude, Codex or Cursor.

Messaging

Adobe Firefly MCP server & CLI

Generate and edit images with Image 5, make video and composite products from Claude, Codex or Cursor.

AI images

Adobe Firefly

OP3 MCP server & CLI

Read your podcast's downloads, real listeners and retention from Claude, Codex or Cursor.

Podcasts

OP3

Beehiiv MCP server & CLI

Draft posts, manage subscribers and segments, and read your stats, from Claude, Codex or Cursor.

NewslettersBeehiiv

Circle MCP server & CLI

Manage members and spaces, draft posts, and run events and courses, from Claude, Codex or Cursor.

Communities

Circle

Calendly MCP server & CLI

Find open times, book and cancel meetings, and read meeting recaps, from Claude, Codex or Cursor.

Calendly

Wistia MCP server & CLI

Upload and organize videos, fix captions and read your analytics, from Claude, Codex or Cursor.

Wistia

ScrapeCreators MCP server & CLI

Research public profiles, posts, transcripts and ads across social platforms, from Claude, Codex or Cursor.

ScrapeCreators

Shotstack MCP server & CLI

Render videos from templates, make AI clips and manage hosted files, from Claude, Codex or Cursor.

Shotstack

Gumloop MCP server & CLI

Run flows, work with your agents and search your Company Brain, from Claude, Codex or Cursor.

Productivity

Gumloop

Buffer MCP server & CLI

Draft and schedule posts, manage your queues and read your analytics, from Claude, Codex or Cursor.

Buffer

Cloudflare MCP server & CLI

Manage DNS records, clear the cache and change domain settings, from Claude, Codex or Cursor.

Productivity

Cloudflare

Bannerbear MCP server & CLI

Make images, animations and videos from your templates, from Claude, Codex or Cursor.

AI images

Bannerbear

Brandfetch MCP server & CLI

Get any brand's logos, colors and fonts, and compare brands, from Claude, Codex or Cursor.

Research

Brandfetch

Creatomate MCP server & CLI

Edit templates, check renders for free and make videos and images, from Claude, Codex or Cursor.

Creatomate

Dub MCP server & CLI

Create short links, read clicks and sales, and run your partner program, from Claude, Codex or Cursor.

Dub

fal.ai MCP server & CLI

Find models, check prices, and generate images and videos, from Claude, Codex or Cursor.

fal.ai

Flodesk MCP server & CLI

Manage subscribers, segments and workflows, and draft campaigns, from Claude, Codex or Cursor.

SalesFlodesk

Fluent WordPress MCP server & CLI

Work with FluentCRM, FluentCommunity and Fluent Forms on your WordPress site, from Claude, Codex or Cursor.

WordPress

Senja MCP server & CLI

Find, approve and tag testimonials, send invites and export them, from Claude, Codex or Cursor.

Senja

Testimonial.to MCP server & CLI

Read, import and export your testimonials, and send request emails, from Claude, Codex or Cursor.

Testimonial.to

Lemon Squeezy MCP server & CLI

Read and refund orders, manage subscriptions and check license keys, from Claude, Codex or Cursor.

Lemon Squeezy

Gumroad MCP server & CLI

Read sales and payouts, refund orders and manage products and license keys, from Claude, Codex or Cursor.

Gumroad

Fourthwall MCP server & CLI

Manage products and orders, ship them, and run promotions and giveaways, from Claude, Codex or Cursor.

Fourthwall

Teachable MCP server & CLI

Read your courses and student progress, and manage enrollments from Claude, Codex or Cursor.

Teachable

Related free tools

All free tools

Sales page teardown

Check your sales page section by section, from the promise to the button, and get the fixes in order.

MarketingAny website

Pricing page teardown

Check your pricing page against 109 real software pricing pages: plans, trials, the highlighted pick.

MarketingAny website

Grand slam offer generator

Turn your answers into a full offer: bonuses, a guarantee, urgency and a name, each tied to a real objection.

Value ladder generator

Map every offer you sell, free to premium, from your answers or a website, with what moves buyers up.

Profit margin calculator

Your profit margin and markup from a price and a cost, and the price for the margin you want.

Stripe fee calculator

What Stripe's card fees take from a payment and what you receive.

X character counter

Counts the way X counts: links as 23, emoji as 2. LinkedIn, Instagram, TikTok, Threads and YouTube limits too.

Bluesky

Instagram

LinkedIn character counter

LinkedIn's 3,000-character post limit, counted as you type, with X, Threads and Bluesky beside it.

Threads character counter

Threads' 500-character limit, counted as you type, with X, Bluesky and LinkedIn beside it.

Threads

Bluesky character counter

Bluesky's 300-character limit, counted the way the protocol counts, with X and Threads beside it.

Bluesky

Mastodon character counter

Mastodon's 500-character default, counted the way Mastodon counts links and mentions.

Mastodon

Instagram character counter

Instagram's 2,200-character caption limit, counted as you type, with TikTok and the rest beside it.