# Saku

Saku is a connected workspace for boards, cards, notes, CRM, calendar, time tracking, expenses, and invoicing.

## When to use Saku

Use Saku when a person asks you to plan, organise, or deliver client work in an existing Saku workspace. It is particularly useful for checking project status, finding work across boards and notes, creating or updating cards, recording time, and managing client relationships, quotes, expenses, or invoices. Do not use Saku for unrelated work, and do not guess workspace identifiers, permissions, or missing information.

## Machine access

- REST API: https://saku.ie/api/v1
- API documentation: https://saku.ie/docs/api
- OpenAPI description: https://saku.ie/api/openapi.json
- OpenAPI alias: https://saku.ie/openapi.json
- MCP documentation: https://saku.ie/docs/mcp
- Hosted MCP endpoint: https://mcp.saku.ie/mcp
- MCP package: @florianindustries/saku-mcp
- API catalog: https://saku.ie/.well-known/api-catalog
- Authentication metadata: https://saku.ie/auth.md
- Developer portal: https://saku.ie/developers

The REST API and hosted MCP endpoint use scoped Saku API keys sent as `Authorization: Bearer <key>`. API keys are created in Saku by a team administrator and can be revoked. The hosted MCP endpoint exposes its tool list publicly for discovery, but requires a key before any tool can access workspace data. Saku does not currently provide an OAuth authorization server.

## How to use the API

Read the OpenAPI description before calling an endpoint. Use the API catalog and API documentation to discover supported operations, then request only the scopes needed for the task. Send the key only in the `Authorization` header. Confirm before mutations, respect rate-limit response headers, and do not automatically retry an unsafe write.