Remote Mode (Recommended)
Zero maintenance. Uses our hosted service with HTTP transport. No local server process to manage. - Automatic updates - No Node.js process running - Rate limits apply (upgradeable with API key)
This guide gets you from zero to managing Fizzy tasks with your AI assistant in under 5 minutes.
Fizzy MCP supports two deployment modes:
Remote Mode (Recommended)
Zero maintenance. Uses our hosted service with HTTP transport. No local server process to manage. - Automatic updates - No Node.js process running - Rate limits apply (upgradeable with API key)
Local Mode
Full control. Traditional stdio MCP server running locally via npx. - No rate limits - Works offline - Requires Node.js runtime
Install and Authenticate
npx @fizzy-mcp/server authWhen prompted for deployment mode, select remote (or just press Enter for the default).
Get Your Access Token
At the token prompt, press Enter to open your browser to the Fizzy API settings page:
Enter your access token (or press Enter to open browser):Opening browser to https://app.fizzy.do/my/profile/api...Copy your token and paste it back in the terminal.
Optional: Add an API Key
For higher rate limits (1,000 writes/day vs 100), enter an API key when prompted:
Enter API key (or press Enter to skip): fmcp_xxxxxxxxxxxxxAuto-Configure Your AI Agent
When prompted, confirm to configure your AI agents:
Would you like to configure Fizzy for these agents? [Y/n] y
Configuring for remote mode...
✔ Configured Claude Desktop → ~/.config/Claude/claude_desktop_config.jsonRestart Your AI Agent
Close and reopen your AI agent (Claude Desktop, Cursor, etc.) to load the new MCP server.
Start Using Fizzy!
Try these commands with your AI:
“Show me my Fizzy boards”
“Create a card on the Engineering board called ‘Fix login bug’”
“What cards are assigned to me?”
Install and Authenticate
npx @fizzy-mcp/server auth --mode localGet Your Access Token
Press Enter to open your browser, or paste your token directly:
Enter your access token (or press Enter to open browser): fz_xxxxxxxxxxxxxAuto-Configure Your AI Agent
Confirm to configure your agents for local mode:
Would you like to configure Fizzy for these agents? [Y/n] y
Configuring for local mode...
✔ Configured Claude Desktop → ~/.config/Claude/claude_desktop_config.jsonRestart Your AI Agent
Close and reopen your AI agent to load the MCP server.
Start Using Fizzy!
Try these commands with your AI:
“Show me my Fizzy boards”
“Create a card on the Engineering board called ‘Fix login bug‘“
The auth command supports several options for non-interactive setup:
# Default: interactive remote modenpx @fizzy-mcp/server auth
# Explicitly set modenpx @fizzy-mcp/server auth --mode remotenpx @fizzy-mcp/server auth --mode local
# Remote mode with API key (higher rate limits)npx @fizzy-mcp/server auth --mode remote --api-key fmcp_xxxxxxxxxxxxx
# Skip agent configurationnpx @fizzy-mcp/server auth --no-configure| Option | Short | Description |
|---|---|---|
--mode <mode> | -m | Deployment mode: remote (default) or local |
--api-key <key> | -k | API key for higher rate limits (remote mode only) |
--no-configure | Skip auto-configuration of AI agents |
You: “What boards do I have access to?”
Claude: I’ll check your Fizzy boards.
[ { "id": "abc123", "name": "Engineering", "cards_count": 24 }, { "id": "def456", "name": "Design", "cards_count": 12 }, { "id": "ghi789", "name": "Marketing", "cards_count": 8 }]You have access to 3 boards: Engineering (24 cards), Design (12 cards), and Marketing (8 cards).
You: “Create a high-priority card for ‘Implement OAuth login’ on the Engineering board”
Claude: I’ll create that card for you.
Created card #142: “Implement OAuth login” on the Engineering board.
You: “Move card #142 to the ‘In Progress’ column”
Claude: Done! Card #142 has been moved to the “In Progress” column.
You: “Tag card #142 with ‘urgent’ and ‘backend’”
Claude: I’ve added both tags to card #142:
You: “Assign card #142 to Sarah”
Claude: Card #142 has been assigned to Sarah.
If auto-configuration doesn’t work, you can manually add Fizzy MCP to your agent’s config file.
Edit ~/.config/Claude/claude_desktop_config.json (Linux/macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{ "mcpServers": { "fizzy": { "type": "http", "url": "https://fizzy-mcp-hosted.ryanyogan.workers.dev/mcp", "headers": { "Authorization": "Bearer fz_xxxxxxxxxxxxx", "X-Fizzy-Api-Key": "fmcp_xxxxxxxxxxxxx" } } }}Edit ~/.cursor/mcp.json:
{ "mcpServers": { "fizzy": { "type": "http", "url": "https://fizzy-mcp-hosted.ryanyogan.workers.dev/mcp", "headers": { "Authorization": "Bearer fz_xxxxxxxxxxxxx", "X-Fizzy-Api-Key": "fmcp_xxxxxxxxxxxxx" } } }}Edit ~/.config/opencode/opencode.json:
{ "mcp": { "fizzy": { "type": "http", "url": "https://fizzy-mcp-hosted.ryanyogan.workers.dev/mcp", "headers": { "Authorization": "Bearer fz_xxxxxxxxxxxxx", "X-Fizzy-Api-Key": "fmcp_xxxxxxxxxxxxx" } } }}Edit ~/.claude/settings.json:
{ "mcpServers": { "fizzy": { "type": "http", "url": "https://fizzy-mcp-hosted.ryanyogan.workers.dev/mcp", "headers": { "Authorization": "Bearer fz_xxxxxxxxxxxxx", "X-Fizzy-Api-Key": "fmcp_xxxxxxxxxxxxx" } } }}Edit ~/.config/Claude/claude_desktop_config.json (Linux/macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{ "mcpServers": { "fizzy": { "command": "npx", "args": ["@fizzy-mcp/server"] } }}Edit ~/.cursor/mcp.json:
{ "mcpServers": { "fizzy": { "command": "npx", "args": ["@fizzy-mcp/server"] } }}Edit ~/.config/opencode/opencode.json:
{ "mcp": { "fizzy": { "type": "local", "command": "npx", "args": ["@fizzy-mcp/server"] } }}Edit ~/.claude/settings.json:
{ "mcpServers": { "fizzy": { "command": "npx", "args": ["@fizzy-mcp/server"] } }}For both modes, you can use environment variables instead of storing tokens in config files:
{ "mcpServers": { "fizzy": { "type": "http", "url": "https://fizzy-mcp-hosted.ryanyogan.workers.dev/mcp", "headers": { "Authorization": "Bearer ${FIZZY_ACCESS_TOKEN}", "X-Fizzy-Api-Key": "${FIZZY_API_KEY}" } } }}Then set environment variables:
export FIZZY_ACCESS_TOKEN=fz_xxxxxxxxxxxxxexport FIZZY_API_KEY=fmcp_xxxxxxxxxxxxx # Optional{ "mcpServers": { "fizzy": { "command": "npx", "args": ["@fizzy-mcp/server"], "env": { "FIZZY_ACCESS_TOKEN": "${FIZZY_ACCESS_TOKEN}" } } }}Then set environment variables:
export FIZZY_ACCESS_TOKEN=fz_xxxxxxxxxxxxx| Tier | Write Operations | Read Operations |
|---|---|---|
| Anonymous (no API key) | 100/day | Unlimited |
| With API Key | 1,000/day | Unlimited |
Write operations include: creating cards, updating cards, deleting cards, moving cards, adding comments, etc.
To check your current usage or upgrade your rate limit:
npx @fizzy-mcp/server auth to add the keynpx @fizzy-mcp/server whoamicurl https://fizzy-mcp-hosted.ryanyogan.workers.dev/healthRun npx @fizzy-mcp/server auth again to re-authenticate.
npx @fizzy-mcp/server auth --api-key fmcp_xxxxxxxxxxxxxnpx @fizzy-mcp/server auth --mode localThe first call may take a few seconds as the server starts. Subsequent calls are faster.
curl https://fizzy-mcp-hosted.ryanyogan.workers.dev/healthfz_): Required for all modes. Authenticates you with Fizzy.fmcp_): Optional, remote mode only. Increases rate limits.