Fizzy runs on your own machine — the client starts it, so there is no endpoint to ping. 39 installs a week from npm. Last commit 15 Feb 2026.
MCP server for Fizzy task management
Today is the operative word: we check Fizzy every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add fizzy -- npx -y @silky/fizzy-mcp
{
"mcpServers": {
"fizzy": {
"args": [
"-y",
"@silky/fizzy-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.fizzy]
command = "npx"
args = ["-y", "@silky/fizzy-mcp"]
{
"mcpServers": {
"fizzy": {
"args": [
"-y",
"@silky/fizzy-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"fizzy": {
"args": [
"-y",
"@silky/fizzy-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
FIZZY_TOKEN (Fizzy API authentication token), FIZZY_BASE_URL (Fizzy API base URL (defaults to production)), FIZZY_ACCOUNT (Default Fizzy account slug).
The author declared them in the registry entry; get the values from the project itself.
A test MCP server for task management
MCP server for Todoist task management integration
MCP Server for Dida365 (TickTick) Task Management Integration
MCP server for Megaplan — tasks, deals management via API v3.
MCP server for URL shortening and management
MCP server for Taskwarrior 3.x, TaskChampion, and Timewarrior task management.
MCP Server for an Agent Task Marketplace
DevCycle MCP server for feature flag management
Answers built from our own checks of this server.