MCP Server for Fizzy - A project management tool by Basecamp
npm install fizzy-mcpA Model Context Protocol (MCP) server for Fizzy — the project management tool by Basecamp.
> 📖 Fizzy API Documentation: github.com/basecamp/fizzy/blob/main/docs/API.md
This MCP server allows AI assistants like Claude, Cursor, and GitHub Copilot to interact with your Fizzy boards, cards, and projects through natural language.
- Full Fizzy API Coverage: 47 tools covering Boards, Cards, Card Actions, Comments, Reactions, Steps, Columns, Tags, Users, and Notifications
- Multiple Transport Protocols: Stdio, SSE, and Streamable HTTP
- IDE Integration: Works with Cursor, VS Code, Claude Desktop, and other MCP-compatible tools
- Local or Hosted: Run locally for development or deploy as a hosted service
- Robust Error Handling: Structured error classes with detailed error messages
- Automatic Retries: Exponential backoff retry logic for transient failures (5xx errors, timeouts, network issues)
- Request Timeout: 30-second default timeout to prevent hanging requests
- ETag Caching: Automatic HTTP caching using ETags to reduce bandwidth and improve response times (as per Fizzy API caching spec)
- Fully Tested: Comprehensive test suite with 300+ test cases
- Node.js 18 or higher
- A Fizzy account with API access
---
``bash`
npm install -g fizzy-mcp
The fizzy-mcp command will be available globally.
`bash`
npx fizzy-mcp --help
`bashClone the repository
git clone https://github.com/Fabric-Pro/fizzy-mcp.git
cd fizzy-mcp
command available)To verify the installation:
`bash
fizzy-mcp --help
`---
Getting Your Fizzy Access Token
1. Log in to your Fizzy account
2. Go to your Profile (click your avatar)
3. Navigate to the API section
4. Click on Personal access tokens
5. Click Generate new access token
6. Give it a description and select permissions:
- Read: For read-only access
- Read + Write: For full access (recommended)
7. Copy and save your token securely
> ⚠️ Important: Keep your access token secret! Anyone with your token can access your Fizzy account.
---
Configuration
$3
1. Open Cursor Settings (
Cmd/Ctrl + ,)
2. Search for "MCP" or navigate to Features > MCP Servers
3. Click Edit in mcp.json or manually edit ~/.cursor/mcp.json:Using npx (recommended):
`json
{
"mcpServers": {
"fizzy": {
"command": "npx",
"args": ["-y", "fizzy-mcp"],
"env": {
"FIZZY_ACCESS_TOKEN": "your-fizzy-access-token-here"
}
}
}
}
`If installed globally:
`json
{
"mcpServers": {
"fizzy": {
"command": "fizzy-mcp",
"env": {
"FIZZY_ACCESS_TOKEN": "your-fizzy-access-token-here"
}
}
}
}
`4. Restart Cursor for changes to take effect
$3
Create or edit
.vscode/mcp.json in your workspace (or global settings):`json
{
"mcpServers": {
"fizzy": {
"command": "npx",
"args": ["-y", "fizzy-mcp"],
"env": {
"FIZZY_ACCESS_TOKEN": "your-fizzy-access-token-here"
}
}
}
}
`$3
Edit your Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
- Linux: ~/.config/Claude/claude_desktop_config.json`json
{
"mcpServers": {
"fizzy": {
"command": "npx",
"args": ["-y", "fizzy-mcp"],
"env": {
"FIZZY_ACCESS_TOKEN": "your-fizzy-access-token-here"
}
}
}
}
`---
Running the Server
$3
`bash
Using npx
FIZZY_ACCESS_TOKEN="your-token" npx fizzy-mcpIf installed globally
FIZZY_ACCESS_TOKEN="your-token" fizzy-mcp
`$3
`bash
FIZZY_ACCESS_TOKEN="your-token" npx fizzy-mcp --transport sse --port 3000Endpoints:
SSE: http://localhost:3000/sse
Messages: http://localhost:3000/messages
`$3
`bash
FIZZY_ACCESS_TOKEN="your-token" npx fizzy-mcp --transport http --port 3000Endpoints:
MCP: http://localhost:3000/mcp
Health: http://localhost:3000/health
`---
Environment Variables
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
|
FIZZY_ACCESS_TOKEN | Yes | — | Your Fizzy API access token (required for all operations) |
| FIZZY_BASE_URL | No | https://app.fizzy.do | Fizzy API base URL |
| PORT | No | 3000 | Port for HTTP/SSE transport |
| MCP_TRANSPORT | No | stdio | Default transport (stdio, sse, http) |
| LOG_LEVEL | No | info | Logging level (debug, info, warn, error) |$3
When using HTTP or SSE transports, additional security options are available:
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
|
MCP_ALLOWED_ORIGINS | No | | Allowed CORS origins (comma-separated or for all) |
| MCP_AUTH_TOKEN | No | — | Bearer token for Client Authentication (authenticates MCP clients) |
| MCP_BIND_ALL_INTERFACES | No | false | Set to true to bind to 0.0.0.0 instead of localhost |Security Model:
- Localhost binding (default): Server binds to
127.0.0.1, preventing remote access
- CORS origins: Controls which web origins can connect (default: all)
- Client Authentication: Optional bearer token to authenticate MCP clients connecting to this server`bash
Basic usage (binds to localhost, allows all CORS origins)
FIZZY_ACCESS_TOKEN="your-token" npx fizzy-mcp --transport http --port 3000Restrict CORS to specific origins
MCP_ALLOWED_ORIGINS="http://localhost:3000,https://myapp.com" \
FIZZY_ACCESS_TOKEN="your-token" npx fizzy-mcp --transport http --port 3000Enable Client Authentication (require MCP clients to provide a bearer token)
MCP_AUTH_TOKEN="my-secret-token" \
FIZZY_ACCESS_TOKEN="your-token" npx fizzy-mcp --transport http --port 3000For Docker/remote access (use with restricted origins and client auth)
MCP_BIND_ALL_INTERFACES=true \
MCP_ALLOWED_ORIGINS="https://myapp.com" \
MCP_AUTH_TOKEN="my-secret-token" \
FIZZY_ACCESS_TOKEN="your-token" npx fizzy-mcp --transport http --port 3000
`> ⚠️ Authentication Types:
> - User Authentication (
FIZZY_ACCESS_TOKEN): Always required. Identifies the user and authenticates requests to the Fizzy API.
> - Client Authentication (MCP_AUTH_TOKEN): Optional. Authenticates MCP clients (like IDE extensions) connecting to this server.---
Available Tools (52 total)
$3
| Tool | Description |
|------|-------------|
| fizzy_get_identity | Get current user's identity and accounts |
| fizzy_get_accounts | List all accessible accounts |
| fizzy_get_account | Get details of a specific account |$3
| Tool | Description |
|------|-------------|
| fizzy_get_boards | List all boards in an account |
| fizzy_get_board | Get details of a specific board |
| fizzy_create_board | Create a new board |
| fizzy_update_board | Update a board's name |
| fizzy_delete_board | Delete a board |$3
| Tool | Description |
|------|-------------|
| fizzy_get_cards | List cards with optional filters (status, column, assignees, tags, search) |
| fizzy_get_board_cards | List cards on a specific board |
| fizzy_get_card | Get card details including description, assignees, tags |
| fizzy_create_card | Create a new card with title, description, status, column, assignees, tags, due date |
| fizzy_update_card | Update any card property |
| fizzy_delete_card | Delete a card |$3
| Tool | Description |
|------|-------------|
| fizzy_close_card | Close a card (mark as done) |
| fizzy_reopen_card | Reopen a closed card |
| fizzy_move_card_to_not_now | Move a card to "Not Now" triage |
| fizzy_move_card_to_column | Move a card from triage to a specific column |
| fizzy_send_card_to_triage | Send a card back to triage (remove from column) |
| fizzy_toggle_card_tag | Toggle a tag on/off for a card |
| fizzy_toggle_card_assignment | Toggle a user assignment on/off for a card |
| fizzy_watch_card | Subscribe to notifications for a card |
| fizzy_unwatch_card | Unsubscribe from notifications for a card |$3
| Tool | Description |
|------|-------------|
| fizzy_get_card_comments | List comments on a card |
| fizzy_get_comment | Get a specific comment |
| fizzy_create_comment | Add a comment to a card (supports HTML) |
| fizzy_update_comment | Update a comment |
| fizzy_delete_comment | Delete a comment |$3
| Tool | Description |
|------|-------------|
| fizzy_get_reactions | Get all emoji reactions on a comment |
| fizzy_add_reaction | Add an emoji reaction to a comment |
| fizzy_remove_reaction | Remove an emoji reaction from a comment |$3
| Tool | Description |
|------|-------------|
| fizzy_get_step | Get a specific to-do step on a card |
| fizzy_create_step | Create a new to-do step on a card |
| fizzy_update_step | Update a step (description or completion status) |
| fizzy_delete_step | Delete a step from a card |$3
| Tool | Description |
|------|-------------|
| fizzy_get_columns | List columns on a board |
| fizzy_get_column | Get column details |
| fizzy_create_column | Create a new column with name and color |
| fizzy_update_column | Update column name/color |
| fizzy_delete_column | Delete a column |$3
| Tool | Description |
|------|-------------|
| fizzy_get_tags | List all tags in an account |
| fizzy_get_board_tags | List tags used on a board |
| fizzy_create_tag | Create a new tag |
| fizzy_delete_tag | Delete a tag |$3
| Tool | Description |
|------|-------------|
| fizzy_get_users | List users in an account |
| fizzy_get_user | Get user details |
| fizzy_update_user | Update user's display name |
| fizzy_deactivate_user | Deactivate a user |$3
| Tool | Description |
|------|-------------|
| fizzy_get_notifications | List notifications for current user |
| fizzy_mark_notification_read | Mark notification as read |
| fizzy_mark_notification_unread | Mark notification as unread |
| fizzy_mark_all_notifications_read | Mark all notifications as read |---
Example Prompts
Once configured, you can ask your AI assistant things like:
- "Show me all my Fizzy boards"
- "What cards are on my Engineering board?"
- "Create a new card called 'Fix login bug' on the Engineering board"
- "What cards are assigned to me?"
- "Move the 'Design review' card to the 'Done' column"
- "Add a comment to the authentication card saying 'Ready for review'"
- "Show me my unread notifications"
- "List all users in my account"
- "Create a new column called 'In Review' with blue color on the Engineering board"
---
Troubleshooting
$3
Make sure you've set your access token in the MCP configuration's env section.$3
- Use npx fizzy-mcp instead of fizzy-mcp
- Or install globally: npm install -g fizzy-mcp$3
1. Restart the IDE after configuration changes
2. Check the path to the executable is correct
3. Verify Node.js is installed: node --version
4. Check Cursor's MCP logs for errors$3
- Verify your access token is valid
- Check that you're using the correct account slug
- Ensure you have permission to access the resource$3
Test your token directly:
`bash
curl -H "Authorization: Bearer your-token" \
-H "Accept: application/json" \
https://app.fizzy.do/my/identity.json
`---
API Reference
This server implements all endpoints from the official Fizzy API Documentation:
| Category | Endpoints Covered |
|----------|-------------------|
| Identity | GET /my/identity.json |
| Accounts | Embedded in identity |
| Boards | GET, POST, PUT, DELETE |
| Cards | GET (list, board, single), POST, PUT, DELETE + filtering |
| Comments | GET, POST, DELETE |
| Columns | GET (list, single), POST, PUT, DELETE |
| Tags | GET (account, board), POST, DELETE |
| Users | GET (list, single), PUT, DELETE |
| Notifications | GET, POST reading, DELETE reading, POST bulk_reading |
---
Development
For contributors and developers:
`bash
Clone the repository
git clone https://github.com/Fabric-Pro/fizzy-mcp.git
cd fizzy-mcpInstall dependencies
npm installRun in development mode with hot reload
npm run devBuild for production
npm run buildRun tests
npm testRun tests with coverage
npm run test:coverageType checking
npm run typecheck
`---
License
MIT
Contributing
Contributions are welcome! Please:
1. Fork the repository
2. Create a feature branch
3. Add tests for new functionality
4. Ensure all tests pass:
npm test`Created by Preetham Reddy