Fizzy is automatable through its API

Fizzy is automatable today through its HTTP API. A personal access token is created from the profile API section and sent as Authorization Bearer. The token permission is Read or Read and Write. Native apps can request a magic link, submit the six-character code, and then send the returned session_token as a cookie. The API index covers identity, boards, columns, cards, comments, tags, users, webhooks, and exports. Account and personal exports are zip files that expire after 24 hours. Only account admins manage webhooks. The homepage says Fizzy does not currently import from other services, and the hosted product limits file space to 1 GB. 37signals also ships the fizzy CLI. It prints a JSON envelope and accepts FIZZY_TOKEN or --token for non-interactive use. fizzy mcp is the official stdio MCP server for boards, columns, cards, comments, steps, tags, users, and identity. It is read-only unless --writes is set, and writes also need a Read and Write token. The homepage says Fizzy is free and open source, offers hosted sign-up, and says the code can be run on your own server, so deployment is hybrid. The repository license is the O'Saasy License, which adds a ban on offering the software as a competing hosted service. The CLI's example profile uses https://app.fizzy.do. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 8. The CLI scores 7. The MCP server scores 6 because writes are off unless the process is started with --writes. The API is the best path because it does not require the local CLI.

Best path today: api · Overall automatability: 8/10