Cursor

Cursor Configuration

This guide covers setting up Fizzy MCP with Cursor, the AI-powered code editor.

Deployment Modes

Fizzy MCP supports two deployment modes:

Mode	Description	Best For
Remote (Recommended)	Connects to hosted Fizzy MCP service via HTTP	Most users, zero maintenance, always up-to-date
Local	Runs MCP server locally via npx	Offline use, custom modifications, self-hosting

Auto-Configuration

The easiest way to configure Cursor is through the Fizzy MCP CLI:

npx fizzy-do-mcp auth

Or use the configure command directly:

npx fizzy-do-mcp configure

When prompted, select Cursor for automatic configuration. The CLI will detect the best mode for your setup.

Configuration File Location

Cursor stores its MCP configuration at:

~/.cursor/mcp.json

Remote mode connects to the hosted Fizzy MCP service via HTTP transport.

Basic Remote Configuration

{
  "mcpServers": {
    "fizzy": {
      "transport": "http",
      "url": "https://fizzy-mcp-hosted.ryanyogan.workers.dev/mcp",
      "headers": {
        "X-Fizzy-Token": "your-fizzy-token"
      }
    }
  }
}

Remote Configuration with All Headers

{
  "mcpServers": {
    "fizzy": {
      "transport": "http",
      "url": "https://fizzy-mcp-hosted.ryanyogan.workers.dev/mcp",
      "headers": {
        "X-Fizzy-Token": "your-fizzy-token",
        "X-Fizzy-Account-Slug": "/my-org",
        "X-API-Key": "fmcp_your_api_key"
      }
    }
  }
}

Local mode runs the MCP server on your machine via stdio.

Basic Local Configuration

{
  "mcpServers": {
    "fizzy": {
      "command": "npx",
      "args": ["-y", "fizzy-do-mcp@latest"]
    }
  }
}

Local Configuration with Environment Variables

{
  "mcpServers": {
    "fizzy": {
      "command": "npx",
      "args": ["-y", "fizzy-do-mcp@latest"],
      "env": {
        "FIZZY_ACCESS_TOKEN": "your-fizzy-token",
        "FIZZY_ACCOUNT_SLUG": "/my-org"
      }
    }
  }
}

After adding the configuration, restart Cursor to load the new settings.

Remote Mode Headers

When using remote mode, the following headers are available:

Header	Required	Description
`X-Fizzy-Token`	Yes	Your Fizzy personal access token (from app.fizzy.do)
`X-Fizzy-Account-Slug`	No	Account slug like `/my-org` to select a specific account
`X-API-Key`	No	API key for higher rate limits (prefix: `fmcp_`)

Verifying the Connection

After restarting Cursor:

Open the AI chat panel
Check that MCP servers are connected (look for the MCP indicator)
Try asking: “What Fizzy boards do I have?”

Using Fizzy with Cursor

Cursor’s AI can help you manage tasks while coding:

“Create a card for this bug I’m fixing”

“Add this function implementation to the card description”

“What cards are in the current sprint?”

Code-Aware Task Management

Cursor can reference your code when creating tasks:

“Create a card describing the changes I made to auth.ts”

“Update card #42 with the implementation status”

Configuration Options

Global Installation (Local Mode Only)

If you installed Fizzy MCP globally:

{
  "mcpServers": {
    "fizzy": {
      "command": "fizzy-mcp"
    }
  }
}

Authentication for Local Mode

After configuring Cursor with local mode, authenticate with Fizzy:

npx fizzy-do-mcp auth

This stores your credentials securely in ~/.config/fizzy-mcp/config.json (mode 0600). No need to put tokens in your MCP config unless you prefer explicit configuration.

Multiple MCP Servers

You can run Fizzy alongside other MCP servers:

Mixed Remote/Local
All Local

{
  "mcpServers": {
    "fizzy": {
      "transport": "http",
      "url": "https://fizzy-mcp-hosted.ryanyogan.workers.dev/mcp",
      "headers": {
        "X-Fizzy-Token": "your-fizzy-token"
      }
    },
    "github": {
      "command": "npx",
      "args": ["@github/mcp-server"]
    }
  }
}

{
  "mcpServers": {
    "fizzy": {
      "command": "npx",
      "args": ["-y", "fizzy-do-mcp@latest"]
    },
    "github": {
      "command": "npx",
      "args": ["@github/mcp-server"]
    }
  }
}

Troubleshooting

Tools not appearing

Verify ~/.cursor/mcp.json exists and is valid JSON
Restart Cursor completely
Check Cursor’s developer console for errors (Help > Toggle Developer Tools)

“Not authenticated” errors (Remote Mode)

Verify your X-Fizzy-Token header is correct:

Check that the token is valid at app.fizzy.do
Ensure there are no extra spaces or quotes around the token
Regenerate the token if needed

”Not authenticated” errors (Local Mode)

Run fizzy-mcp auth to set up or refresh your credentials:

npx fizzy-do-mcp auth

Permission errors

Ensure the config file is readable:

chmod 644 ~/.cursor/mcp.json

Server not starting (Local Mode)

Test the server manually:

npx fizzy-do-mcp status

Connection issues (Remote Mode)

Check your internet connection

Verify the hosted service is accessible:

curl https://fizzy-mcp-hosted.ryanyogan.workers.dev/health

If using a corporate network, check for firewall rules

Best Practices

Use remote mode for automatic updates and zero maintenance
Keep tokens secure - never commit config files with tokens to version control
Use X-Fizzy-Account-Slug if you have access to multiple Fizzy accounts
Restart Cursor after any configuration changes
Leverage code context - ask Cursor to create cards that reference your current code